Notify the issue channel
Send text, Block Kit content, attachments, or a thread reply to a channel.
→
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.
Before activation
Connect your accounts in the Draft
GitHub
Connect your own GitHub account and review the provider settings used by this Workflow.
Slack
Connect your own Slack account and review the provider settings used by this Workflow.
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.