CONTENT CREATION
Split a localization request into per-locale Asana tasks
When a localization request comes in via webhook, splits the source copy by target locale and creates one Asana task per language under a parent project.
How it runs
The automated pipeline, trigger to output.
- TriggerLocalization request received via webhookHTTP webhook
- LogicValidate payload and expand target locales into work items
- ActionCreate one Asana subtask per locale under the parent projectAsana
- OutputPost task summary to the localization Slack channelSlack
What it does
Turns a single localization request into a fan-out of trackable translation tasks. It reads the source copy and the list of requested locales, then creates one Asana subtask per locale so each translator owns a clear, isolated unit of work.
When to use it
Use it when a content or product team submits new copy that needs to ship in several languages and you want every locale tracked separately instead of as one giant ticket. Ideal for marketing pages, release notes, and UI string sets.
How it works
- 1A webhook receives the request payload (source text, source locale, and an array of target locales).
- 2A logic step validates the payload and expands the target-locale array into individual work items.
- 3For each locale, an Asana action creates a subtask under the request's parent project, titled by locale, with the source copy and word count in the description.
- 4A Slack message posts a summary to the localization channel listing every task created and its assignee placeholder.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect AsanaTasks, projects, milestones — everywhere.
- 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.