GitHub logo
Gmail logo

Workflow template

Email published GitHub releases with Gmail

Email the full release notes when a GitHub release is published. Include its tag, optional title, repository, author, publication time, pre-release flag and source link in a plain-text Gmail message.

How it works

From a published release to the reviewer’s inbox

1 Trigger · 1 Action
GitHub1 · Trigger

Release

Receive release webhooks for the selected repository with Actions filtered to published. Stable releases and published pre-releases are included; unpublished drafts and later edits are excluded.

Gmail2 · Action

Email the release reviewer

Send your fixed recipient a plain-text email with release metadata and the complete release body. The subject contains the tag and title; Gmail keeps a copy in Sent.

The result

A release publication email with the full notes

Release notes are copied as literal Markdown text. The publication event reports a GitHub release; it does not confirm that a deployment succeeded.

Example published-release email

GitHub release v3.0.0: Dresden release handoff — Grüße

A GitHub release was published. Tag: v3.0.0 Title: Dresden release handoff — Grüße Repository: example-studio/release-handbook Author: alex-example Published: 2026-09-17T16:00:00Z Pre-release: false https://github.com/example-studio/release-handbook/releases/tag/v3.0.0 Release notes Fictional release notes for the Dresden team. Grüße "Dresden" — handoff checklist - Improve release review instructions - Confirm support handoff

Fictional release. The release title is optional; the tag remains part of the subject and body. Binary assets, source code and attachments are not copied.

Before activation

Set up your workflow

  1. Select the release repository

    Connect the FastHook GitHub App with repository access, then browse to the repository. Keep published selected in Actions. The prepared filter also includes published pre-releases.

  2. Set the Gmail sender and recipient

    Connect Gmail and enter a fixed recipient in Email the release reviewer. Start with your own address. Review the plain-text message because it includes full release notes; HTML, Cc and Bcc are not configured.

  3. Publish a fictional test release

    Activate and wait for the GitHub trigger to connect, then publish a fictional release in a test repository you selected. Creating only a draft does not send the email. Compare the inbox and Sent copy with the release metadata and notes.

Details and limitations
  • Publication includes pre-releases. The published filter includes both stable releases and published pre-releases, showing the pre-release flag. Drafts, edits, deletions and other release actions do not send another email through this recipe.

  • Release notes are text, not a deployment result. The complete release body remains literal Markdown in plain text. The workflow does not verify deployment success, download assets or source code, or synchronize later note changes. Existing releases are not imported.

  • Copied notes and repeat sends. Recipients can read the copied notes even if they cannot open the private GitHub source. Gmail sending limits apply. Manual reruns, ambiguous provider retries or unpublishing and republishing can send duplicate emails.

Questions about this template

Will publishing a pre-release send an email?

Yes. The prepared published filter includes published pre-releases as well as stable releases. The email shows the pre-release flag; an unpublished draft does not trigger it.

Does the email contain all release notes or just a link?

It includes the full release body as literal Markdown in plain text, alongside tag, optional title, repository, author, publication time, pre-release flag and link. Assets and code are not downloaded.

Does this prove the release deployed successfully?

No. It reports the GitHub release publication event. There is no deployment-status check in this workflow.

Will editing notes or republishing send another email?

Editing notes is excluded by the published filter. Unpublishing and republishing can generate another publication event and another email; manual reruns can also resend it.

Explore connected apps