Issues
Start a workflow when GitHub delivers the issues webhook. Use this to coordinate work across your team and other apps.
Developer tools
Connect GitHub to FastHook, start Workflows from repository webhooks, and automate issues, pull requests, repositories, and Actions workflows.
Start a workflow
Choose what starts your automation.
Start a workflow when GitHub delivers the issues webhook. Use this to coordinate work across your team and other apps.
Start a workflow when GitHub delivers the pull_request webhook.
Start a workflow when GitHub delivers one of the subscribed events. Emit every webhook event delivered by the connected GitHub App installation.
Start a workflow when GitHub delivers the branch_protection_configuration webhook.
Start a workflow when GitHub delivers the branch_protection_rule webhook.
Start a workflow when GitHub delivers the check_run webhook.
Start a workflow when GitHub delivers the check_suite webhook.
Start a workflow when GitHub delivers the code_scanning_alert webhook.
Start a workflow when GitHub delivers the commit_comment webhook. Use this to route messages or notify the right people in another app.
Start a workflow when GitHub delivers the create webhook.
Start a workflow when GitHub delivers the custom_property webhook.
Start a workflow when GitHub delivers the custom_property_values webhook.
Start a workflow for the GitHub event types you select. Emit any of the selected GitHub webhook event types from one Source.
Start a workflow when GitHub delivers the delete webhook. Use this to flag related records in another system for review.
Start a workflow when GitHub delivers the dependabot_alert webhook.
Start a workflow when GitHub delivers the deploy_key webhook.
Start a workflow when GitHub delivers the deployment webhook.
Start a workflow when GitHub delivers the deployment_protection_rule webhook.
Start a workflow when GitHub delivers the deployment_review webhook.
Start a workflow when GitHub delivers the deployment_status webhook.
Then take action
Choose what your workflow does in GitHub.
Create an issue in an installed repository in GitHub. Use this to turn an incoming request into work your team can track.
Update an issue or pull request title, body, state, labels, or assignees. Use this to apply changes received from another app to an existing record.
Call another GitHub REST API operation available to the installation. Use this when the integration has no dedicated action for the operation you need; account permissions still apply.
Comment on an issue or pull request.
Open a pull request between repository branches.
Run a workflow_dispatch workflow.
Start with a published template and adapt it to your work.
Create a Linear issue when a new GitHub issue is opened in the selected repositories.
When an issue is opened in GitHub, send its ID, number, title and link as a JSON message to Amazon SQS. Issue bodies and attachments stay in GitHub.
Notify a Discord channel whenever a new GitHub issue is opened in a selected repository.
Keep release reviewers informed with a plain-text email when a GitHub release is published.
Give reviewers an inbox summary when a GitHub pull request is opened.
Let project reviewers follow newly opened GitHub issues from their inbox.
Archive published GitHub release notes as UTF-8 text files in Google Drive.
Create a UTF-8 text file in Google Drive whenever a GitHub pull request is opened.
Create a UTF-8 text file in Google Drive whenever a GitHub issue is opened.
Keep a release register in Google Sheets when a GitHub release is published.
Keep a pull request register in Google Sheets whenever a GitHub PR is opened.
Keep a release journal in Notion: create a child page when a GitHub release is published.
Turn published GitHub releases into Trello cards for release checks and follow-up tasks.
Notify your team when a GitHub release is published.
Notify your team when a GitHub release is published.
Notify your Telegram chat when a GitHub pull request is opened.
Create a Notion review page when a GitHub pull request is opened.
Turn newly opened GitHub pull requests into Trello cards for your review queue.
Notify your team when a GitHub pull request is opened.
Keep an issue register in Google Sheets whenever a new GitHub issue is opened.
Create a Notion triage page when a new GitHub issue is opened.
Notify your Telegram chat when a new GitHub issue is opened.
Keep your team informed when a GitHub issue is opened.
Turn newly opened GitHub issues into Trello cards for your triage queue.
Connection. Install the FastHook GitHub App and grant it access to all required repositories.
Repository access is controlled by the GitHub App installation as well as Source filters.
Use the webhook action field to distinguish opened, edited, closed, and other changes.