Issues
Emit an event when GitHub delivers the issues webhook.
Ready-made Workflow
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.
What gets copied
FastHook recreates every Step, route, field mapping, and setting with new IDs in your workspace.
Emit an event when GitHub delivers the issues webhook.
Send rich content, files, a poll, or a reply to a channel.
Before activation
Connect your own GitHub account and review the provider settings used by this Workflow.
Connect your own Discord account and review the provider settings used by this Workflow.
Questions
No. FastHook creates a disconnected Draft. Connect your own GitHub, Discord 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.