CONTENT CREATION

Draft Notion changelog entries from merged feature PRs

When a PR labeled as a user-facing feature merges, the agent writes a plain-English changelog entry, appends it to your Notion changelog.

CategoryContent Creation
Enginepaperclip
Difficultybeginner
Triggerevent
Steps6
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerFeature pull request mergedGitHubGitHub
  • LogicFilter to user-facing feature label
  • ActionRead PR details and diffGitHubGitHub
  • ActionDraft customer-readable changelog entry
  • ActionCreate draft row in Notion changelogNotionNotion
  • OutputSend to Slack for sign-offSlack

What it does

Listens for merged pull requests that carry a user-facing feature label, then turns the technical change into a customer-readable changelog entry. It drafts the entry into your Notion changelog database and routes it to the team for a quick approval rather than publishing silently.

When to use it

Use it when your changelog lives in Notion and falls behind because writing entries is nobody's job. Best for product and growth teams who want every shipped feature captured in customer-friendly language with a human gate before it goes out.

How it works

  1. 1A merged pull request fires the trigger.
  2. 2A filter step keeps only PRs tagged with a user-facing feature label.
  3. 3The agent reads the PR title, description, and diff to understand what shipped.
  4. 4It drafts a concise, jargon-free changelog entry with a title and summary.
  5. 5It creates the entry as a draft row in the Notion changelog database.
  6. 6It sends the draft to Slack with approve and edit actions for sign-off.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect GitHubRepos, issues, pull requests, actions.
  2. 2
    Connect NotionPages, databases, comments.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    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.