spec sheet · code & design

Your workflows and Transglot, automate the localization handoff.

Connect a project token to your automation tool, choose an action, and test it with a small project. Start translations and use project events to continue your workflow when they are ready.

Project events out; API actions in

Direction: Project events out; API actions in
Plan: Starter and up
Scope: project events out, translation runs and pulls back in
Authentication: a project deploy token carrying push, pull and manage
Get started: Connect through the project API, signed webhooks, or the self-hosted n8n package.

Create your project Setup

code & design

the workflow

Connect your content. Review every language.

Connect once, choose your content and languages, then translate and review in the same project. The steps below show how it works in your tool.

Choose a workflow
Pick the project event or manual action that starts your automation.
choose
Connect the API
Configure the project token in your automation tool’s credential store.
connect
Run the localization steps
Push a source file, optionally start a translation batch, and wait for the batch result.
run
Deliver the locale files
Pull the target-locale output and send it to the next step in your workflow.
deliver

Use event payloads to start your automation and API actions to push, translate, inspect a batch or pull locale files.

what moves

What you can translate and deliver.

Connect localization with Zapier, Make or n8n through their own Transglot apps. Each has its own supported actions, setup guide and release availability. Translation batches use the same public API as the CLI; event triggers are available in Zapier and self-hosted n8n.

What you can translate and deliver.
Surface	What to expect
Source and scope	project events out, translation runs and pulls back in
Translated output	Use event payloads to start your automation and API actions to push, translate, inspect a batch or pull locale files.
Keep in mind	Your automation owns its steps and credentials. AI batches use your Transglot word allowance; a webhook needs a reachable receiver.

get connected

A few steps to your first connection.

Follow your tool’s setup below: add the connection, choose what to sync, and try it with a small set of content. Your team can keep working in the tools they already use.

What you need

a project deploy token carrying push, pull and manage.

A Transglot project with its source and target locales configured.
Save credentials in the connection settings so your team can work without copying secrets between files.
Hosted API access requires a paid Transglot plan. AI translation uses your workspace’s word allowance.

Create your project

Create a project access token with only the abilities your workflow needs.
Configure the Transglot API connection in Zapier, Make or n8n, or use their HTTP request actions.
Register a project webhook for the events you need, then verify signed deliveries in your receiver.
Connect the event to a push, translate, batch-status or pull action and test the complete workflow.

same project, more possibilities