CONTENT CREATION
Turn shipped Linear issues into localized ReadMe changelog drafts
When a Linear issue moves to Done with a customer-facing label, draft a localized release note per locale and stage each as a hidden ReadMe changelog entry.
How it runs
The automated pipeline, trigger to output.
- TriggerLinear issue moved to DoneLinear
- LogicProceed only if customer-facing label present
- ActionDraft and localize note per localeOpenAI
- ActionStage hidden ReadMe changelog entry per localeReadMe
- OutputSlack approval request linking staged draftsSlack
What it does
Listens for Linear issues that reach a Done state and carry a "customer-facing" label. It writes a clear release note from the issue title and description, localizes it for each market, and stages each as a hidden (unpublished) changelog entry in ReadMe. A Slack approval request links every staged entry so a reviewer can publish with one action.
When to use it
Use this when your product changelog lives in ReadMe and your team treats a Linear issue hitting Done as the signal that something shipped. It bridges issue tracking and public docs while keeping a human gate before anything goes live.
How it works
- 1A Linear issue transitioning to Done with the customer-facing label triggers the flow.
- 2The flow checks the label and skips internal-only issues.
- 3An LLM drafts a customer-facing note from the issue summary, then localizes it per configured locale.
- 4Each localized note is created as a hidden ReadMe changelog entry tagged with its locale.
- 5A Slack message requests review and links every staged draft for approval and publish.
Set it up
What you configure once, before turning it on.
- 1Connect LinearIssues, projects, cycles, triage.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect ReadMeAPI docs, changelog, auth.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, 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.