Announce GitHub releases in Discord with a generated banner

When you publish a release on GitHub, FlowMattic renders a version banner from your Image Builder template and posts the release name, banner link and release page link to a Discord channel.

GitHub

Image Builder

Discord

Download this workflow Browse more workflows

3 steps Setup ~5 min Used on 3.1k sites Developer & DevOps Free to import

The Announce GitHub releases in Discord with a generated banner workflow on the FlowMattic canvas, with 3 steps across GitHub, Image Builder, Discord — The workflow as it appears in the builder after import. Each step opens for editing.

What this workflow does

Release notes on GitHub reach the people who watch the repository. Your community on Discord often hears later, if at all. This workflow announces each release there with a banner image made for that version.

The GitHub trigger is New Release. It passes on the release data, including its name, tag name and the link to its page on GitHub.

The Image Builder step renders a saved template through Cloudflare Browser Rendering and saves a PNG named release- plus the tag name in your Media Library. It points at template ID 8, so select your banner design and map the release name or tag into its tokens. Then Discord posts a message to the channel you choose: the release name in bold, a line saying it is out, the banner's URL and the GitHub release link.

Open-source project announcements

Maintainers publish a release on GitHub, and the project's Discord announcements channel gets a banner and link without anyone copying notes across.

Game or mod update news

A game studio that ships builds through GitHub releases posts a version banner in its player Discord with each new release.

Plugin or app changelog for customers

A WordPress plugin developer's customer Discord sees each new version as a banner, with the GitHub release page for the full changelog.

How this workflow runs

What happens at each step once the workflow is on, and what you need before you import it.

Step 1Trigger
GitHub New Release
Starts when GitHub reports a new release for your repository. The release name, tag name and release page URL are available to map.
Step 2Action
Image Builder Generate Image from Template
Renders your Image Builder banner template and saves the PNG as release-{tag} in the Media Library. Replace template ID 8 with your design and map the release name or tag into its tokens.
Step 3Action
Discord Send Channel Message
Posts to your chosen Discord channel with the release name in bold, a note that it is out, the banner URL and the GitHub release link. Connect Discord and pick the channel.

What you need

FlowMatticCore
GitHub AccountAccount
Discord AccountAccount

After importing, map your own data. To keep the template universal, not every step is pre-filled. Open each step in the builder and connect your accounts and fields (channels, lists, sheets, recipients) before you switch the workflow on.

Make it yours

Changes worth making after you import it.

Skip pre-releases by adding a Filter after the trigger that continues only when the release's prerelease value is false.
Include the release body in the Discord message if you want the changelog text in the post, not only the link.
The Discord text ships with an emoji at the start. Edit it in the Discord step if your server prefers plain announcements.

Questions about this workflow

Do I need Cloudflare Browser Rendering for the release banner?

Yes. Image Builder renders its HTML templates through Cloudflare Browser Rendering, which has to be configured for FlowMattic before the banner can be generated.

Will pre-releases also be announced in Discord?

As imported, nothing checks for them, so a published pre-release may be posted too. Add a Filter on the release's prerelease value to leave them out.

Where is the GitHub release banner stored?

Image Builder saves the PNG to your WordPress Media Library, not to GitHub. The Discord message links to that file, so it stays available as long as you keep it in the library.