Store new Cockpit localized project saves as rows in Airtable
Each Localize Project Save event from Cockpit creates a new record in Airtable, so you keep a log of localization project saves in a base your team can filter and review.
Cockpit
Airtable2 steps Setup ~5 min Used on 1.2k sites Free to import
What this workflow does
Localization work in a headless CMS is hard to follow from outside it. Project managers and translators who don't use Cockpit still want to know when a project was saved. An Airtable base gives them a record they can filter, comment on and share.
The Cockpit trigger, Localize Project Save, fires on that Cockpit event, which FlowMattic describes as a project being saved locally inside Cockpit. FlowMattic passes the event's data to Airtable, and the Create Record action adds a record to the table you choose. Map the project details from the trigger to your Airtable fields, after a test save shows what Cockpit sends.
Each save creates a new record. Saving the same project again adds another one, so the table works as a history of saves rather than one record per project.
Translation agency activity log
An agency managing a client's Cockpit site keeps an Airtable log of each localization project save to review with the client.
Release checklists for multilingual sites
Before a launch, the project manager checks the Airtable table to confirm that each language project was saved recently.
Freelance translator hours
Saves recorded in Airtable give a rough timeline of when translation work happened, useful when checking a freelancer's invoice.
How this workflow runs
What happens at each step once the workflow is on, and what you need before you import it.
Cockpit Localize Project SaveFires on Cockpit's Localize Project Save event. The project data from the save is passed on for mapping in Airtable.
- Airtable Create Record
Creates a new record in the Airtable table you select. Connect your Airtable account and map Cockpit's project details to the fields in your table.
What you need
- FlowMatticCore
- Cockpit AccountAccount
- Airtable 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.
- Add a created-time field in your Airtable table, so every record shows when the save happened without mapping a date.
- Build a second workflow on Cockpit's Save Content Item trigger if you also want content saves logged in another table.
- Make one save in Cockpit right after import so the trigger captures sample data, then map it to your Airtable fields.
Questions about this workflow
Does saving the same Cockpit project twice update one Airtable record?
No. Each save creates a new record. The workflow uses Create Record and has no step that finds or updates existing records.
Which Airtable base and table receive the records?
The ones you select in the Create Record step after import. Set up the fields in that table before you map.
Are Cockpit content items and pages included?
No. This workflow uses Localize Project Save. Cockpit's Save Content Item and Save Pages Page triggers cover those in other workflows.
What do I need to connect for Cockpit and Airtable?
Your Cockpit account for the trigger and an Airtable account with access to the base you want to fill.
More Spreadsheets & Data workflows
Other ready-to-import templates from the same category.
Import this workflow into your WordPress site
Download the JSON, import it from the Workflows screen and connect your accounts. Every run stays on your server, with no per-task fees.
30-day money-back guarantee Unlimited workflows and runs Self-hosted