When a Lokalise task is closed, update the row in Airtable and notify the team in Slack

When a translation or review task is closed in Lokalise, FlowMattic finds the matching Airtable record, updates it, and posts a message to your Slack channel so the team knows the work is done.

Lokalise

Airtable

Filter

Slack

Download this workflow Browse more workflows

5 steps Setup ~8 min Used on 2.1k sites Productivity Free to import

The When a Lokalise task is closed, update the row in Airtable and notify the team in Slack workflow on the FlowMattic canvas, with 5 steps across Lokalise, Airtable, Filter, Slack — The workflow as it appears in the builder after import. Each step opens for editing.

What this workflow does

Localization teams often track their Lokalise tasks in an Airtable base next to release dates, owners and markets. Keeping that base current by hand means someone has to notice each finished task and edit the right record. This workflow does the lookup and the edit for you, then tells the team in Slack.

The Lokalise trigger fires when a translation or review task is closed in a project, and passes the task details on. The first Airtable step searches your base with a filter formula. You write that formula after import, usually matching a column in which you keep the Lokalise task ID or title against the value from the trigger.

A Filter then checks how many records the search found. The run continues only when the total is greater than 0, so a task with no matching record never reaches the update or the Slack message. When there is a match, the Update Record step edits the first record the search returned. Its record ID is already mapped; you choose which fields change, such as a status column set to Done.

Last, the Slack step posts to a channel. It ships unmapped, so pick the channel and write the message with the task and record details you want. Task History shows what Airtable returned at each step.

Release tracker that updates itself

A product team lists every Lokalise task for the next release in Airtable. Closing a task in Lokalise marks its record as translated, and the release channel in Slack sees it.

Agency jobs per client

A translation agency keeps one Airtable record per client job. When the reviewer closes the review task, the job's status changes and the account manager hears about it in Slack.

Marketing copy ready for launch

A marketing team waits on translated campaign strings. The closed task updates the campaign record, and the Slack post tells the designers they can start on the localized assets.

How this workflow runs

What happens at each step once the workflow is on, and what you need before you import it.

Step 1Trigger
Lokalise Task Closed
Fires when a translation or review task is closed in a Lokalise project. The task's details are passed to the Airtable search and can be mapped into the Slack message.
Step 2Action
Airtable Search Record
Looks for the matching record in your Airtable table using a filter formula. The step ships unmapped: after import, pick the base and table and write a formula that matches the closed task, for example on a task ID column.
Step 3Logic
Filter Continue If Condition Meet
Continues only when the search's total_records is greater than 0. If Airtable finds no matching record, the run stops here and neither the update nor the Slack post happens.
Step 4Action
Airtable Update Record
Updates the first record the search found, using the record ID already mapped from step 2. Choose the fields to change after import, such as a status or a completed date.
Step 5Action
Slack Send Channel Message
Sends the team a Slack channel message about the closed task. Nothing is mapped in the template, so pick the channel and write the text, mapping in the task name or the Airtable record details.

What you need

FlowMatticCore
Lokalise AccountAccount
Airtable AccountAccount
Slack AccountAccount

After importing, map your own data. To keep the template universal, not every step is pre-filled. Open each step in the builder and connect your accounts and fields (channels, lists, sheets, recipients) before you switch the workflow on.

Make it yours

Changes worth making after you import it.

Store the Lokalise task ID in its own Airtable column and match on it in the filter formula. Titles can repeat across projects, while the ID points to one task.
Write the formula so it can only match one record. The Update Record step edits only the first result, so a loose formula could change the wrong row.
Map the closing date from the trigger into a date field in the Update Record step, so the base shows when each task finished.
Mention the person who owns the record in the Slack message, so the next person in your process sees the update without checking the base.

Questions about this workflow

What happens when the closed Lokalise task has no record in Airtable?

The Filter after the search stops the run, because total_records is 0. Airtable isn't changed and no Slack message is posted. Task History shows the search returned nothing.

Does this create an Airtable record for new tasks?

No. It only updates records you already have. To add records as tasks start, build a separate workflow on the Lokalise Task Created trigger with Airtable's Create Record action.

Does closing one language of a task start a run?

This template uses the Task Closed trigger. FlowMattic's Lokalise integration has a separate Task Language Closed trigger if you want to track each language.

Which Airtable fields does the update change?

Only the ones you map. The template sets the record ID from the search, and you choose the fields and values after import.