CONTENT CREATION

Linear completed cycle to multi-channel release notes

When a Linear cycle closes, pulls every shipped issue, drafts release notes, then fans them out to Notion for the record and Slack for the team.

CategoryContent Creation
EngineSim + Paperclip
Difficultyadvanced
Triggerevent
Steps6
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerLinear cycle completedLinearLinear
  • ActionFetch issues marked Done in the cycleLinearLinear
  • LogicFlag major features for human review
  • ActionDraft grouped release notesOpenAI
  • ActionArchive notes to Notion release pageNotionNotion
  • OutputPost summary with review flags to SlackSlack

What it does

Uses your Linear cycle as the release boundary. When a cycle completes, it gathers all issues marked Done, turns them into customer-facing release notes, archives the notes in Notion, and posts a summary to Slack. Issues tagged as major features are flagged so a human can approve copy before it reaches customers.

When to use it

Use it when Linear drives your planning and a cycle maps to a release. Good for product teams that want the changelog generated from the work tracker itself, not from Git history.

How it works

  1. 1A completed Linear cycle triggers the flow.
  2. 2The flow fetches every issue moved to Done in that cycle.
  3. 3A decision step splits items: major-labeled features route to a review note, everything else flows straight through.
  4. 4An LLM step writes grouped, polished release notes from the issue titles and descriptions.
  5. 5The notes are saved to a Notion release page, and a summary with the review flags is posted to Slack.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect LinearIssues, projects, cycles, triage.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect NotionPages, databases, comments.
  4. 4
    Connect SlackChannels, DMs, threads, mentions.
  5. 5
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  6. 6
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  7. 7
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.