CONTENT CREATION
Sync linguist-approved strings into target locale files via GitHub PR
When a linguist board card flips to Approved, write the approved translation into the matching target locale file and open a GitHub pull request grouping the day's approved…
How it runs
The automated pipeline, trigger to output.
- TriggerLinguist-board card set to ApprovedNotion
- ActionRead key, language, and approved stringNotion
- LogicValidate locale file and key exist
- ActionWrite translation to target locale on branchGitHub
- OutputOpen PR and notify #localizationGitHub
What it does
Closes the loop from review back to code. When a string is approved on the linguist board, it locates the right target locale file by key and language, inserts the approved translation, and bundles approvals into a pull request for engineering to merge.
When to use it
Use it once translations are reviewed and you want them in the product without manual file edits. It guarantees the approved text, not a stale draft, is what lands in the repo, with a reviewable PR trail.
How it works
- 1A linguist-board card status change to Approved fires the trigger.
- 2The flow reads the card to get the key, target language, and approved string.
- 3A check confirms the target locale file and key exist; mismatches route to a Slack alert instead of a write.
- 4It updates the locale file value on a translations branch, batching with other approvals from the same window.
- 5It opens or updates a GitHub PR listing the approved keys and notifies #localization with the PR link.
Set it up
What you configure once, before turning it on.
- 1Connect NotionPages, databases, comments.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Content Creation workflows
Build a Dropbox B-roll library from exported blog drafts
Triggers when a new blog draft file lands in a Dropbox folder, generates a Replicate B-roll clip for each paragraph.
Generate B-roll clips when a blog post is marked Ready in Notion
Watches a Notion blog database for posts flipped to 'Ready', splits the body into paragraphs, and generates a short B-roll video clip for each paragraph with Replicate.
On-demand: turn a blog URL into narrated B-roll clips
Accepts a blog URL via webhook, scrapes the article, generates a B-roll clip per paragraph with Replicate and a voiceover with ElevenLabs.
On-Demand Screenshot Freshness Report from a Slack Command
A writer requests a freshness check in Slack for a specific docs page; the workflow inspects every screenshot on that page, scores each by age and version gap.
Sync a Figma master frame into localized hero renders
Pulls the current master hero frame and its text layers from Figma, generates a localized image variant for each locale defined in Airtable.
Research-driven localized hero banners tuned per market
An agent researches cultural and seasonal cues for each target market, adapts the master hero concept to fit local context, generates a tailored image per locale.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.