GitHub logo
→Slack logo

Ready-made Workflow

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.

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.

Step 1 · GitHub · Trigger

Issues

Emit an event when GitHub delivers the issues webhook.

Step 2 · Slack

Notify the issue channel

Send text, Block Kit content, attachments, or a thread reply to a channel.

Before activation

Connect your accounts in the Draft

1

GitHub

Connect your own GitHub account and review the provider settings used by this Workflow.

2

Slack

Connect your own Slack account and review the provider settings used by this Workflow.

Explore connected apps

Related Workflow templates

GitHub · 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. 1. GitHub · Release
  2. 2. Slack · Notify the team about a published release
View template →Use template

GitHub · 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. 1. GitHub · Pull Request
  2. 2. Slack · Notify the team about a new pull request
View template →Use template

Questions

Template FAQ

Does the template copy someone else's credentials?

No. FastHook creates a disconnected Draft. Connect your own GitHub, Slack 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.