Issues
Emit an event when GitHub delivers the issues webhook.
→
Ready-made Workflow
Send Telegram alerts for new GitHub issues
Notify your Telegram chat when a new GitHub issue is opened. Connect the FastHook GitHub App, browse to the repository to track, and choose a Telegram chat where the FastHook bot can post. The prepared message includes the issue title, number, repository, author and link. The Actions filter is already set to opened, so edits, comments, closed and reopened issues do not send another notification. Includes a fictional English issue example with German characters. Messages use plain text and disable link previews; issue bodies and attachments are not copied. Processes new webhook events after activation, not existing issues. This is a one-way notification, not a status sync. Mapped issue details become visible to members of the destination chat.
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.
Notify the Telegram issue chat
Send a text message through a connected Telegram bot.
Before activation
Connect your accounts in the Draft
GitHub
Connect your own GitHub account and review the provider settings used by this Workflow.
Telegram Bot
Connect your own Telegram Bot account and review the provider settings used by this Workflow.
Explore connected apps
Related Workflow templates
GitHub · Telegram Bot
Send Telegram alerts for published GitHub releases
Notify your team when a GitHub release is published. Connect the FastHook GitHub App and Telegram, browse to the repository to track, then browse to a chat or 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 Telegram chat or channel. Manual workflow reruns or unpublishing and republishing a release can duplicate notifications.
- 1. GitHub · Release
- 2. Telegram Bot · Notify the team about a published release
GitHub · Telegram Bot
Send Telegram alerts for new GitHub pull requests
Notify your Telegram chat when a GitHub pull request is opened. Connect the FastHook GitHub App, browse to the repository to track, and choose a Telegram chat where the FastHook bot can post. The prepared message includes the PR title, number, repository, author, source and target branches, draft flag and GitHub link. The Actions filter is prefilled with opened. Draft PRs are included. Edits, new commits, reviews, closed and reopened PRs do not send another notification. Includes an independent fictional English example with German characters. Messages use plain text and disable link previews. PR bodies, code changes and attachments are not copied. Processes new webhook events after activation, not existing PRs. This is a one-way notification, not a status sync or reviewer assignment. Mapped PR details become visible to members of the destination chat. Manual workflow reruns can duplicate messages.
- 1. GitHub · Pull Request
- 2. Telegram Bot · Notify the Telegram pull request chat
Questions
Template FAQ
Does the template copy someone else's credentials?
No. FastHook creates a disconnected Draft. Connect your own GitHub, Telegram Bot 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.