Ready-made connectors

How to wire Tygy into Zapier, Make, n8n and Albato before the official apps exist.

What is possible today

Official directory apps are planned, not published. But the public API and webhooks are enough to build the integration yourself in any of these services, without code.

You need two things: an API key from Settings → API & MCP, and a service that can receive a webhook and make an HTTP request. All four can.

Catching events

The recipe is the same everywhere:

1. Create a scenario starting with a «Webhook» step (Albato calls it «Incoming webhook»). The service gives you an address.
2. In Tygy open Settings → API & MCP → Webhooks → Add webhook, paste that address and tick the events you want.
3. Press «Test» — a sample event appears in the scenario and the service learns the data shape.

From there work with the fields inside data: it is the same object the API returns.

Verifying the signature is usually impossible in no-code tools. The webhook address is itself a secret: do not publish it. If the data is sensitive, receive events with your own code and verify the signature.

Taking actions

Use an «HTTP Request» step (Make: «HTTP → Make a request», n8n: the «HTTP Request» node, Albato: «HTTP request»):

• Method: POST, PATCH or GET
• URL: https://api.tg-desk.com/v1/…
• Header: Authorization: Bearer <your key>
• Body: JSON

For example, replying to a customer:

POST https://api.tg-desk.com/v1/conversations/{{conversation_id}}/messages
Authorization: Bearer tgdesk_…
Content-Type: application/json

{ "body": "Thanks for reaching out! We are on it." }

Three useful recipes

New request → a CRM record. conversation.created → create a deal in your CRM, using data.contact_id (fetch the person with GET /v1/contacts/{id}).

Conversation closed → a spreadsheet row. conversation.status_changed filtered on data.status = closed → append a row to Google Sheets for reporting.

Website enquiry → a message in the team's Telegram chat. message.created filtered on data.direction = inbound → send the text to your chat.

Limits worth knowing

• 300 requests per minute per key. Plenty for scenarios, but do not build a loop that calls the API once per row of a large spreadsheet.
• Five seconds to answer a webhook. Builder services normally answer immediately and run the scenario asynchronously, which is fine.
• Create a separate key per integration, with minimal scopes. Then you can cut one integration off without touching the others.