CONTENT CREATION
Open translation issues from new keys in a GitHub source locale file
On every push touching the en.json source locale, diff the new keys against existing translations and open a GitHub issue listing strings that need linguist work.
How it runs
The automated pipeline, trigger to output.
- TriggerPush modifies locales/en.json on default branchGitHub
- ActionRead changed locale file at new commitGitHub
- LogicDiff keys to find added or modified strings
- LogicStop if no translatable keys changed
- OutputOpen needs-translation GitHub issueGitHub
What it does
Keeps your translation backlog in sync with code. When a developer adds or changes keys in the source locale file (en.json), it computes which keys are new or modified, then opens a single GitHub issue enumerating every string a linguist must translate, with file path and key.
When to use it
Use it for product UI strings that live in the repo. Engineers add copy in code; this makes sure localization sees those additions the moment they merge, without anyone manually scanning diffs.
How it works
- 1A push to the default branch that modifies locales/en.json fires the trigger.
- 2The flow reads the changed file at the new commit and parses its key/value pairs.
- 3It compares against the last localized snapshot to find added or changed keys.
- 4A branch checks whether any keys actually changed; if none, the run ends quietly.
- 5For the changed set it opens a GitHub issue titled with the commit and key count, labeled needs-translation, listing each key and source string.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 3Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 4Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Content Creation workflows
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.
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.
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.
Weekly: clip last week's top blog paragraph and post to socials
Runs on a weekly schedule, picks the highest-traffic paragraph from the past week's posts, generates one polished B-roll clip with Replicate.
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.
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.