CONTENT CREATION

Gated Discord blast for major-only ReadMe releases

Checks each published ReadMe changelog entry and only fires a Discord announcement plus banner for major releases.

CategoryContent Creation
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerReadMe changelog entry publishedReadMeReadMe
  • LogicClassify release: major vs. minor/patch
  • ActionLog minor/patch entry to Airtable archiveAirtableAirtable
  • ActionGenerate hero banner for major releaseImage generation
  • OutputPost major-release announcement to DiscordDiscordDiscord

What it does

Not every changelog deserves a community ping. This workflow inspects each published ReadMe entry, classifies it as major, minor, or patch, and only generates a banner and Discord announcement when it is a major release. Smaller entries are recorded to an Airtable changelog log instead of spamming the channel.

When to use it

When your ReadMe changelog mixes big launches with routine bug-fix notes and your Discord community only wants to hear about the big ones. Keeps signal high while still archiving everything.

How it works

  1. 1A ReadMe changelog entry is published, firing the trigger.
  2. 2A logic step classifies the entry by tag or semver bump into major vs. minor/patch.
  3. 3If minor or patch, the entry is appended to an Airtable changelog table and the run ends quietly.
  4. 4If major, generate-image builds a hero banner from the release title.
  5. 5A Discord step posts the highlighted announcement with the banner to the community channel.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect ReadMeAPI docs, changelog, auth.
  2. 2
    Connect AirtableBases, tables, views, automations.
  3. 3
    Connect Image generationManaged Nano Banana image renders, metered per image.
  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.