Todoist · Slack
Notify Slack about new Todoist tasks
Post newly added Todoist tasks to a selected Slack channel. OAuth data:read_write covers the connected account, and this trigger receives item:added events across its accessible projects. The message includes task content, task ID, project ID and event time; descriptions, collaborator identities and emails are omitted. Content becomes visible to channel members. Uses plain text with link and media previews disabled. Existing tasks are not backfilled. Updates and completions do not emit this creation alert. Pause disables this consumer; the shared app webhook remains installed. Review the destination and use a fictional test task before activation.
- 1. Todoist · Task added
- 2. Slack · Notify the new task channel
View template →Use templateSalesforce · Slack
Notify Slack about new Salesforce leads
Send a Slack notification when a new lead is created in Salesforce. Connect Salesforce and Slack, then choose the destination channel. The polling trigger watches Lead records accessible to the connected Salesforce user. Each plain-text message includes the lead name, company, status, record ID and creation time. Wait for Connected and the initial polling baseline before creating a test lead. Existing leads are not backfilled; edits, conversions and deleted leads do not create another new-lead notification. Polling introduces a delay before delivery. The example contains fictional German business data. Email addresses, phone numbers, notes and custom fields are not included in the Slack message. Lead details become visible to members of the selected channel. Link and media previews are disabled. Manual reruns can create duplicate messages; this workflow sends alerts rather than synchronizing CRM records.
- 1. Salesforce · New Lead
- 2. Slack · Notify the new lead channel
View template →Use templateActiveCampaign · Slack
Notify Slack about new ActiveCampaign subscribers
Notify a Slack channel when a contact subscribes to an ActiveCampaign list. Connect ActiveCampaign and Slack, then select the destination Slack channel. The trigger listens for subscribe webhooks from the connected ActiveCampaign account. A prepared Filter ignores ActiveCampaign placeholder subscriptions whose list ID is 0. FastHook retrieves the current contact and list before sending a plain-text message with the subscriber name, email address, list name and subscription time. The fictional example uses German characters and contains no real customer data. Only subscriptions received after activation are processed; existing list members, contact updates, campaign activity and unsubscribes are excluded. ActiveCampaign can send a subscribe webhook when a contact is subscribed through the UI, an automation, a form or the API. The connected account must still be able to read both the contact and list when the workflow runs. Contact custom fields, tags, phone numbers, campaign history and other profile data are not copied. Subscriber identity becomes visible to members of the selected Slack channel. Wait for the Trigger to show Connected before adding a test subscriber. Link and media previews are disabled. Provider retries or repeated subscriptions may post a duplicate notification.
- 1. ActiveCampaign · Contact Subscribed
- 2. Filter · Only continue for a real list
- 3. ActiveCampaign · Get the subscribed contact
- 4. ActiveCampaign · Get the ActiveCampaign list
- 5. Slack · Notify the subscriber channel
View template →Use templateAsana · Slack
Notify Slack about new Asana tasks
Notify a Slack channel when a task is created in or added to selected Asana projects. Connect Asana and Slack, choose one or more projects with the standard browser, then select the destination Slack channel. Asana webhook events contain a task identifier but may omit display fields, so FastHook retrieves the current task before sending the notification. Each plain-text message includes the task name, project name, creator, creation time and a direct Asana task link. The fictional example uses German characters and contains no real customer data. Only task-added events received after activation are processed; existing tasks, later edits, comments, completions and deletions are excluded. Asana can emit this event both when a task is created directly in a selected project and when an existing task is later added to it. A multi-homed task added to several watched projects can produce more than one notification. The connected account must be able to read the task when the workflow runs. Task descriptions, assignees, due dates, attachments, comments and custom fields are not copied. Task names and project metadata become visible to members of the selected Slack channel, who still need Asana permission to open the source link. Wait for the Trigger to show Connected before creating a test task. Link and media previews are disabled. Provider retries or manual reruns may post a duplicate notification.
- 1. Asana · Task Added
- 2. Asana · Get the new Asana task
- 3. Slack · Notify the task channel
View template →Use templateClickUp · Slack
Notify Slack about new ClickUp tasks
Notify a Slack channel whenever a new ClickUp task is created in one of the selected Workspaces. Connect ClickUp and Slack, select one or more source Workspaces with the standard browser, then choose the Slack channel used for task alerts. ClickUp webhook events contain task identifiers rather than a complete task, so FastHook retrieves the current task before sending the notification. Each plain-text message includes the task name, status, creator, List and direct ClickUp URL. The fictional example uses German characters and contains no real customer data. Only taskCreated events received after activation are processed; existing tasks, later edits, status changes, comments and deletions are excluded. The ClickUp connection must be able to read the created task. A task deleted immediately after creation or hidden from the connected user can make the lookup fail and prevent the Slack message. Task descriptions, Custom Fields, assignees, attachments, comments and private content are not copied. Task names and metadata become visible to members of the selected Slack channel, who still need ClickUp permission to open the source link. Link and media previews are disabled. Provider retries or manual reruns may post a duplicate notification.
- 1. ClickUp · Task Created
- 2. ClickUp · Get the new ClickUp task
- 3. Slack · Notify the task channel
View template →Use templateMicrosoft 365 · Slack
Send new Microsoft Outlook emails to Slack
Notify a Slack channel when a new email arrives in the connected Microsoft Outlook inbox. Connect Microsoft 365 and Slack, then browse to the channel used for inbox alerts. Each plain-text message includes the sender name and address, subject, received time, importance and a link to open the email in Outlook. Includes its own fictional Berlin customer-escalation example with German characters. The trigger uses a managed Microsoft Graph subscription and starts with new inbox messages after activation; it does not import older mail. Email bodies, previews, attachments, recipients, conversation history and account identifiers are not copied into Slack. Link and media previews are disabled. Microsoft Graph notifications can be retried, so a provider replay may post another notification. This template only reports new messages and does not reply, forward, move, mark, or delete email.
- 1. Microsoft 365 · New Outlook Email
- 2. Slack · Notify the inbox channel
View template →Use templateTwilio · Slack
Send Twilio error logs to Slack
Notify a Slack channel when Twilio records an application error or warning. Connect Twilio and Slack, then browse to the channel used for operational alerts. Each message includes the log level, Twilio product, error code and creation time. Includes its own fictional Hamburg delivery-error example with German characters. The trigger listens for Twilio Error Logs events delivered through Event Streams after the workflow is activated; it does not import older Debugger entries. Request bodies, response bodies, phone numbers, message content, account identifiers and credentials are not copied into Slack. The message uses plain text with link and media previews disabled. Twilio Event Streams provides at-least-once delivery, so a provider replay can post another notification. This template monitors errors and does not send messages, place calls or modify Twilio resources.
- 1. Twilio · Error Log Recorded
- 2. Slack · Notify the operations channel
View template →Use templateKlaviyo · Slack
Send new Klaviyo profiles to Slack
Notify a Slack channel when a new customer profile is created in Klaviyo. Connect Klaviyo and Slack, then browse to the Slack channel that should receive the alert. FastHook checks Klaviyo every 5 minutes and sends the profile name, email address, profile ID and creation time. Includes its own fictional German customer example. Only profiles created after the workflow is activated are included; existing profiles are not backfilled. Phone numbers, consent records, custom properties, list memberships and OAuth credentials are not copied into Slack. The message uses plain text with link and media previews disabled. Klaviyo API delays can postpone a notification until a later poll, and manual reruns can post a duplicate message. This template only sends notifications and does not update the Klaviyo profile.
- 1. Klaviyo · New Profile
- 2. Slack · Notify the customer channel
View template →Use templateWebflow · Slack
Send new Webflow CMS items to Slack
Notify a Slack channel when a CMS item is created in selected Webflow sites. Connect Webflow and Slack, choose one to five sites with the standard site browser, then browse to the Slack channel that should receive the alert. Each message includes the item name, slug, collection ID and site ID. Includes its own fictional Berlin release-note example with German characters. The trigger listens for Webflow collection_item_created webhooks after the workflow is activated; it does not import existing CMS items. Item body content, unpublished fields, collaborator details and OAuth credentials are not copied into Slack. The message uses plain text with link and media previews disabled. Webflow may retry webhook deliveries, so a provider replay can post another message. This template only sends notifications and does not publish or modify Webflow content.
- 1. Webflow · Collection Item Created
- 2. Slack · Notify the content channel
View template →Use templateBrevo · Slack
Send new Brevo list contacts to Slack
Notify a Slack channel when a contact is added to a Brevo list. Connect Brevo and Slack, then browse to the Slack channel that should receive the alert. Each message includes the contact email, affected list IDs and provider timestamp. Includes its own fictional Berlin customer example with German characters. The trigger listens for Brevo marketing list_addition webhooks after the workflow is activated; it does not import existing list members. Contact attributes, phone numbers, campaign content and API credentials are not copied into Slack. The message uses plain text with link and media previews disabled. Brevo may deliver repeated webhook attempts, so a provider replay can post another message. This template provides team notifications and does not modify contacts, lists or campaigns.
- 1. Brevo · Marketing List Addition
- 2. Slack · Notify the new contacts channel
View template →Use templateJotform · Slack
Send new Jotform submissions to Slack
Notify a Slack channel whenever a response is submitted to a selected Jotform form. Connect Jotform and Slack, choose the form with the standard form browser, then browse to the Slack channel that should receive the alert. Each message includes the form ID, submission ID, submission time and a direct link to the response in Jotform Inbox. Includes its own fictional Berlin project-request example with German characters. The trigger listens for new submissions after the workflow is activated; it does not import existing responses. Answer values, uploaded files, respondent IP addresses and account details are not copied into Slack. The message uses plain text with link and media previews disabled. Jotform can omit the submission timestamp for some delivery formats, but the form and submission IDs remain available. Submitting one response should produce one alert, while a manual webhook replay can post another message. This template provides team notifications and does not modify the form or its responses.
- 1. Jotform · New Submission
- 2. Slack · Notify the form response channel
View template →Use templatemonday.com · Slack
Send new monday.com items to Slack
Notify a Slack channel whenever a new item is created on selected monday.com boards. Connect monday.com and Slack, choose one to five boards with the standard board browser, then browse to the Slack channel that should receive the alert. Each message includes the item name, item ID, board ID, group name, creator ID and webhook time. Includes its own fictional Berlin product-launch example with German characters. The trigger listens for monday.com create_item events after the workflow is activated; it does not import existing items. Column values, files, updates, private board data and user profiles are not copied into Slack. The message uses plain text with link and media previews disabled. monday.com may omit optional group details, and the creator is shown as an ID because the webhook does not guarantee a user name. Creating one item should produce one alert, but manual webhook replays can post another message. This template is a team notification, not a two-way board sync.
- 1. monday.com · Create Item
- 2. Slack · Notify the monday.com item channel
View template →Use templateMailchimp · Slack
Notify Slack about new Mailchimp subscribers
Send a Slack channel notification when Mailchimp reports a new subscriber for a selected audience. Connect Mailchimp and Slack, choose the audience with the standard Audiences browser, and select the destination channel. Each message contains the subscriber email address, audience ID, event type and the fired_at value supplied by Mailchimp. The source timestamp is preserved as text because the webhook does not include a timezone. The template has its own fictional Hamburg subscriber example with German characters in unused merge fields. Names, interests, signup IPs, tags and other merge fields are not copied. Subscriber email addresses become visible to members of the selected Slack channel, so use a channel with appropriate access. Wait for Connected before creating a fictional test subscriber. Existing contacts are not backfilled. Mailchimp can emit another subscribe event for a resubscription, and FastHook treats it as a separate notification. Unsubscribe, cleaned, profile-update and email-change events are excluded. The workflow does not create contacts, change marketing consent or send campaigns. Messages are plain text with link and media previews disabled. Manual reruns can post duplicate notifications.
- 1. Mailchimp · Subscribe
- 2. Slack · Notify the subscriber channel
View template →Use templateDropbox · Slack
Notify Slack about new or updated Dropbox files
Notify a Slack channel when a file is added or updated in Dropbox. Include its name, path, size in bytes and server modification time to help your team notice incoming documents and revisions. Connect Dropbox and Slack, review the optional folder path and file extension filters, then choose a Slack channel. Without a folder filter, eligible file changes across the connected account are included. Nested folders are included when a folder path is set. Wait for the Trigger to show Connected before uploading a fictional test file. Existing files are not imported. This trigger includes updates as well as additions; it does not distinguish a new upload from a revision. Folder and deletion events do not send messages. Messages use plain text with link previews disabled. File contents are not copied and no public sharing link is created. File names and paths become visible to channel members. The fictional sample includes German characters. Manual reruns can send another notification.
- 1. Dropbox · File Added or Updated
- 2. Slack · Notify the document channel
View template →Use templateJira · Slack
Notify Slack about new Jira issues
Send a Slack channel notification when a new Jira Cloud issue is created. Include the issue key, summary, project and issue type so your team can triage incoming work. Connect Jira and Slack, select a Jira site using Browse and choose a Slack channel. An optional JQL filter can restrict eligible projects; without a filter, new issues from the selected site are eligible. Wait for the Trigger to show Connected before creating a test issue. Existing issues and issue updates are not imported. Messages use plain text with link previews disabled. Descriptions, comments and attachments are not copied. Issue summaries become visible to channel members. This is a one-way notification, not a task or status sync. The fictional sample includes German characters. Manual reruns can send another notification.
- 1. Jira · Issue Created
- 2. Slack · Notify the issue channel
View template →Use templatePipedrive · Slack
Notify Slack about new Pipedrive deals
Notify your sales team when a new deal is created in the connected Pipedrive account. Connect Pipedrive and Slack and select a channel where FastHook can post. The existing trigger watches create.deal webhook v2 events available to the connected user; no project or pipeline selector is required. It is not restricted to one pipeline. Each message includes deal title, ID, value, currency, status and a link built from the source account host. Values are preserved as supplied by Pipedrive, without division by 100 or conversion. A deal value is an opportunity estimate, not an invoice or received payment. Includes its own fictional Hamburg deal with German characters. Person and organization contact details, notes, custom fields and files are not copied. Deal titles and values become visible to destination channel members, who still need Pipedrive permission to open the source deal. Messages are plain text with previews disabled. Wait for Connected before creating a fictional test deal. Existing deals are not backfilled; stage changes, wins, losses, edits and deletions do not post another creation alert. Manual reruns may duplicate notifications. This template is a new-deal alert, not a pipeline-state synchronization.
- 1. Pipedrive · Create Deal
- 2. Slack · Notify the new deal channel
View template →Use templateTypeform · Slack
Notify Slack about new Typeform responses
Notify your team when Typeform sends a new response for a selected form. Connect Typeform and Slack, choose the form with the standard Forms browser, and select a channel where FastHook can post. Each message shows the form title, submitted timestamp, response identifier and a link to the form results. The results link opens the form results page, not a public or guaranteed response-specific page; team members still need access to the form. Answers, hidden fields, uploaded files, respondent contact information and payment details are not copied into Slack. This makes the notification independent of question order or form-specific field IDs. Includes its own fictional Hamburg feedback form with German characters. The trigger uses form_response events, not historical response polling. Wait for Connected before submitting a fictional test response. Check the connected webhook response settings if partial responses are enabled: this template does not infer completion from answers or deduplicate different partial/completed events by respondent. Submitted time is an event field, not a scheduling or reminder time. Messages use plain text with previews disabled. Manual reruns can post another message. This template alerts the team; it does not export answers or synchronize response edits.
- 1. Typeform · Form Response
- 2. Slack · Notify the form response channel
View template →Use templateCalendly · Slack
Notify Slack about new Calendly bookings
Notify your team in Slack when a Calendly invitee books a meeting. FastHook checks Calendly every 5 minutes, so the template works with Calendly Free without webhook access. Connect Calendly and Slack, use the standard Organizations browser to select the source organization, and choose a Slack channel where FastHook can post. Polling is user-scoped: choosing an organization does not mean every member booking is tracked. Each message includes the invitee name, booking-created timestamp, invitee timezone and Rescheduled flag. Booking-created time is not meeting start time; this template does not display meeting start or end time and is not a reminder. A moved booking can produce a new notification with Rescheduled true. Group bookings can produce one message per invitee rather than one per meeting. Cancellation and no-show events are excluded, and existing bookings are not backfilled. Includes its own fictional German-name example. Emails, custom answers, meeting URLs and cancel/reschedule links are not copied. Invitee names become visible to channel members. Messages use plain text with previews disabled. Manual reruns may post duplicate messages.
- 1. Calendly · New Booking
- 2. Slack · Notify the booking channel
View template →Use templateGitLab · Slack
Notify Slack about new GitLab merge requests
Notify a Slack channel when a new GitLab merge request is opened. Help reviewers notice incoming work with the title, merge request number, project, author, branches and source link. Connect GitLab and Slack, choose the source project using the standard resource browser and select a Slack channel where FastHook can post. The Actions filter is prefilled with open; edits, approvals, merges and closures do not post another creation alert. Wait for the Trigger to show Connected after activation before opening a test merge request. Only new webhook events are processed, not existing merge requests. The fictional example contains German characters. Messages use plain text with link previews disabled. Descriptions, code and attachments are not copied. This is a one-way notification, not a review-status sync. Project members still need GitLab access to open the source link; title and branch names become visible to channel members. Manual reruns can send another message.
- 1. GitLab · Merge Request
- 2. Slack · Notify the review channel
View template →Use templateAirtable · Slack
Notify Slack about new Airtable records
Post a Slack alert with a direct record link whenever a new record is created in Airtable. Use it to help a team notice incoming leads, requests or project entries without watching the base all day. Connect Airtable and Slack, browse to the source base and optionally enter a Table ID filter, then choose a Slack channel where FastHook can post. Leaving Table IDs empty watches every table in the selected base; enter a table ID to keep alerts focused. The message includes the record ID, creation-event timestamp and an Airtable link. Cell values, attachments and private notes are not copied into Slack; recipients still need Airtable access to open the record. After activation, wait for the Trigger to show Connected before creating records: webhook provisioning can take up to 15 minutes. Only record-creation events received after the webhook is connected are processed. Existing records, later edits and deletions are excluded. Records created through the app, forms, API or automations are eligible unless you select a Change source filter. The fictional example is a Hamburg onboarding request with German characters. This is a one-way notification, not a record synchronization. Manual reruns may post another alert.
- 1. Airtable · Record Created
- 2. Slack · Announce the new record
View template →Use templateSlack · Discord
Share Slack announcements in Discord
Send Slack messages marked [Announcement] to a chosen Discord text channel. Keep a community informed without forwarding every team conversation. Connect Slack and Discord, choose the source Slack channel and browse to the destination Discord channel. The prefilled [Announcement] keyword matches anywhere, without case sensitivity, and bot messages are ignored. Matching human thread replies are also forwarded; edits and deletions are excluded. Only new matching events after activation are processed. Add FastHook to the Slack source channel before activating; leaving Channels empty watches all accessible channels. The Discord bot needs access to the destination channel and permission to send messages. The message text is copied as supplied, without converting Slack mentions or formatting. Messages longer than Discord’s 2,000-character limit are truncated; keep announcements short to preserve the complete text. User, role and everyone mentions are disabled. No files or thread history are copied, and messages are not synchronized back to Slack. Forwarded text is visible to destination channel members. Includes its own fictional English Hamburg announcement with German characters. Manual reruns can create duplicate messages.
- 1. Slack · New Keyword Mention
- 2. Discord · Share the announcement
View template →Use templateSlack · Linear
Create Linear issues from Slack issue messages
Capture Slack messages marked [Issue] as Linear issues in your chosen team. The complete message becomes the issue title; its description includes the source channel link, author ID and timestamp. Connect Slack and Linear, select the channel to watch, and browse to the destination Linear team. [Issue] is prefilled and matches anywhere in a message without case sensitivity; bot messages, edits and deletions are ignored. Matching human thread replies also create issues. Add FastHook to the source channel before activation. Leaving Channels empty watches every channel accessible to that account. This imports only new matching messages after activation, without files or thread history. Slack mentions and formatting are copied as supplied; keep messages short and use plain text. This is one-way issue capture without comment or status synchronization. No assignee or project is chosen by the template. Source text becomes visible to members with access to the destination team. Includes its own fictional English Bremen example with German characters. Manual reruns may create duplicate issues.
- 1. Slack · New Keyword Mention
- 2. Linear · Capture the Slack issue
View template →Use templateSlack · ClickUp
Create ClickUp tasks from Slack task messages
Turn Slack messages containing [Task] into ClickUp tasks. Connect Slack and ClickUp, choose the Slack channel to watch, then browse to the destination Workspace, Space and List. The keyword [Task] is prefilled and matched anywhere in the message, without case sensitivity. Bot messages are ignored. Matching human thread replies also create tasks; edits and deletions do not. Each task uses the message text as its title and includes the source channel link, author ID and message timestamp. Keep task messages short and use plain text: Slack mentions and formatting are copied as supplied rather than converted. Includes its own fictional English task example with German characters. Add FastHook to the source channel before activating. Leaving Channels empty watches every channel accessible to the connection. Only new events after activation are processed; existing messages are not imported. This is one-way task capture, not status synchronization. Files and thread history are not copied. Message text becomes visible to members of the destination ClickUp List. Manual reruns can create duplicate tasks.
- 1. Slack · New Keyword Mention
- 2. ClickUp · Capture the Slack task
View template →Use templateGoogle Calendar · Slack
Announce Google Calendar event changes in Slack
Tell your team when an existing Google Calendar event changes, including a revised meeting title or schedule. Each plain-text Slack notification includes the latest title, start, end, event ID, update timestamp and calendar link. Connect Google Calendar and Slack, browse to the calendar you want to watch and choose a channel where FastHook can post. The primary calendar is preselected and can be changed. Includes its own fictional Würzburg planning example. The first poll establishes a baseline without announcing history. Edit existing events after that baseline; recently created events within the two-minute overlap window are treated as new and excluded, so allow new events to settle before editing them. New events and cancellations do not trigger this template. Timed events retain timestamp offsets; all-day events use dates with an exclusive end date. Notifications contain the latest event snapshot, not a before-and-after comparison, and multiple changes between polls may be combined. Other Calendar changes can also produce a notification even when the displayed title and times are unchanged. Earlier Slack messages are not updated. Descriptions, attendees and attachments are not copied; link previews and Slack formatting are disabled. Channel members can see the displayed event details, while opening the calendar link still requires calendar access. Manual reruns or uncertain provider retries may duplicate notifications. Start with a dedicated test calendar.
- 1. Google Calendar · Updated Event
- 2. Slack · Notify the channel about the event change
View template →Use templateSlack · Google Calendar
Create Google Calendar events from marked Slack messages
Turn selected Slack messages into Google Calendar events by adding [Event] to an English scheduling description. Use this to save planning sessions mentioned in a team channel without copying them into Calendar by hand. Connect Slack, choose source channels through Browse, connect Google Calendar and select a writable calendar through the standard browser. The [Event] keyword is prefilled, matched anywhere without case sensitivity, and bot messages are ignored. Google Quick Add parses the complete message for its title, date and time. Write an explicit date and time range, for example: [Event] Erlangen planning — Grüße on September 19, 2026 from 9:00 AM to 9:30 AM. Includes its own fictional scheduling example with German Unicode. Google may retain or normalize the marker and other punctuation in the parsed event title. Times without a timezone use the selected calendar's timezone; ambiguous or missing dates and times may produce an unintended schedule. Review the created event before using this for real meetings. Add FastHook to the source channel before activation. Leaving Channels empty watches every channel accessible to the Slack connection; matching human thread replies also create events. Only new matching messages are processed, not history, edits or deletions. Files, attachments and surrounding thread history are not copied. No attendees or invitation updates are configured, and Calendar defaults such as reminders still apply. This creates a calendar entry, not a synchronized meeting: no availability check, conferencing link or later update is provided. Manual reruns or ambiguous provider retries may create duplicate events. Use a dedicated test calendar for the first run.
- 1. Slack · New Keyword Mention
- 2. Google Calendar · Create an event from the marked message
View template →Use templateSlack · Gmail
Email marked Slack messages with Gmail
Send a Gmail email when someone marks a Slack message with [Email]. Use this to pass selected channel updates to reviewers who follow work from their inbox. Connect Slack, select source channels through Browse, connect Gmail and enter a fixed recipient address. The [Email] keyword is prefilled, matched anywhere without case sensitivity, and bot messages are ignored. Each plain-text email contains the complete message, author ID, channel ID, original Slack timestamp and source channel link. Includes its own fictional English Hannover handoff example with German Unicode. Add FastHook to the source channel before activation. Leaving Channels empty watches every channel accessible to the Slack connection; matching human thread replies also send email. Only new matching messages are processed, not historical messages, edits or deletions. Mentions and Slack formatting remain literal source text. Files, attachments and surrounding thread history are not copied. This creates an email notification, not a Slack reply or synchronized conversation. Email recipients can read the copied message; opening the source channel still requires Slack access. Emails are sent from the connected Gmail account and appear in Sent. No HTML, Cc or Bcc is configured. Gmail limits apply and manual reruns or ambiguous provider retries can resend a message. Use your own email address for the first test.
- 1. Slack · New Keyword Mention
- 2. Gmail · Email the marked Slack message
View template →Use templateSlack · 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 templateSlack · Google Drive
Archive Slack messages as Google Drive text files
Save Slack messages containing [Archive] as UTF-8 text files in Google Drive. Connect Slack and Google Drive, choose source channels and optionally browse to a destination folder. The [Archive] keyword is prefilled and matched anywhere without case sensitivity; bot messages are ignored. Each file contains the original message text, author ID, channel ID, message timestamp and a source channel URL. The filename uses the workspace, channel and message timestamp with a .txt extension. Leaving Parent folder empty saves to My Drive. Includes its own fictional English Bremen handoff example. Add FastHook to the source Slack channel before activation. Leaving Channels empty watches every channel accessible to the connection. Matching human thread replies also create files. Existing messages, edits and deletions are not synchronized; attached files and thread history are not copied. Slack formatting and mentions remain source text. This is a message capture, not a full workspace backup. Files inherit the destination folder access; no public sharing action is added. Manual reruns can create duplicate files.
- 1. Slack · New Keyword Mention
- 2. Google Drive · Save Slack message as a text file
View template →Use templateSlack · Google Sheets
Log Slack feedback in Google Sheets
Collect Slack messages containing [Feedback] in a Google Sheets feedback log. Connect Slack and Google Sheets, choose source channels, then browse to a destination spreadsheet and worksheet. The [Feedback] keyword is prefilled, matched anywhere without case sensitivity, and bot messages are ignored. Append Values writes Message, Author ID, Channel ID, Message timestamp, Workspace ID and Source channel URL into columns A-F in that order. Headers are optional; an empty worksheet works immediately. RAW input preserves message text, quotes and newlines without evaluating formulas or converting Slack timestamps to numbers. Includes its own fictional English Hamburg feedback example. Add FastHook to the source channel before activation. Leaving Channels empty watches all channels accessible to the connection. Matching human thread replies are included. Existing messages, edits and deletions are not synchronized. Files and thread history are not copied. Slack mentions and formatting are stored as source text. Choose a worksheet with appropriate access to the source messages. Manual reruns can add duplicate rows.
- 1. Slack · New Keyword Mention
- 2. Google Sheets · Append feedback to the log
View template →Use templateSlack · Notion
Save Slack notes as Notion pages
Save Slack messages containing [Notes] as Notion child pages for your team knowledge base. Connect Slack and Notion, choose the Slack channel to watch, then browse to a parent page accessible to the Notion connection. The [Notes] keyword is prefilled and matched anywhere without case sensitivity. Bot messages are ignored. Each page includes the message text, author ID, message timestamp, a clickable source channel link and a Follow-up section. The page title is Slack note plus the message timestamp. Use short notes up to 2000 characters, including the marker, to fit the Notion text-block limit. Slack mentions and formatting are preserved as source text rather than converted. Includes its own fictional English Leipzig workshop note. Add FastHook to the source Slack channel before activation. Leaving Channels empty watches every channel accessible to the connection. Matching human thread replies also create pages; edits, deletions and historical messages are not synchronized. Files and thread history are not copied. This creates child pages, not database rows. Message text becomes visible to people with access to the selected parent page. Manual reruns can create duplicates.
- 1. Slack · New Keyword Mention
- 2. Notion · Save the Slack note
View template →Use templateSlack · Trello
Create Trello cards from Slack task messages
Turn Slack messages containing [Task] into Trello cards. Connect Slack and Trello, choose the Slack channel to watch, then browse to the destination board and list. The keyword [Task] is prefilled and matched anywhere in the message, without case sensitivity. Bot messages are ignored. Matching human thread replies also create cards; edits and deletions do not. Each card uses the message text as its title and includes the source channel link, author ID and message timestamp. Keep task messages short and use plain text: Slack mentions and formatting are copied as supplied rather than converted. Includes its own fictional English task example with German characters. Add FastHook to the source channel before activating. Leaving Channels empty watches every channel accessible to the connection. Only new events after activation are processed; existing messages are not imported. This is one-way task capture, not status synchronization. Files and thread history are not copied. Message text becomes visible to members of the destination Trello board. Manual reruns can create duplicate cards.
- 1. Slack · New Keyword Mention
- 2. Trello · Capture the Slack task
View template →Use templateGitHub · Slack
Send Slack alerts for published GitHub releases
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.
- 1. GitHub · Release
- 2. Slack · Notify the team about a published release
View template →Use templateGitHub · Slack
Send new GitHub pull requests to Slack
Notify your team when a GitHub pull request is opened. Connect the FastHook GitHub App and Slack, browse to the repository to track, and choose a channel where the FastHook bot can post. The Actions filter is prefilled with opened. Messages include the PR title, number, author, source and target branches, draft flag and link. Draft pull requests are included. Edits, new commits, reviews, closed and reopened PRs do not create another alert. Includes an independent fictional English pull request example. PR bodies, code changes and attachments are not copied. Messages use plain text with link previews disabled. Processes new webhook events after activation, not existing PRs. This is a one-way alert, not a review assignment or status sync. Details become visible to members of the destination channel. Manual workflow reruns can duplicate messages.
- 1. GitHub · Pull Request
- 2. Slack · Notify the team about a new pull request
View template →Use templateStripe · Slack
Send Slack alerts for paid Stripe invoices
Notify your team when a Stripe invoice becomes paid. Connect Stripe and Slack, browse to your billing channel, then publish. Uses invoice.paid and sends the Invoice ID, invoice amount paid in Stripe minor units, currency, event ID and live-mode flag. Includes subscription renewal invoices and one-off invoices. For EUR and USD, 1900 minor units means 19.00; for JPY, 1900 means 1900. Paid invoices can include zero-value invoices, customer balance and invoices marked paid outside Stripe, so this alert is not proof of a new card charge or bank payout. Includes an independent fictional München invoice example. Review the invoice in Stripe for payment details. No customer contact information, payment details, hosted invoice links, PDF links or metadata are forwarded. This workflow does not create invoices, collect payments, or import existing paid invoices. Drafts and open invoices do not trigger it. Test with Stripe sandbox first; Live mode false identifies test events. Manual workflow reruns can duplicate notifications.
- 1. Stripe · Invoice Paid
- 2. Slack · Notify the team about a paid invoice
View template →Use templateStripe · Slack
Send Slack alerts for canceled Stripe subscriptions
Notify your team when a Stripe subscription actually ends. Connect Stripe and Slack, browse to your customer-success channel, then publish. Uses customer.subscription.deleted and sends the Subscription ID, status, currency, event ID and live-mode flag. Scheduling cancellation at the end of a period only updates the subscription and does not trigger this workflow; the alert arrives when the subscription ends. Includes an independent fictional München canceled-trial example. Covers cancellations after trials as well as paid subscriptions without claiming lost revenue or a customer-requested cancellation. Review the subscription in Stripe for the cause and any outstanding invoices. This workflow does not cancel subscriptions, issue refunds, revoke access, or import past cancellations. No customer contact information, cancellation comments, payment details or metadata are forwarded. Test with Stripe sandbox first; Live mode false identifies test events. Manual workflow reruns can duplicate notifications.
- 1. Stripe · Customer Subscription Deleted
- 2. Slack · Notify the team about an ended subscription
View template →Use templateStripe · Slack
Send Slack alerts for new Stripe subscriptions
Notify your team when a Stripe subscription is created, including trial subscriptions. Connect Stripe and Slack, browse to your subscriptions channel, then publish. Uses customer.subscription.created and sends the Subscription ID, status at creation, currency, event ID and live-mode flag. A new subscription can be trialing or incomplete: creation is not proof of payment and this workflow does not grant customer access. Includes an independent fictional München trial subscription example. Supports subscriptions with multiple prices without presenting a single price as the total. No customer contact information, payment details or metadata are forwarded. This workflow does not create subscriptions, import existing subscriptions, or notify about renewals, updates and cancellations. Test with Stripe sandbox first; Live mode false identifies test events. Manual workflow reruns can duplicate notifications.
- 1. Stripe · Customer Subscription Created
- 2. Slack · Notify the team about a new subscription
View template →Use templateStripe · Slack
Send Slack alerts for new Stripe refunds
Notify your team when a new Stripe refund is created, including partial refunds. Connect Stripe and Slack, browse to a payment operations channel, then publish. Uses refund.created and sends the Refund ID, the amount of that individual refund in Stripe minor units, currency, event ID and live-mode flag. For EUR and USD, 1000 minor units means 10.00; for JPY, 1000 means 1000. Two partial refunds produce separate alerts for their own amounts, not the accumulated refunded total. Includes an independent fictional EUR sandbox refund example. Refund created does not mean funds have reached the customer: review its current status in Stripe. This workflow does not issue refunds or track subsequent pending, failed, canceled or completed status updates. No customer contact information, card details, instructions email, metadata or destination details are forwarded. Test with Stripe sandbox first; Live mode false identifies test events. Existing refunds are not imported, and manual workflow reruns can duplicate notifications.
- 1. Stripe · Refund Created
- 2. Slack · Notify the team about a new refund
View template →Use templateStripe · Slack
Send Slack alerts for failed Stripe payments
Alert your team when a Stripe PaymentIntent payment attempt fails. Connect Stripe and Slack, browse to your payment alerts channel, then publish. Listens only for payment_intent.payment_failed and sends the PaymentIntent ID, attempted amount in Stripe minor units, currency, event ID and live-mode flag. For EUR and USD, 2900 minor units means 29.00; for JPY, 2900 means 2900. Includes its own fictional failed EUR sandbox payment example. Review the payment in Stripe before contacting a customer: a failed attempt is not necessarily a permanently failed payment, and a later retry can succeed. Each new failed-attempt event can generate another alert. Successful, pending and canceled payments do not trigger this workflow. It does not retry charges, issue refunds, contact customers or track invoice-specific retry schedules. No card details, client secrets, customer contact information or raw error objects are forwarded. Test in Stripe sandbox first; Live mode false identifies test events. Manual workflow reruns can duplicate notifications.
- 1. Stripe · Payment Intent Payment Failed
- 2. Slack · Notify the team about a failed payment
View template →Use templateStripe · Slack
Send Slack alerts for successful Stripe payments
Notify your team when a Stripe PaymentIntent succeeds. Connect Stripe and Slack, browse to a channel where the FastHook bot can post, then publish. The trigger listens only for payment_intent.succeeded. Each plain-text message contains the PaymentIntent ID, amount received in Stripe minor units, currency, event ID and live-mode flag. For EUR and USD, 4900 minor units means 49.00; for zero-decimal currencies such as JPY, 4900 means 4900. Amounts are not converted between currencies. Includes its own fictional EUR sandbox payment example. Pending, failed and canceled payments do not send this alert. Existing payments, later refunds, disputes and bank payouts are not synchronized. Payment success does not mean funds have reached your bank. No card details, client secrets, customer contact information or metadata are forwarded. Choose a channel appropriate for payment notifications and test with Stripe sandbox first. Live mode false identifies test events. Manual reruns can send another notification.
- 1. Stripe · Payment Intent Succeeded
- 2. Slack · Notify the payment alerts channel
View template →Use templateHubSpot · Slack
Send Slack alerts for new HubSpot contacts
Notify a Slack channel when a new contact is created in HubSpot. Connect HubSpot and Slack, then browse to a channel where the FastHook bot can post. Each message contains the contact ID and a direct link to its HubSpot record. The instant trigger listens only for contact.creation events after activation. Existing contacts, property edits, merges and deletions are not announced. HubSpot creation webhooks contain record IDs, not the full contact profile, so names, emails and other contact properties are not copied. Opening the link requires existing HubSpot access. Includes its own fictional contact-created example. Choose a channel appropriate for CRM notifications. Test with one fictional contact first; this template does not create contacts, send marketing emails or change contact permissions.
- 1. HubSpot · Contact Creation
- 2. Slack · Notify the CRM contacts channel
View template →Use templateStripe · Slack
Send Slack alerts for new Stripe customers
Notify your team when a customer is created in Stripe. Connect Stripe and Slack, choose a channel where the FastHook bot can post, 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 customer with German characters. New customers do not necessarily represent a payment or a subscription. Existing customers and later updates are not imported. Customer name and email are shared with everyone in the selected Slack channel; choose an appropriate channel. No payment details, addresses, tax IDs or metadata are forwarded. Test with a fictional customer in Stripe sandbox first; the message includes the live-mode flag so test events can be distinguished. Customer name and email may be empty if they were not provided in Stripe.
- 1. Stripe · Customer Created
- 2. Slack · Notify the customer onboarding channel
View template →Use templateGmail · Slack
Send Slack 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 Slack alert with the subject, sender, received date and Gmail conversation link. Connect Gmail and Slack, review the search query and choose a channel where the FastHook bot can post. 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 channel. Each new matching message produces one alert, including replies that still match the search.
- 1. Gmail · New Email Matching Search
- 2. Slack · Notify the email alerts channel
View template →Use templateGoogle Drive · Slack
Send Slack notifications for new Google Drive files
Notify your Slack channel when a new file is created in a Google Drive folder. Each message includes the file name, type and a direct Drive URL. Connect Google Drive and Slack, browse to the folder to watch, and choose a channel where the FastHook bot can post. Leaving the folder empty watches the connected Drive. The folder scope includes direct children only; subfolders are not scanned. Detection uses file creation time, so moving an older file into the folder is not guaranteed to trigger a notification. Polling may include files created roughly one minute before setup; older files and later edits are not imported. Includes its own fictional English project document example with German characters. Messages preserve literal text and disable link previews. File names and URLs become visible to channel members, but Drive sharing permissions stay unchanged.
- 1. Google Drive · New Files
- 2. Slack · Announce the new Drive file
View template →Use templateGoogle Sheets · Slack
Send Slack notifications for new Google Sheets rows
Notify your team when a new request is added to Google Sheets. Use Title, Company, Priority and Details headers in row 1, then append one complete request per row. Connect Google Sheets and Slack, browse to your spreadsheet and worksheet, and choose a channel where the FastHook bot can post. The prepared message includes those four columns, the worksheet name, row number and spreadsheet link. Edit the mappings if your column names differ. Activate and let the first poll establish a baseline before appending rows. Existing rows and later edits are not sent; avoid deleting or reordering rows while active. Includes a fictional English request example with German characters. Messages use plain text with link previews disabled. Mapped row data becomes visible to members of the selected Slack channel; spreadsheet access permissions remain unchanged.
- 1. Google Sheets · New Row Added
- 2. Slack · Notify the requests channel
View template →Use templateGoogle Calendar · Slack
Announce new Google Calendar events in Slack
Keep your team channel informed when a new event is added to Google Calendar. Each Slack message includes the event title, start, end and a direct calendar link. Connect Google Calendar and Slack, choose the calendar and a channel where the FastHook bot can post. The primary calendar is preselected and can be changed. Includes a fictional English planning-session example. Timed events preserve their original timestamps and timezone offsets; all-day events use dates and the end date is exclusive. The first poll establishes a baseline: create new events afterwards. Existing events, later edits and cancellations are not synchronized. This announces event creation, not an upcoming-event reminder. Messages use plain text with link previews disabled; attendee addresses, descriptions and attachments are not copied. Event details become visible to channel members, and the calendar link still requires appropriate calendar access.
- 1. Google Calendar · New Event
- 2. Slack · Notify the planning channel
View template →Use templateTrello · Slack
Send new Trello cards to a Slack channel
Keep your project channel informed when a new card is created on a selected Trello board. Each Slack message contains the card name, board, list and a direct card link. Connect Trello and Slack, choose the board to watch and a channel where the FastHook bot can post. Includes its own fictional English project handoff example. Messages use plain text with link previews disabled; descriptions and attachments are not copied. Wait for the trigger to show Connected before creating the first card; initial webhook registration can take up to 15 minutes. Only new card creation after activation is processed. Existing cards, copied cards, moves and later edits do not send another message. This is a one-way notification, not a status sync. Card names and board details become visible to everyone in the destination channel; the card link still requires Trello access.
- 1. Trello · Create Card
- 2. Slack · Notify the project channel
View template →Use templateGitHub · Slack
Send new GitHub issues to a Slack channel
Keep your team informed when a GitHub issue is opened. FastHook posts the issue title, number, repository, author and source link in your chosen Slack channel. Connect the FastHook GitHub App and Slack, select the repository to track, then choose a channel where the FastHook bot can post. The Actions filter is prefilled with opened; edits, comments, closed and reopened issues do not send another message. Includes a fictional English support issue example. Messages use plain text with link previews disabled. Issue bodies and attachments are not copied. Processes new webhook events after activation, not existing issues. This is a one-way notification, not a threaded status sync. Issue details become visible to members of the destination channel.
- 1. GitHub · Issues
- 2. Slack · Notify the issue channel
View template →Use template
