Zapier, Make and n8n
Start an automation when something happens in a transglot project, and drive transglot from your flows over the API.
Automation platforms connect to transglot in two directions, and you can use either or both:
- transglot to your flow. transglot sends a signed event to your flow when something happens in a project: a batch finishes, translations are reviewed, a language is added, a quality check completes. Use it for "when a batch completes, post to the release channel" or "when a locale is reviewed, start a deploy", without polling.
- Your flow to transglot. Your flow calls the public API to push source files, start a translation, read a batch's status or pull a translated file.
Both directions authenticate with a deploy token, which belongs to one project. There is no project id to configure: the token is the project.
Requirements
- Plan: Starter or above. The API, deploy tokens and webhooks are not part of the Free plan.
- A deploy token for the project, created by an Owner or Admin. Give it only the abilities your flow uses:
| What the flow does | Ability needed |
|---|---|
| Read the project or a batch | any ability |
| Push source files | push |
| Pull translated files | pull |
| Start a translation | manage |
| Subscribe to events (turn a trigger on or off) | manage |
n8n
transglot publishes an n8n community node package, n8n-nodes-transglot. It adds two nodes:
- transglot, an action node. Resource Project: Get, Push Source, Translate, Pull. Resource Batch: Get.
- transglot Trigger, which starts a workflow when the project event you pick in Event fires.
Install the package
In your n8n instance, go to Settings, Community Nodes, Install, enter n8n-nodes-transglot and confirm. On a self-hosted instance you can also install it into your custom nodes directory and restart n8n:
npm install n8n-nodes-transglotCreate the credential
Add a transglot API credential:
| Field | Value |
|---|---|
| Base URL | https://api.transglot.ai (the default) |
| API Token | Your deploy token, starting tgl_ |
Select Test. A successful test confirms the URL, the token and the project without changing anything.
Build the workflow
Add a transglot Trigger node to react to events, or a transglot node to act on the project. When you activate a workflow that starts with transglot Trigger, the node subscribes to the event; when you deactivate it, the subscription is removed.
Zapier and Make
Use the webhook and HTTP tools built into Zapier and Make.
To start a Zap or scenario from a transglot event:
- Create a trigger in Zapier or Make that gives you an incoming webhook URL.
- In transglot, create a webhook endpoint on the project with that URL, and choose the events that should start the flow.
- Zapier and Make learn the payload shape from the first delivery they receive. To map fields before then, use the examples in the event reference, or fetch one from
GET /v1/webhooks/events/{event}/sample.
Every delivery is signed. If your flow can run code, verify the signature before acting on a delivery.
To act on transglot from a Zap or scenario, add an HTTP request step that calls the API with the header Authorization: Bearer <your deploy token>. Common calls:
| Goal | Request |
|---|---|
| Push a source file | POST https://api.transglot.ai/v1/push |
| Start a translation | POST https://api.transglot.ai/v1/translate |
| Check a batch | GET https://api.transglot.ai/v1/batches/{id} |
| Pull a translated file | GET https://api.transglot.ai/v1/pull |
See the API reference for parameters and responses.
Manage event subscriptions over the API
Any tool that can make HTTP requests can subscribe and unsubscribe itself, the way the n8n trigger does:
| Request | What it does |
|---|---|
GET /v1/webhooks/events | Lists the events you can subscribe to |
GET /v1/webhooks/events/{event}/sample | Returns a sample payload for one event |
POST /v1/webhooks | Subscribes a URL to one or more events. Send url and an events array. The response includes the signing secret, shown only this once |
GET /v1/webhooks | Lists this project's subscriptions |
DELETE /v1/webhooks/{id} | Removes a subscription |
A subscription created this way is an ordinary webhook endpoint on the project, with the same signing, retries and delivery log as one created in the console.
Troubleshooting
The token is wrong, expired or revoked. Create a new deploy token and update the credential.
Either the token lacks the manage ability, or the account's plan does not include webhooks. Webhooks need the Starter plan or above.
transglot only delivers to public HTTPS addresses. The response says which rule the URL broke, for example "The webhook URL must use https." or "The webhook URL resolves to a private or reserved address." Use the webhook URL your automation platform gives you.