GitHub · Discord
Send new GitHub issues to a Discord channel
Notify a Discord channel whenever a new GitHub issue is opened in a selected repository. Connect the FastHook GitHub App and Discord, browse to the repository, then choose the destination Discord text channel. The Actions filter is prefilled with opened, so edits, comments, closures and reopened issues do not create extra notifications. Each message contains the issue number, title, repository, author and canonical GitHub link. Issue bodies, attachments, labels, assignees and private repository metadata are not copied. The destination bot needs permission to view the channel and send messages. User, role and everyone mentions are disabled, so issue text cannot trigger Discord notifications accidentally. Existing issues are not backfilled; wait for Connected before opening a fictional test issue. The template includes its own fictional English support issue example and keeps non-ASCII text intact. This is a one-way notification rather than a status synchronization. Manual reruns can create duplicate messages.
- 1. GitHub · Issues
- 2. Discord · Notify the issue channel
View template →Use templateGitHub · 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
View template →Use templateGitHub · 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
View template →Use templateGitHub · Gmail
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.
- 1. GitHub · Issues
- 2. Gmail · Email the issue reviewer
View template →Use templateGitHub · Google Drive
Save published GitHub release notes in Google Drive
Archive published GitHub release notes as UTF-8 text files in Google Drive. Each file contains the tag, optional release title, full notes, repository, author, publication time, pre-release flag and original GitHub link. Connect GitHub and Google Drive, browse to a repository and optionally select a destination folder. The Actions filter is prefilled with published; stable releases and published pre-releases are included. Leaving Parent folder empty saves to My Drive. Filenames use repository and release IDs, so tags containing slashes or German characters do not become folder paths. Includes its own fictional English Nürnberg release example. Only new publication events received after activation are processed; existing releases are not imported. Drafts, edits and deleted releases do not create or update files. Markdown remains plain source text; release assets, source code and binaries are not downloaded. This is a release-notes snapshot, not a deployment check or synchronized backup. Files inherit destination folder access; no public sharing is added. Manual reruns or unpublishing and republishing a release can create duplicates.
- 1. GitHub · Release
- 2. Google Drive · Archive GitHub release notes
View template →Use templateGitHub · Google Drive
Save new GitHub pull requests as Google Drive text files
Create a UTF-8 text file in Google Drive whenever a GitHub pull request is opened. Files include the PR title, full description, repository, author, creation time, draft status, source and target branches, and original PR link. Connect GitHub and Google Drive, browse to a repository and optionally select a destination folder. The Actions filter is prefilled with opened; draft PRs are included. Leaving Parent folder empty saves to My Drive. Filenames use the repository ID and PR number. Includes its own fictional English Freiburg example with German characters. Only new opened events received after activation are processed; existing PRs are not imported. Edits, new commits, reviews, closed and reopened PRs do not create or update files. Markdown remains plain source text; code changes, comments and linked attachments are not downloaded. This is a one-time snapshot, not a code backup, reviewer assignment or two-way synchronization. Files inherit destination folder access; no public sharing is added. Manual reruns can create duplicate files.
- 1. GitHub · Pull Request
- 2. Google Drive · Save GitHub pull request as a text file
View template →Use templateGitHub · Google Drive
Save new GitHub issues as Google Drive text files
Create a UTF-8 text file in Google Drive whenever a GitHub issue is opened. Files include the issue title, full description, repository, author, creation time and original issue link. Connect GitHub and Google Drive, browse to a repository and optionally select a destination folder. The Actions filter is prefilled with opened. Leaving Parent folder empty saves to My Drive. Each filename uses the repository ID and issue number to distinguish issues across repositories. Includes its own fictional English Leipzig example. Only new opened events received after activation are processed; existing issues are not imported. Edits, comments, closed and reopened issues do not create or update files. Markdown remains plain source text; linked attachments are not downloaded. This is a one-time snapshot, not an issue backup or two-way synchronization. Files inherit destination folder access; no public sharing is added. Manual reruns can create duplicate files.
- 1. GitHub · Issues
- 2. Google Drive · Save GitHub issue as a text file
View template →Use templateGitHub · Google Sheets
Log published GitHub releases in Google Sheets
Keep a release register in Google Sheets when a GitHub release is published. Append Values writes Release tag, Title, Repository, Author, Release URL, Published at (UTC) and Pre-release into columns A-G in that order. Connect the FastHook GitHub App and Google Sheets, browse to the repository, then select a destination spreadsheet and worksheet. The Actions filter is prefilled with published. Both stable releases and published pre-releases are included. Draft releases, edits and deleted releases do not add rows. Headers are optional; an empty worksheet works immediately. Includes an independent fictional English release example. RAW input keeps titles starting with an equals sign as text. Only new publication events after activation are processed; existing releases are not imported and later changes are not synchronized. This is a release register, not deployment verification. Release notes, assets and source code are not copied. Select a worksheet with appropriate access for repository details. Manual reruns or unpublishing and republishing a release can create duplicate rows.
- 1. GitHub · Release
- 2. Google Sheets · Append published release to the register
View template →Use templateGitHub · Google Sheets
Log new GitHub pull requests in Google Sheets
Keep a pull request register in Google Sheets whenever a GitHub PR is opened. Append Values writes PR number, Title, Repository, Author, PR URL, Created at (UTC), Source branch, Target branch and Draft into columns A-I in that order. Connect the FastHook GitHub App and Google Sheets, browse to the repository, then choose a destination spreadsheet and worksheet. The Actions filter is prefilled with opened. Draft PRs are included with their draft flag. Edits, commits, reviews, closed and reopened PRs do not add another row. Headers are optional: an empty worksheet works immediately, or add your own header row. Includes an independent fictional English example with German characters. Only new events after activation are processed; existing PRs are not imported and later status changes are not synchronized. RAW input keeps titles beginning with an equals sign as text. PR bodies, code, comments and attachments are not copied. Select a worksheet with appropriate access for repository details. Manual reruns can create duplicate rows.
- 1. GitHub · Pull Request
- 2. Google Sheets · Append pull request to the register
View template →Use templateGitHub · Notion
Create Notion pages for published GitHub releases
Keep a release journal in Notion: create a child page when a GitHub release is published. Each page includes the release tag and optional title, repository, author, publication time, pre-release flag, clickable GitHub link, and Review notes and Follow-up sections. Connect the FastHook GitHub App and Notion, browse to the repository to track, then choose an accessible parent Notion page. The Actions filter is prefilled with published. Both stable releases and published pre-releases are included. Draft releases, edits and deleted releases do not create pages. Includes an independent fictional English release example. Release notes, assets and source code are not copied. Only new publication events after activation are processed; existing releases are not imported. This creates child pages, not database rows or deployment verification, and does not synchronize later changes. Page details become visible to people with access to the selected parent. Manual workflow reruns or unpublishing and republishing a release can create duplicates.
- 1. GitHub · Release
- 2. Notion · Create a release journal page
View template →Use templateGitHub · Trello
Create Trello follow-up cards for published GitHub releases
Turn published GitHub releases into Trello cards for release checks and follow-up tasks. Connect the FastHook GitHub App and Trello, browse to the repository to track, then select a destination board and list. Each card includes the release tag, optional title, repository, author, pre-release flag, publication time and GitHub link. The Actions filter is prefilled with published. Both stable releases and published pre-releases are included. Draft releases, edits and deleted releases do not create cards. Includes an independent fictional English release example. Release notes, assets and source code are not copied. Only new publication events after activation are processed; existing releases are not imported. This creates a tracking card; it does not deploy code, verify deployment or synchronize later changes. Card details become visible to members of the destination board. Manual workflow reruns or unpublishing and republishing a release can create duplicate cards.
- 1. GitHub · Release
- 2. Trello · Create release follow-up card
View template →Use templateGitHub · Telegram Bot
Send Telegram alerts for published GitHub releases
Notify your team when a GitHub release is published. Connect the FastHook GitHub App and Telegram, browse to the repository to track, then browse to a chat or channel where the FastHook bot can post. Messages include the repository, release tag, optional release title, author, pre-release flag and release link. The Actions filter is prefilled with published. Both stable releases and published pre-releases are included. Draft releases, edits and deleted releases do not send alerts. Includes an independent fictional English release example. Release notes, assets and source code are not copied. Messages use plain text with link previews disabled. Processes new publication events after activation, not existing releases. This is a notification only; it does not deploy code or prove deployment succeeded. Details become visible to members of the destination Telegram chat or channel. Manual workflow reruns or unpublishing and republishing a release can duplicate notifications.
- 1. GitHub · Release
- 2. Telegram Bot · Notify the team about a published release
View template →Use templateGitHub · Slack
Send Slack alerts for published GitHub releases
Notify your team when a GitHub release is published. Connect the FastHook GitHub App and Slack, browse to the repository to track, then choose a channel where the FastHook bot can post. Messages include the repository, release tag, optional release title, author, pre-release flag and release link. The Actions filter is prefilled with published. Both stable releases and published pre-releases are included. Draft releases, edits and deleted releases do not send alerts. Includes an independent fictional English release example. Release notes, assets and source code are not copied. Messages use plain text with link previews disabled. Processes new publication events after activation, not existing releases. This is a notification only; it does not deploy code or prove deployment succeeded. Details become visible to members of the destination Slack channel. Manual workflow reruns or unpublishing and republishing a release can duplicate notifications.
- 1. GitHub · Release
- 2. Slack · Notify the team about a published release
View template →Use templateGitHub · Telegram Bot
Send Telegram alerts for new GitHub pull requests
Notify your Telegram chat when a GitHub pull request is opened. Connect the FastHook GitHub App, browse to the repository to track, and choose a Telegram chat where the FastHook bot can post. The prepared message includes the PR title, number, repository, author, source and target branches, draft flag and GitHub link. The Actions filter is prefilled with opened. Draft PRs are included. Edits, new commits, reviews, closed and reopened PRs do not send another notification. Includes an independent fictional English example with German characters. Messages use plain text and disable link previews. PR bodies, code changes and attachments are not copied. Processes new webhook events after activation, not existing PRs. This is a one-way notification, not a status sync or reviewer assignment. Mapped PR details become visible to members of the destination chat. Manual workflow reruns can duplicate messages.
- 1. GitHub · Pull Request
- 2. Telegram Bot · Notify the Telegram pull request chat
View template →Use templateGitHub · Notion
Create Notion review pages for new GitHub pull requests
Create a Notion review page when a GitHub pull request is opened. Each child page includes the PR title and number, repository, author, source and target branches, a clickable GitHub link, and Review notes and Follow-up sections. Connect the FastHook GitHub App and Notion, browse to the repository to track, then choose an accessible parent Notion page. The Actions filter is prefilled with opened. Draft PRs are included. Edits, new commits, reviews, closed and reopened PRs do not create another page. Includes an independent fictional English example with German characters. Only new webhook events received after activation are processed; existing PRs are not imported. This is one-way child page creation, not database rows, reviewer assignment or status synchronization. PR bodies, code changes, comments and attachments are not copied. Page details become visible to people with access to the selected Notion parent. Manual workflow reruns can create duplicates.
- 1. GitHub · Pull Request
- 2. Notion · Create a Notion pull request review page
View template →Use templateGitHub · Trello
Create Trello review cards from new GitHub pull requests
Turn newly opened GitHub pull requests into Trello cards for your review queue. Each card includes the PR title, number, repository, author, source and target branches, draft flag, creation time and GitHub link. Connect the FastHook GitHub App and Trello, browse to the repository to track, then choose a destination board and list. The Actions filter is prefilled with opened. Draft pull requests are included, with their draft flag shown in the description. Edits, new commits, reviews, closed and reopened PRs do not create another card. Includes an independent fictional English review example. Only new webhook events after activation are processed; existing PRs are not imported. This is one-way card creation, not review assignment or status synchronization. PR bodies, code changes and attachments are not copied. Card details become visible to members of the destination board. Manual workflow reruns can create duplicate cards.
- 1. GitHub · Pull Request
- 2. Trello · Create pull request review card
View template →Use templateGitHub · Slack
Send new GitHub pull requests to Slack
Notify your team when a GitHub pull request is opened. Connect the FastHook GitHub App and Slack, browse to the repository to track, and choose a channel where the FastHook bot can post. The Actions filter is prefilled with opened. Messages include the PR title, number, author, source and target branches, draft flag and link. Draft pull requests are included. Edits, new commits, reviews, closed and reopened PRs do not create another alert. Includes an independent fictional English pull request example. PR bodies, code changes and attachments are not copied. Messages use plain text with link previews disabled. Processes new webhook events after activation, not existing PRs. This is a one-way alert, not a review assignment or status sync. Details become visible to members of the destination channel. Manual workflow reruns can duplicate messages.
- 1. GitHub · Pull Request
- 2. Slack · Notify the team about a new pull request
View template →Use templateGitHub · Google Sheets
Log new GitHub issues in Google Sheets
Keep an issue register in Google Sheets whenever a new GitHub issue is opened. Append Values writes Issue number, Title, Repository, Author, Issue URL and Created at (UTC) into columns A-F in that order. Connect the FastHook GitHub App and Google Sheets, browse to the repository, then choose a destination spreadsheet and worksheet. The Actions filter is prefilled with opened: edits, comments, closed and reopened issues do not add rows. Headers are optional; an empty worksheet works immediately, or add your own header row. Includes a fictional English example with German characters. Only new events received after activation are processed; existing issues are not imported and later status changes are not synchronized. Values use RAW input, so issue titles starting with an equals sign remain text. Issue bodies, comments and attachments are not copied. Select a worksheet with appropriate access for the repository details.
- 1. GitHub · Issues
- 2. Google Sheets · Append issue to the register
View template →Use templateGitHub · Notion
Create Notion triage pages for new GitHub issues
Create a Notion triage page when a new GitHub issue is opened. Each child page includes the issue title, repository, author and source link, plus Triage and Notes sections for your team. Connect the FastHook GitHub App and Notion, select a repository, then browse to an accessible parent Notion page. The Actions filter is prefilled with opened, so edits, comments, closed and reopened issues do not create pages. Includes a fictional English example with German characters. Only new events received after activation are processed; existing issues are not imported. This is one-way page creation, not status synchronization. Issue bodies, comments and attachments are not copied. Titles and repository details become visible to everyone with access to the selected Notion parent. This creates child pages, not database rows.
- 1. GitHub · Issues
- 2. Notion · Create a Notion issue triage page
View template →Use templateGitHub · Telegram Bot
Send Telegram alerts for new GitHub issues
Notify your Telegram chat when a new GitHub issue is opened. Connect the FastHook GitHub App, browse to the repository to track, and choose a Telegram chat where the FastHook bot can post. The prepared message includes the issue title, number, repository, author and link. The Actions filter is already set to opened, so edits, comments, closed and reopened issues do not send another notification. Includes a fictional English issue example with German characters. Messages use plain text and disable link previews; issue bodies and attachments are not copied. Processes new webhook events after activation, not existing issues. This is a one-way notification, not a status sync. Mapped issue details become visible to members of the destination chat.
- 1. GitHub · Issues
- 2. Telegram Bot · Notify the Telegram issue chat
View template →Use templateGitHub · Slack
Send new GitHub issues to a Slack channel
Keep your team informed when a GitHub issue is opened. FastHook posts the issue title, number, repository, author and source link in your chosen Slack channel. Connect the FastHook GitHub App and Slack, select the repository to track, then choose a channel where the FastHook bot can post. The Actions filter is prefilled with opened; edits, comments, closed and reopened issues do not send another message. Includes a fictional English support issue example. Messages use plain text with link previews disabled. Issue bodies and attachments are not copied. Processes new webhook events after activation, not existing issues. This is a one-way notification, not a threaded status sync. Issue details become visible to members of the destination channel.
- 1. GitHub · Issues
- 2. Slack · Notify the issue channel
View template →Use templateGitHub · Trello
Create Trello cards from new GitHub issues
Turn newly opened GitHub issues into Trello cards for your triage queue. Each card includes the issue title, number, repository, author and a link back to GitHub. Connect the FastHook GitHub App and Trello, select the repository you want to track, then choose a destination board and list. The Actions filter is prefilled with opened: edits, comments, closed and reopened issues do not create cards. Includes a fictional English issue example. Only new webhook events received after activation are processed; existing issues are not imported. This is one-way card creation, not status synchronization. Issue bodies and attachments are not copied. Issue titles and repository details become visible to members of the destination board.
- 1. GitHub · Issues
- 2. Trello · Create issue triage card
View template →Use template
