Lokalise manages your translation keys, tasks and vendor orders. FlowMattic posts translation updates to the localization channel, DMs translators when a task is created, tells developers about key comments and reports when tasks close or orders complete. For localization managers and developers who ship in many languages and plan releases in Slack.
26 triggers 14 actions 6 example workflows 2 ready-made templates Unlimited runs
When this happens in Lokalise26 triggers
Do this in Slack14 actions
1. TriggerTranslation Updated2. ActionSend Channel MessageWhen Lokalise fires Translation Updated, FlowMattic runs Send Channel Message in Slack with the data from that event.
You build this in the FlowMattic workflow builder on your own site. See the setup steps
Each one uses only triggers and actions the two integrations ship today, plus FlowMattic's own tools. Where the library has a ready-made template, import it instead of building from scratch.
Ready-made templateEach updated translation posts with the key, language and new text, so the localization manager can follow progress during a busy release week.
Translation UpdatedSend Channel Message
View the template Find User by Email finds the assignee in Slack, and the DM gives the task name, languages and due date, so in-house translators start on time.
Task CreatedFind User by EmailSend Direct Message
A closed translation or review task means those languages are ready. The release channel hears it, so the build can include the new strings.
Task ClosedSend Channel Message
Translators comment on keys to ask about context or length limits. Posting the comment and key name to the dev channel gets them a quick answer.
Key Comment AddedSend Channel Message
When a vendor order is completed, the localization manager gets the order details in Slack and can review the delivered languages.
Order CompletedSend Direct Message
Contributor Added Public posts new self-signups to a private admin channel, so admins can check who joined a community translation project.
Contributor Added PublicSend Private Channel Message
At the end, every translation updated in your Lokalise project posts the key, language and text to Slack.
Under Connects in FlowMattic, add your Slack workspace.
Create a workflow with Lokalise and Translation Updated, then follow the trigger's instructions to add the workflow as a webhook in your Lokalise project.
Change one translation in Lokalise so FlowMattic captures the event fields.
Add Slack Send Channel Message, choose the localization channel, map the key, language, translation and user, test it and switch the workflow on.
1. Trigger in Lokalise
Translation Updated
2. Action in Slack
Send Channel Message
Fields mapped from the earlier steps (a typical setup)
| From Lokalise | To Slack |
|---|---|
| Key name | Message: key |
| Language | Message: language |
| Translation | Message: new text |
| User | Message: edited by |
| Project name | Message: project |
A trigger starts a workflow. An action is something FlowMattic does in the app as a step.
Lokalise and Slack connect through FlowMattic on your own site, with no separate automation account in the middle and no charge per run.
Closed tasks and completed orders reach the release channel, so the build picks up translations as soon as they are ready.
Key comments land where developers read, so translators get context without a separate email thread.
FlowMattic runs on your WordPress site with unlimited runs, so thousands of translation events need no bigger plan.
Create a FlowMattic workflow with a Lokalise trigger such as Translation Updated, add the workflow as a webhook in your Lokalise project, then add Slack Send Channel Message and map the key, language and text.
Yes. Start with Task Created, find the assignee with Find User by Email, then send them a direct message with the task and due date.
Yes. Add a Filter on the language field so only the languages your team reviews reach the channel, or a Router to send each language to its reviewer.
Yes. Key Added is its own trigger. Post it to the translators channel so they know new text is waiting.
No. These workflows read Lokalise events and post to Slack. Tasks, keys and translations are still managed in Lokalise.
Did not find your answer? You can browse the help center or ask us directly.
Slack and Google Sheets149 shared templates
Slack and Airtable44 shared templates
Slack and Fluent Forms42 shared templates
Slack and FluentCRM35 shared templates
Slack and ClickUp28 shared templates
Slack and Fluent Support21 shared templates
Slack and WooCommerce18 shared templates
Slack and Notion17 shared templatesInstall FlowMattic, connect both accounts and import a template. Every run stays on your own server.
30-day money-back guarantee Unlimited workflows and runs Self-hosted
Reviewed 27 Oct 2026. The example workflows are written with AI from the real triggers and actions of both integrations and checked against them. Lokalise integration 1.0.0, Slack integration 1.0.
