Localazy sits between your code and your translators. FlowMattic tells Slack when new source keys arrive for translation, when translators leave a comment, when a release tag is promoted and when the project is published. For developers and localization managers who ship apps or websites in several languages and coordinate releases in Slack.
5 triggers14 actions5 example workflows2 ready-made templatesUnlimited runs
Try a pairing
When this happens in Localazy5 triggers
Do this in Slack14 actions
1. TriggerProject Published
2. ActionSend Channel Message
When Localazy fires Project Published, 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
Localazy and Slack workflows you can build
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 template
Tell the team when a Localazy project is published
The project name posts to the release channel when translations are published, so developers know the new strings are ready to pull into the build.
Alert translators when new source keys are imported
Content Imported fires when keys are added, updated or deprecated. Translators see in their channel that there is new text to work on before the release date.
Content Imported→Send Channel Message
Send translator comments to the developers
Translators often ask what a placeholder means or how long a label can be. Posting their comments to the dev channel gets them an answer from the person who wrote the string.
Comment Added→Send Channel Message
Announce promoted release tags
When a release tag is promoted, for example from staging to production, the release channel hears about it, so QA knows which translations are going live.
Tag Promoted→Send Channel Message
Log imports that changed nothing in a quiet channel
Content Imported Empty confirms that an upload from your CI ran with no changes. A private log channel shows the sync is alive without disturbing translators.
At the end, every time a Localazy project is published your release channel gets a message with the project name.
1
Connect Slack
Add your Slack workspace under Connects in FlowMattic.
2
Start with Project Published
Create a workflow with Localazy and Project Published, then follow the trigger's instructions to add the workflow as a webhook in your Localazy project.
3
Publish once
Publish the project in Localazy so FlowMattic captures the event fields.
4
Post to the release channel
Add Slack Send Channel Message, choose the channel, map the project name and time, test it and switch the workflow on.
Send Channel MessagePost or Schedule a new message to a specific #channel
Add ReminderAdds a reminder for the user
Create ChannelCreates a new channel
List All ChannelsRetrieve list of all channels
Set Channel TopicSets the topic on a selected channel
Set StatusSets your Slack status to the given text and emoji
Invite User To ChannelInvite an existing User to an existing Channel. You must be a member of the channel to invite someone to it
Find User by EmailFinds a user by matching against their email instead of their username
Find User by IDFinds a user by their ID.
Send Direct MessageSend a direct message to a user or yourself from the Slackbot. Can also schedule a message for later
Send Private Channel MessagePost a new message to a private channel you choose. Can also schedule a message for later
Update ProfileUpdate basic profile fields such as name or title
Find MessageFinds a Slack message using the Slack Search feature
Upload FileUpload file to your slack workplace
Why run this pair with FlowMattic
Localazy and Slack connect through FlowMattic on your own site, with no separate automation account in the middle and no charge per run.
Translators hear about new text
New and changed keys reach the translators channel, so translation starts before the release deadline, not after.
Developers see questions sooner
Translator comments arrive where developers read, which cuts the wait for an answer about context.
Runs on your server
FlowMattic runs on your WordPress site with unlimited runs, so frequent CI imports cost nothing extra.
Common questions
How do I connect Localazy to Slack?
Create a FlowMattic workflow with a Localazy trigger such as Project Published, add the workflow's address as a webhook in the Localazy project, then add Slack Send Channel Message.
Can translators be told when there are new strings?
Yes. Content Imported fires when keys are added, updated or deprecated. Post it to the translators channel with the project name.
What is Content Imported Empty for?
It fires when an import finished with no changes. It is handy as a health check for automated uploads, posted to a quiet log channel.
Can each project post to its own channel?
Yes. Build one workflow per project, or use a Router on the project name so each project's events go to that team's channel.
Can a reminder be set when new keys arrive?
Yes. Add Add Reminder after the Content Imported step so the localization manager checks progress a few days before the release.
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. Localazy integration 1.0.0, Slack integration 1.0.