CONTENT CREATION
Turn a CMS publish webhook into a localization packet and locale tasks
Receives a publish webhook from your CMS, fetches the published article, generates a translation brief and glossary.
How it runs
The automated pipeline, trigger to output.
- TriggerCMS publish webhook receivedHTTP webhook
- LogicIgnore drafts and locale-less events
- ActionFetch published article contentHTTP webhook
- ActionGenerate per-locale brief and glossaryOpenAI
- ActionCreate Linear task per localeLinear
- OutputReturn task links to the callerHTTP webhook
What it does
Connects your publishing pipeline directly to localization. The instant an article is published, a webhook hands the content to this flow, which prepares a translation packet (source text plus a generated glossary and tone notes) and opens a tracked task for each target locale.
When to use it
Use this when localization should start automatically on publish rather than waiting for someone to notice. It is ideal for high-cadence content teams where translation must trail publishing closely.
How it works
- 1The CMS sends a publish webhook containing the article ID and target locales.
- 2The flow validates the payload and ignores events that are drafts or carry no locales.
- 3It fetches the full published content from the source of record.
- 4OpenAI produces a per-locale brief: source body, extracted glossary terms, and tone guidance.
- 5A Linear task is created per locale in the Localization project with the brief and a default SLA due date.
- 6The created task links are returned to the webhook caller so the CMS can show localization status inline.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect LinearIssues, projects, cycles, triage.
- 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.