CONTENT CREATION

Publish Changelog and Broadcast Highlights to Discord

On a new release tag, this builds and deploys the changelog microsite, then posts a short highlight summary with the live link to your community Discord.

CategoryContent Creation
Enginesim
Difficultybeginner
Triggerevent
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew git tag pushedGitHubGitHub
  • ActionDraft changelog from merged PRsOpenAI
  • ActionCommit entry and deploy micrositeVercelVercel
  • ActionCondense entry into 3-bullet highlightOpenAI
  • OutputBroadcast highlight and link to DiscordDiscordDiscord

What it does

Closes the loop between shipping and announcing. It assembles the changelog from PRs merged since the last tag, deploys it to the microsite, then writes a tight three-bullet highlight summary and broadcasts it to your community Discord channel with a link to the full notes.

When to use it

Use it when you have an engaged community that wants to hear about releases where they already hang out, and you do not want to maintain a separate announcement workflow from your changelog.

How it works

  1. 1A new tag push triggers the flow.
  2. 2It gathers the PRs merged since the previous tag and drafts the full changelog entry.
  3. 3The entry is committed and the microsite is redeployed on Vercel, yielding a live URL.
  4. 4A separate LLM step condenses the entry into a three-bullet, community-friendly highlight.
  5. 5The highlight plus the live changelog link is posted to the configured Discord channel as the final output.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect GitHubRepos, issues, pull requests, actions.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect VercelDeploys, runtime logs, analytics.
  4. 4
    Connect DiscordCommunity channels + voice + bots.
  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.