CHATBOTS

Broadcast new ReadMe changelog entries to Discord

On a schedule, checks ReadMe for newly published changelog and doc updates and posts a formatted digest to a Discord announcements channel so developers stay current.

CategoryChatbots
Enginesim
Difficultyintermediate
Triggerschedule
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerScheduled poll (hourly)
  • ActionFetch recent ReadMe changelog and doc updatesReadMeReadMe
  • LogicFilter to items newer than stored watermark
  • ActionCompose formatted update digestOpenAI
  • OutputPost digest to Discord announcements channelDiscordDiscord
  • ActionUpdate last-seen watermark in PostgresPostgreSQLPostgres

What it does

Polls ReadMe on a schedule for newly published changelog entries and updated documentation pages, formats them into a clean digest, and posts it to a Discord announcements channel. Developers in your community learn about API changes and new docs without leaving Discord.

When to use it

Run this when your docs and changelog ship updates that your developer community needs to know about, and you want announcements to be automatic and consistently formatted rather than copy-pasted by hand.

How it works

  1. 1A schedule (for example hourly) triggers the run.
  2. 2The flow pulls recent ReadMe changelog entries and recently updated pages.
  3. 3A logic step filters to only items published since the last run, using a stored watermark in Postgres.
  4. 4An LLM step writes a concise, friendly digest with links for each update.
  5. 5The flow posts the digest to the Discord announcements channel.
  6. 6It updates the watermark in Postgres so the next run starts where this one ended.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect ReadMeAPI docs, changelog, auth.
  2. 2
    Connect DiscordCommunity channels + voice + bots.
  3. 3
    Connect PostgresAny Postgres URL — query, write, migrate.
  4. 4
    Connect OpenAIModels, embeddings, files.
  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.