Issues
Emit an event when GitHub delivers the issues webhook.
→
Ready-made Workflow
Email new GitHub issues with Gmail
Let project reviewers follow newly opened GitHub issues from their inbox. Each email includes the issue number and title, repository, author, creation time and source link. Connect the FastHook GitHub App, browse to the repository to watch, connect Gmail and enter a fixed recipient address. The opened action filter is already selected; edits, comments, closed and reopened issues do not send another email. Includes its own fictional Bremen documentation example with German Unicode. Emails are sent from your connected Gmail account and appear in Sent. Issue bodies, attachments and labels are not copied. This workflow processes new webhook events after activation, not existing issues, and does not synchronize later changes or replies. The recipient can read the issue title and repository details; opening a private issue still requires GitHub access. Messages use plain text, with no HTML, Cc or Bcc configured. Gmail sending limits apply. Manual reruns or retries after ambiguous provider failures can resend a notification. Use your own email address for the first test.
Use this templateCreates a new Draft · no credentials copied
What gets copied
The working graph, not another user's secrets
FastHook recreates every Step, route, field mapping, and setting with new IDs in your workspace.
Email the issue reviewer
Send an RFC 5322 email from the connected mailbox.
Before activation
Connect your accounts in the Draft
GitHub
Connect your own GitHub account and review the provider settings used by this Workflow.
Gmail
Connect your own Gmail account and review the provider settings used by this Workflow.
Explore connected apps
Related Workflow templates
GitHub · Gmail
Email new GitHub pull requests with Gmail
Give reviewers an inbox summary when a GitHub pull request is opened. Each email includes the PR number and title, repository, author, source and target branches, draft flag, creation time and source link. Connect the FastHook GitHub App, browse to the repository to watch, connect Gmail and enter a fixed recipient address. The opened action filter is already selected; draft PRs are included. Edits, new commits, reviews, closed and reopened PRs do not send another email. Includes its own fictional Hamburg onboarding example with German Unicode. Emails are sent from your connected Gmail account and appear in Sent. PR bodies, code changes, comments and attachments are not copied. This processes new webhook events after activation, not existing PRs, and does not assign reviewers or synchronize review status. The recipient can read the title and branch details; opening a private PR still requires GitHub access. Messages use plain text, with no HTML, Cc or Bcc configured. Gmail sending limits apply. Manual reruns or retries after ambiguous provider failures can resend a notification. Use your own email address for the first test.
- 1. GitHub · Pull Request
- 2. Gmail · Email the pull request reviewer
GitHub · Gmail
Email published GitHub releases with Gmail
Keep release reviewers informed with a plain-text email when a GitHub release is published. Each message contains the tag, optional title, repository, author, publication time, pre-release flag, original link and complete release notes. Connect the FastHook GitHub App, browse to the repository to watch, connect Gmail and enter a fixed recipient address. The published action filter is already selected; published pre-releases are included. Drafts, edits, deletions and other release actions do not send another email. Includes its own fictional English Dresden handoff example with German Unicode. Only new publication webhooks after activation are processed, not existing releases. This does not confirm deployment success, download assets or synchronize later note changes. Release notes remain literal Markdown in plain text; binary assets, source code and attachments are excluded. Emails are sent from your connected Gmail account and appear in Sent. Recipients can read the copied notes; opening a private release still requires GitHub access. No public sharing, HTML, Cc or Bcc is configured. Gmail sending limits apply. Manual reruns, ambiguous provider retries, or unpublishing and republishing can send duplicate emails. Use your own email address for the first test.
- 1. GitHub · Release
- 2. Gmail · Email the release reviewer
Questions
Template FAQ
Does the template copy someone else's credentials?
No. FastHook creates a disconnected Draft. Connect your own GitHub, Gmail accounts before activation.
Can I change the Steps and mappings?
Yes. The copied Workflow is an editable Draft. Review every Step, input, mapping, and route before you activate it.
What is copied into my workspace?
FastHook recreates the Trigger configuration, Action Steps, routes, and mappings with new IDs. Provider accounts, credentials, and secrets are never copied.
When does the Workflow start running?
Only after you connect the required accounts, finish the configuration, and explicitly activate the Draft.