Notify the team about a published release
Send text, Block Kit content, attachments, or a thread reply to a channel.
Ready-made Workflow
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.
What gets copied
FastHook recreates every Step, route, field mapping, and setting with new IDs in your workspace.
Send text, Block Kit content, attachments, or a thread reply to a channel.
Before activation
Connect your own GitHub account and review the provider settings used by this Workflow.
Connect your own Slack account and review the provider settings used by this Workflow.
Questions
No. FastHook creates a disconnected Draft. Connect your own GitHub, Slack accounts before activation.
Yes. The copied Workflow is an editable Draft. Review every Step, input, mapping, and route before you activate it.
FastHook recreates the Trigger configuration, Action Steps, routes, and mappings with new IDs. Provider accounts, credentials, and secrets are never copied.
Only after you connect the required accounts, finish the configuration, and explicitly activate the Draft.