Issues
Receive issue events from the selected repository, with Actions already filtered to opened. Later changes and existing issues are outside this recipe.
Workflow template
Send newly opened GitHub issues to your Telegram chat. The FastHook bot posts the issue number, title, repository, author and source link as plain text with link previews disabled.
How it works
Receive issue events from the selected repository, with Actions already filtered to opened. Later changes and existing issues are outside this recipe.
Send the issue number, title, repository, author and URL to the selected Chat Id. Keep the prepared plain-text mode and disabled link previews.
The result
The message is ready to read on your phone, with the original GitHub link for opening the issue separately.
New GitHub issue #62: Improve the München office onboarding guide Repository: example-studio/team-handbook Opened by: alex-example https://github.com/example-studio/team-handbook/issues/62
Fictional issue. The prepared message preserves non-ASCII text without parsing it as Telegram Markdown or HTML.
Before activation
Connect the FastHook GitHub App with access to the repository, then select it in the trigger browser. Keep the prepared opened Actions filter.
Connect the FastHook Telegram bot and select the destination Chat Id. Confirm it can post there; for a channel, grant posting access. Review who can see the copied repository metadata.
Wait for the source to connect after activation, then open a fictional issue in the selected GitHub repository. Compare the Telegram text and source URL with the issue, including any non-ASCII characters.
Opened events only. Existing issues are not imported. Edits, comments, closures and reopenings do not send messages while the prepared opened filter is selected. This recipe does not synchronize later status changes.
Plain-text metadata with previews disabled. The prepared action does not parse Markdown or HTML and disables link previews. Only number, title, repository, author and URL are mapped; issue bodies and attachments are not copied.
The chat’s audience can see copied details. Chat or channel members see the mapped title and repository identity. A GitHub link retains the repository’s access requirements. Manual reruns can send another notification for the same event.
Yes. Select its Chat Id and allow the connected FastHook Telegram bot to post there. The same mapped issue metadata will be visible to channel readers.
No. The prepared action uses plain-text mode and disables link previews. It sends mapped text without Telegram Markdown or HTML parsing.
No. The Actions filter is prepared with opened only. Edits, comments, closures and reopened events are excluded.
No. It sends number, title, repository, author and source link. Issue bodies and attachments stay out of the prepared message.
Notify your team when a GitHub release is published.
View template →Notify your Telegram chat when a GitHub pull request is opened.
View template →