Slack · Telegram Bot
Send Telegram alerts for marked Slack messages
Forward Slack messages containing [Alert] to a Telegram chat or channel. Connect Slack, choose source channels, then select a Telegram destination through Browse. The [Alert] keyword is prefilled and matched anywhere without case sensitivity; bot messages are ignored. Each notification includes the original message text, author ID, channel ID and a source channel link. Includes its own fictional English Dresden handoff example. Add FastHook to the source Slack channel and the FastHook bot to the destination Telegram chat before activation. Leaving Channels empty watches all channels accessible to the Slack connection. Matching human thread replies also send notifications. Only new matching messages are processed; existing messages, edits, deleted messages, attachments and thread history are not copied. Slack formatting and mention codes remain plain text, with Telegram link previews disabled. Keep source messages under 3500 characters to leave room for metadata within Telegram’s 4096-character message limit. Message contents become visible to members of the destination Telegram chat. Manual reruns can create duplicate notifications.
- 1. Slack · New Keyword Mention
- 2. Telegram Bot · Send marked Slack message to Telegram
View template →Use templateGitHub · 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
View template →Use templateGitHub · 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
View template →Use templateHubSpot · Telegram Bot
Send Telegram alerts for new HubSpot contacts
Receive a Telegram notification whenever a new contact is created in HubSpot. Connect HubSpot and Telegram, then select a chat where your bot can post. Each message contains the contact ID and a direct link to its HubSpot record. Only contact.creation events received after activation are processed; existing contacts, later edits, merges and deletions are not announced. Creation webhooks provide record IDs, not contact names or email addresses, so profile fields are not copied. Opening the CRM link requires existing HubSpot access. Includes its own fictional contact-created example. Choose a chat appropriate for CRM notifications. Test with one fictional contact first. This workflow sends alerts to the selected chat, does not message the contact directly, and does not change CRM permissions.
- 1. HubSpot · Contact Creation
- 2. Telegram Bot · Notify the CRM alerts chat
View template →Use templateStripe · Telegram Bot
Send Telegram alerts for new Stripe customers
Receive a Telegram notification when a new customer is created in Stripe. Connect Stripe and Telegram, select the destination chat, and keep the prepared customer name, email and ID mappings. The instant trigger listens only for customer.created events from the connected Stripe account. Includes its own fictional English sandbox customer with German characters. Creating a customer does not confirm a payment or subscription. Existing customers and later updates are not imported. Name and email may be empty. The message includes the live-mode flag to distinguish sandbox events. No payment details, addresses, tax IDs or metadata are forwarded. Choose a chat whose members may see customer names and email addresses; the Telegram bot must be able to post there. Test with a fictional Stripe sandbox customer first.
- 1. Stripe · Customer Created
- 2. Telegram Bot · Notify the customer alerts chat
View template →Use templateGitHub · Telegram Bot
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.
- 1. GitHub · Issues
- 2. Telegram Bot · Notify the Telegram issue chat
View template →Use templateGoogle Sheets · Telegram Bot
Send Telegram notifications for new Google Sheets rows
Send a Telegram notification when a new request is appended to Google Sheets. Put Title, Company, Priority and Details headers in row 1, then add one complete request per row. Connect Google Sheets and Telegram, browse to your spreadsheet and worksheet, and choose a chat where the FastHook bot can post. The prepared plain-text message includes those four columns, the worksheet name, row number and spreadsheet link. Change the mappings if your headers differ. Activate and allow the first poll to establish a baseline before adding rows. Existing rows and later edits are not sent; avoid deleting or reordering rows while active. Includes a fictional English request with German characters. Keep the combined message within Telegram’s 4096-character limit. Mapped data is visible to members of the selected chat; spreadsheet access permissions remain unchanged.
- 1. Google Sheets · New Row Added
- 2. Telegram Bot · Notify the Telegram requests chat
View template →Use templateGmail · Telegram Bot
Send Telegram alerts for matching Gmail emails
Stay informed about priority inbox messages without forwarding whole emails. New Gmail messages matching the prefilled search subject:"[Alert]" produce a plain-text Telegram alert with the subject, sender, received date and Gmail conversation link. Connect Gmail and Telegram, review the search query and choose a private chat where your bot can send messages. Includes its own fictional English alert. Only newly received matching inbox messages are processed; this is not a historical import, label-change monitor or two-way sync. Email bodies and attachments are not forwarded. The Gmail link requires access to the same mailbox; select that Google account if you use multiple accounts. Subject and sender details are shared with everyone in the selected chat. Each new matching message produces one alert, including replies that still match the search.
- 1. Gmail · New Email Matching Search
- 2. Telegram Bot · Send priority email alert
View template →Use templateGoogle Drive · Telegram Bot
Send Telegram alerts for new Google Drive files
Notify your Telegram chat when new files are created in Google Drive. Each message includes the file name and a direct Drive link. Connect Google Drive and Telegram, choose the folder to watch, and select your chat. Leaving the folder empty watches the connected Drive. Includes its own English document example. The folder scope is direct children only, and detection uses file creation time: moving an older file into the folder is not guaranteed to trigger an alert. Polling can include files from roughly the minute before setup; older files and later edits are not imported. A link does not grant access: recipients still need existing Drive permissions. The Telegram bot needs permission to post in the selected chat.
- 1. Google Drive · New Files
- 2. Telegram Bot · Announce new Drive file
View template →Use templateGoogle Calendar · Telegram Bot
Send Telegram alerts for new Google Calendar events
Keep your team informed when new events are added to Google Calendar. Send the event title and a direct event link with the current schedule to Telegram. Connect Google Calendar and Telegram, choose the calendar, and select the destination chat. The primary calendar is preselected and can be changed. Includes an English sample meeting and supports all-day events. The first poll establishes a baseline; events created afterwards are announced. Existing events and later edits are not imported. This is a new-event alert, not a reminder before the meeting starts. The Telegram bot needs permission to post in your chat.
- 1. Google Calendar · New Event
- 2. Telegram Bot · Announce new calendar event
View template →Use templateTrello · Telegram Bot
Send Telegram alerts for new Trello cards
Notify your team in Telegram whenever a new card is created on a selected Trello board. Each message includes the card name, board, list and a direct card link. Connect Trello and Telegram, choose the board and enter the destination chat ID. Messages use plain text. Includes its own English sample card. Watches new card creation after activation; existing cards, copies and later card updates are not imported. Your connected Telegram bot needs permission to send messages to the destination chat. Initial webhook registration can take up to 15 minutes; wait for the trigger to show Connected before creating the first card.
- 1. Trello · Create Card
- 2. Telegram Bot · Notify about new card
View template →Use templateGoogle Sheets · Trello · Telegram Bot
Turn Google Sheets leads into Trello cards and Telegram alerts
Turn each new Google Sheets row into a Trello card with the lead name, email, company and request, then send the card link to Telegram. Use the column headers Name, Email, Company and Request, or adjust the mappings. Connect your accounts, choose a spreadsheet and worksheet, select a Trello board and list, and enter your Telegram chat ID. Includes an English example lead. New rows added after activation are processed; existing rows are not imported.
- 1. Google Sheets · New Row Added
- 2. Trello · Create lead card
- 3. Telegram Bot · Send lead notification
View template →Use templateGmail · Google Drive · Telegram Bot
Gmail attachments to Drive and Telegram
Save every new Gmail attachment in a sender/date folder, make the uploaded file public, and send its link to Telegram.
- 1. Gmail · New Attachment Received
- 2. Google Drive · Create sender/date folder
- 3. Google Drive · Upload attachment
- 4. Google Drive · Make attachment public
- 5. Telegram Bot · Send public link to Telegram
View template →Use template
