FastHook logoFastHookBuild a Workflow

Workflow templates

Copy a complete automation in one click

Templates create an editable Draft with its Steps and mappings already connected. Your accounts and secrets are never copied.

143 templates · 100 groups

TallyGoogle TasksTally → Google Tasks1 templateCreate Google Tasks from new Tally submissions

Tally · Google Tasks

Create Google Tasks from new Tally submissions

Create one task for each new completed submission to selected Tally forms. Connect Tally and Google Tasks, select the forms and a task list. The task title uses the form name; notes include the submission ID and timestamp. Add your own form-answer mappings if needed. Existing submissions are not backfilled. Manual reruns may create duplicate tasks. Pausing stops the Tally subscription when no active consumer needs it. Google Tasks has no webhook subscriptions of its own.

  1. 1. Tally · New Submission
  2. 2. Google Tasks · Create task for the submission
View template →Use template
Zoho CRMGoogle SheetsZoho CRM → Google Sheets1 templateLog new Zoho CRM contacts in Google Sheets

Zoho CRM · Google Sheets

Log new Zoho CRM contacts in Google Sheets

Append a row for every new contact ID reported by Zoho CRM EU. Connect Zoho CRM and Google Sheets, then select a spreadsheet and worksheet. Columns A-D contain module, record ID, operation and provider event time in Unix milliseconds. The visible Loop step processes every ID in a batched notification; Google Sheets inside the Loop appends one row per ID. Only Contacts insert notifications received after activation are processed; existing contacts are not backfilled. Contact names, email addresses and other personal fields are not copied. RAW preserves text without formula evaluation. Provider retries or manual reruns may append duplicate rows. Wait for the trigger to show Connected before creating a test contact. Pausing removes the owned notification channel when no active consumer still needs it.

  1. 1. Zoho CRM · New Contact
  2. 2. Loop · For each new contact ID
  3. 3. Google Sheets · Append contact event rows to the worksheet
View template →Use template
TallyGoogle SheetsTally → Google Sheets1 templateLog new Tally submissions in Google Sheets

Tally · Google Sheets

Log new Tally submissions in Google Sheets

Append one row for each new completed submission to selected Tally forms. Connect Tally through OAuth, select the forms, then select a Google Sheets spreadsheet and worksheet. Columns A-D contain Form name, Submission ID, Form ID and Submission time UTC. An empty worksheet works; headers are optional. This starter records submission metadata; add answer mappings for your form if needed. Answers, uploaded files and signed preview/PDF links are not copied. Existing submissions are not backfilled. RAW preserves formula-looking form names as text. Manual reruns can append duplicate rows. Pausing the workflow removes its webhook subscription when no active consumer still needs it.

  1. 1. Tally · New Submission
  2. 2. Google Sheets · Append submission metadata to the worksheet
View template →Use template
TodoistGoogle SheetsTodoist → Google Sheets1 templateLog new Todoist tasks in Google Sheets

Todoist · Google Sheets

Log new Todoist tasks in Google Sheets

Add one row to Google Sheets when a new Todoist task is created. Connect Todoist and Google Sheets, then use Browse to choose the destination spreadsheet and worksheet. Columns A-D contain Task name, Task ID, Project ID and Event time UTC, in that order. An empty worksheet works; headers are optional. The Todoist trigger receives item:added events across the connected account's accessible projects. Existing tasks are not backfilled, and updates or completions do not add rows. Descriptions and collaborator identities are not copied. Task names become visible to everyone with access to the spreadsheet. RAW input preserves formula-looking task names as text. Manual reruns can append duplicate rows. Pausing the Workflow disables this consumer while the shared Todoist app webhook remains installed.

  1. 1. Todoist · Task added
  2. 2. Google Sheets · Append the new task to the worksheet
View template →Use template
TodoistSlackTodoist → Slack1 templateNotify Slack about new Todoist tasks

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. 1. Todoist · Task added
  2. 2. Slack · Notify the new task channel
View template →Use template
SalesforceSlackSalesforce → Slack1 templateNotify Slack about new Salesforce leads
Explore Salesforce → Slack integrations →

Salesforce · 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. 1. Salesforce · New Lead
  2. 2. Slack · Notify the new lead channel
View template →Use template
ActiveCampaignSlackActiveCampaign → Slack1 templateNotify Slack about new ActiveCampaign subscribers
Explore ActiveCampaign → Slack integrations →

ActiveCampaign · 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. 1. ActiveCampaign · Contact Subscribed
  2. 2. Filter · Only continue for a real list
  3. 3. ActiveCampaign · Get the subscribed contact
  4. 4. ActiveCampaign · Get the ActiveCampaign list
  5. 5. Slack · Notify the subscriber channel
View template →Use template
AsanaSlackAsana → Slack1 templateNotify Slack about new Asana tasks
Explore Asana → Slack integrations →

Asana · 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. 1. Asana · Task Added
  2. 2. Asana · Get the new Asana task
  3. 3. Slack · Notify the task channel
View template →Use template
ClickUpSlackClickUp → Slack1 templateNotify Slack about new ClickUp tasks
Explore ClickUp → Slack integrations →

ClickUp · 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. 1. ClickUp · Task Created
  2. 2. ClickUp · Get the new ClickUp task
  3. 3. Slack · Notify the task channel
View template →Use template
AirtableMicrosoft 365Airtable → Microsoft 3651 templateEmail new Airtable records with Microsoft Outlook

Airtable · Microsoft 365

Email new Airtable records with Microsoft Outlook

Send a plain-text Microsoft Outlook email whenever a new Airtable record is created. Connect Airtable and Microsoft 365, browse to the source base, and enter the recipient address that should receive the alert. The email includes the record ID, base and table IDs, creation timestamp and a direct Airtable link. It does not copy cell values, attachments or private notes, so the recipient can open the source record only if they already have Airtable access. Only record.created events received after the workflow is activated are processed; existing records, edits and deletions are excluded. Records created through the Airtable app, forms, API or automations are eligible. Includes a fictional English onboarding request with German characters. The message is saved to Outlook Sent Items, and manual reruns or provider retries may send another email.

  1. 1. Airtable · Record Created
  2. 2. Microsoft 365 · Email the new Airtable record
View template →Use template
Microsoft 365SlackMicrosoft 365 → Slack1 templateSend new Microsoft Outlook emails to Slack
Explore Microsoft 365 → Slack integrations →

Microsoft 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. 1. Microsoft 365 · New Outlook Email
  2. 2. Slack · Notify the inbox channel
View template →Use template
TwilioSlackTwilio → Slack1 templateSend Twilio error logs to Slack
Explore Twilio → Slack integrations →

Twilio · 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. 1. Twilio · Error Log Recorded
  2. 2. Slack · Notify the operations channel
View template →Use template
Google CalendarMicrosoft 365Google Calendar → Microsoft 3651 templateCreate Outlook Calendar events from new Google Calendar events

Google Calendar · Microsoft 365

Create Outlook Calendar events from new Google Calendar events

Create a matching Outlook Calendar event whenever a new timed event is added to Google Calendar. Connect Google Calendar and Microsoft 365, browse to the source calendar, and optionally choose the destination Outlook calendar. The primary Google calendar and default Outlook calendar work without extra selection. A Filter skips all-day events because Microsoft Graph requires explicit start and end times for this mapping. Two Formatter steps convert RFC 3339 timestamps and their offsets to UTC before the Outlook event is created. The event title and Google Calendar link are copied; descriptions, locations, attendees, conferencing details and attachments are not copied. No invitations or emails are sent. Activate the workflow and let the first Google Calendar poll establish a baseline before creating a test event. Existing events, all-day events, later edits, cancellations and deletions are not synchronized. Includes a fictional Berlin planning example with German characters. The Outlook event uses UTC internally and displays in the destination calendar timezone. Manual reruns can create duplicate events. This is one-way event creation, not a two-way calendar sync.

  1. 1. Google Calendar · New Event
  2. 2. Filter · Only copy timed events
  3. 3. Formatter · Convert the start time to UTC
  4. 4. Formatter · Convert the end time to UTC
  5. 5. Microsoft 365 · Create the event in Outlook Calendar
View template →Use template
KlaviyoSlackKlaviyo → Slack1 templateSend new Klaviyo profiles to Slack
Explore Klaviyo → Slack integrations →

Klaviyo · 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. 1. Klaviyo · New Profile
  2. 2. Slack · Notify the customer channel
View template →Use template
WebflowSlackWebflow → Slack1 templateSend new Webflow CMS items to Slack
Explore Webflow → Slack integrations →

Webflow · 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. 1. Webflow · Collection Item Created
  2. 2. Slack · Notify the content channel
View template →Use template
BrevoSlackBrevo → Slack1 templateSend new Brevo list contacts to Slack
Explore Brevo → Slack integrations →

Brevo · 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. 1. Brevo · Marketing List Addition
  2. 2. Slack · Notify the new contacts channel
View template →Use template
JotformSlackJotform → Slack1 templateSend new Jotform submissions to Slack
Explore Jotform → Slack integrations →

Jotform · 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. 1. Jotform · New Submission
  2. 2. Slack · Notify the form response channel
View template →Use template
monday.comSlackmonday.com → Slack1 templateSend new monday.com items to Slack
Explore monday.com → Slack integrations →

monday.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. 1. monday.com · Create Item
  2. 2. Slack · Notify the monday.com item channel
View template →Use template
Google CalendarGoogle SheetsGoogle Calendar → Google Sheets2 templatesLog Google Calendar event changes in Google Sheets · Log new Google Calendar events in Google Sheets
Explore Google Calendar → Google Sheets integrations →

Google Calendar · Google Sheets

Log Google Calendar event changes in Google Sheets

Keep a searchable change log in Google Sheets when an existing Google Calendar event is updated. Each change appends one row with Event ID, Event title, Start, End, Status, Updated and Event URL in columns A-G. Headers are optional: an empty worksheet works immediately, or add these exact labels in row 1 for a readable log. Connect Google Calendar and Google Sheets, browse to the calendar you want to watch, then browse to the destination spreadsheet and worksheet. The primary calendar is preselected and can be changed. Includes its own fictional English and German example. Start and End retain the original ISO timestamps and offsets; all-day events use dates with an exclusive end date. Values are written as plain text. The first poll establishes a baseline without adding history. Edit existing events after that baseline; recently created events within the roughly 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. Rows 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 row even when the displayed title and times are unchanged. Earlier rows are not updated or removed, and manual reruns can append duplicates. This is an append-only change log, not a live calendar mirror; follow the event link for current details. Use a private worksheet when event details should remain restricted.

  1. 1. Google Calendar · Updated Event
  2. 2. Google Sheets · Append calendar change to the log
View template →Use template

Google Calendar · Google Sheets

Log new Google Calendar events in Google Sheets

Keep a searchable register of newly created Google Calendar events in Google Sheets. Each event adds one row with Event ID, Event title, Start, End, Status and Event URL. Prepare these exact headers in columns A-F, connect both accounts, select a calendar and worksheet, then publish. The primary calendar is preselected. Includes its own fictional English appointment example. Start and End retain the original ISO timestamps and offsets; all-day events use dates, with an exclusive end date. Values are written as plain text. The first poll establishes a baseline; create events afterwards. Existing events and later edits or cancellations are not synchronized. This is an append-only creation log, not a live calendar mirror. Follow the event link for current details.

  1. 1. Google Calendar · New Event
  2. 2. Google Sheets · Log calendar event
View template →Use template
Google SheetsGoogle DriveGoogle Sheets → Google Drive2 templatesCreate Google Drive text files from new Google Sheets rows · Create Google Drive project folders from new Google Sheets rows

Google Sheets · Google Drive

Create Google Drive text files from new Google Sheets rows

Create one UTF-8 plain-text file in Google Drive for each new row appended to a selected Google Sheets worksheet. Prepare FileName and Content headers in row 1, connect Google Sheets and Google Drive, browse to the source spreadsheet and worksheet, and optionally choose a destination folder; leaving Parent folder empty saves to My Drive. Both FileName and Content are required. Activate and let the first poll establish a baseline before adding rows. Existing rows and later edits are not imported or synchronized. Append complete rows at the bottom and keep the headers stable while active. Only FileName and Content are copied; other columns remain in the sheet. Includes a fictional English project note with German characters and line breaks. Files inherit destination folder access, no public sharing is added, and manual reruns can create duplicate files.

  1. 1. Google Sheets · New Row Added
  2. 2. Filter · Only create files with a name
  3. 3. Google Drive · Create the row as a text file
View template →Use template

Google Sheets · Google Drive

Create Google Drive project folders from new Google Sheets rows

Prepare a project workspace automatically from your Google Sheets intake list. Add the header Project in row 1 and enter a project name in each new row. FastHook creates one empty Google Drive folder with that name inside the parent folder you select. Connect Google Sheets and Google Drive, choose the source spreadsheet and worksheet, and optionally choose a writable parent folder; without a parent, folders are created in My Drive. Includes its own fictional English project example. Activate and allow the first poll to establish a baseline before adding rows. Append complete rows at the bottom: existing rows and later edits are not imported. Keep the header unchanged and avoid deleting or reordering rows while active. A Project value is required. Separate rows create separate folders even when their names match. This template does not copy files, change permissions or write a folder link back to the sheet. Access follows the destination folder.

  1. 1. Google Sheets · New Row Added
  2. 2. Google Drive · Create project folder
View template →Use template
StripeDiscordStripe → Discord1 templateSend new Stripe customers to a Discord channel
Explore Stripe → Discord integrations →

Stripe · Discord

Send new Stripe customers to a Discord channel

Post a Discord notification when a customer is created in Stripe. Connect Stripe and Discord, wait for the Stripe source to show Connected, then choose a Discord text channel. The instant trigger listens only for customer.created events from the connected Stripe account; existing customers and later updates are not imported. Each message contains the customer name, email, Stripe customer ID and live-mode flag. New customers do not necessarily represent a payment or subscription. No payment details, addresses, tax IDs, descriptions or metadata are forwarded. User, role and everyone mentions are disabled, so customer text cannot trigger Discord notifications accidentally. Test with a fictional customer in Stripe sandbox first and choose a channel whose members may see customer names and email addresses. Name and email may be empty when Stripe does not provide them. Includes its own fictional German customer example with no real customer data.

  1. 1. Stripe · Customer Created
  2. 2. Discord · Notify the customer channel
View template →Use template
Google DriveDiscordGoogle Drive → Discord1 templateSend new Google Drive files to a Discord channel
Explore Google Drive → Discord integrations →

Google Drive · Discord

Send new Google Drive files to a Discord channel

Post a Discord notification when a new file is created in a selected Google Drive folder. Connect Google Drive and Discord, browse to the folder to watch, then choose a Discord text channel. 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. Activate the workflow and let its first poll establish a baseline before creating a test file; older files and later edits are not sent. Each message includes the file name, type and direct Drive URL. User, role and everyone mentions are disabled, and Drive links are not expanded automatically. File names and URLs become visible to members of the selected Discord channel, while Drive sharing permissions stay unchanged. Includes a fictional German project document example with no customer data.

  1. 1. Google Drive · New Files
  2. 2. Discord · Notify the files channel
View template →Use template
Google SheetsDiscordGoogle Sheets → Discord1 templateSend new Google Sheets rows to a Discord channel
Explore Google Sheets → Discord integrations →

Google Sheets · Discord

Send new Google Sheets rows to a Discord channel

Post a Discord notification when a new row is appended to a selected Google Sheets worksheet. Connect Google Sheets and Discord, browse to the spreadsheet and worksheet, then choose a Discord text channel. Use Title, Owner, Status and Details headers in row 1 and append one complete item per row. The prepared message includes those four columns, the worksheet name, row number and spreadsheet link. Edit the mappings if your headers differ. Activate the workflow and let its first poll establish a baseline before adding a test row; existing rows and later edits are not sent. Avoid deleting or reordering rows while the workflow is active. User, role and everyone mentions are disabled, and spreadsheet links are not expanded automatically. Row values become visible to members of the selected Discord channel, while spreadsheet sharing permissions stay unchanged. Includes a fictional German project update example with no customer data.

  1. 1. Google Sheets · New Row Added
  2. 2. Discord · Notify the updates channel
View template →Use template
GmailDiscordGmail → Discord1 templateSend matching Gmail emails to a Discord channel
Explore Gmail → Discord integrations →

Gmail · Discord

Send matching Gmail emails to a Discord channel

Notify a Discord channel when a new Gmail message matches a focused search. Connect Gmail and Discord, review the prefilled subject:"[Discord]" query, then browse to the destination Discord text channel. Each notification contains the subject, sender, received date and a direct Gmail conversation link. Email bodies, attachments, recipients and mailbox history are not copied. Only newly received matching inbox messages are processed after activation; existing mail is not backfilled and label changes do not create notifications. The Gmail link opens only for people who already have access to that mailbox. Subject and sender details become visible to members of the selected Discord channel, so choose a suitable destination. User, role and everyone mentions are disabled, and links are not expanded automatically. Includes its own fictional German support email example with no real customer data. This is a one-way alert rather than email synchronization. Replies that still match the Gmail query can create additional notifications.

  1. 1. Gmail · New Email Matching Search
  2. 2. Discord · Notify the email channel
View template →Use template
GitHubDiscordGitHub → Discord1 templateSend new GitHub issues to a Discord channel
Explore GitHub → Discord integrations →

GitHub · Discord

Send new GitHub issues to a Discord channel

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.

  1. 1. GitHub · Issues
  2. 2. Discord · Notify the issue channel
View template →Use template
MailchimpSlackMailchimp → Slack1 templateNotify Slack about new Mailchimp subscribers

Mailchimp · 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. 1. Mailchimp · Subscribe
  2. 2. Slack · Notify the subscriber channel
View template →Use template
CalendlyGoogle SheetsCalendly → Google Sheets1 templateLog new Calendly bookings in Google Sheets

Calendly · Google Sheets

Log new Calendly bookings in Google Sheets

Keep a booking register in Google Sheets when a Calendly invitee schedules a meeting. FastHook checks the connected Calendly user's bookings every 5 minutes, so this template works with Calendly Free without webhook access. Connect Calendly and Google Sheets, then use Browse to choose the destination spreadsheet and worksheet. Append Values writes Invitee name, Email, Booking created UTC, Invitee timezone, Rescheduled, Event URI and Invitee URI into columns A-G in that order. Headers are optional: an empty worksheet works immediately, or add your own first row. Existing bookings are not backfilled, and cancellation or no-show events are excluded. Booking created time is not the meeting start time. Rescheduled bookings can create another row with Rescheduled true, and group bookings can create one row per invitee. Includes its own fictional German-name example. Custom answers, meeting locations and cancel or reschedule links are not copied. Invitee names and email addresses become visible to everyone who can access the worksheet, so use a private spreadsheet. RAW input keeps formula-looking values as text. Manual reruns can append duplicate rows.

  1. 1. Calendly · New Booking
  2. 2. Google Sheets · Append booking to the register
View template →Use template
PayPalGoogle SheetsPayPal → Google Sheets1 templateLog completed PayPal payments in Google Sheets
Explore PayPal → Google Sheets integrations →

PayPal · Google Sheets

Log completed PayPal payments in Google Sheets

Append one Google Sheets row when PayPal sends PAYMENT.CAPTURE.COMPLETED for the connected REST app. Record Capture ID, Status, Gross amount, Currency, Capture created UTC and Webhook event ID in columns A-F. Connect PayPal and Google Sheets, then use Browse to select the spreadsheet and worksheet. Append Values supports an empty worksheet without column headers. The trigger records completed captures, not merely approved orders, pending payments, authorizations or legacy sale events. Each capture becomes its own row; an order with multiple captures can produce multiple rows. The amount is the gross capture amount in the original currency, preserved as a decimal string without division by 100 or currency conversion. Capture creation time is not settlement time or the time the webhook arrived. Use a PayPal sandbox app and a fictional completed sandbox payment for testing, and wait for Connected before sending it. Existing payments are not imported. Payer names, email addresses, addresses, payment instruments, item details and notes are not copied. RAW input prevents formula-looking strings from being interpreted as formulas. Refunds, reversals, disputes and later changes do not update previous rows. Manual reruns can duplicate rows. This is a capture-event register, not a balance, tax or accounting ledger.

  1. 1. PayPal · Payment · Capture · Completed
  2. 2. Google Sheets · Append completed capture to the register
View template →Use template
DropboxSlackDropbox → Slack1 templateNotify Slack about new or updated Dropbox files

Dropbox · 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. 1. Dropbox · File Added or Updated
  2. 2. Slack · Notify the document channel
View template →Use template
JiraSlackJira → Slack1 templateNotify Slack about new Jira issues
Explore Jira → Slack integrations →

Jira · 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. 1. Jira · Issue Created
  2. 2. Slack · Notify the issue channel
View template →Use template
MailchimpGoogle SheetsMailchimp → Google Sheets1 templateLog new Mailchimp subscribers in Google Sheets

Mailchimp · Google Sheets

Log new Mailchimp subscribers in Google Sheets

Append a Google Sheets row when Mailchimp sends a subscribe event for a selected audience. Keep a subscription-event register with Email, Audience ID, Event fired time and Event type in columns A-D. Connect Mailchimp and Google Sheets, choose the audience using the standard Audiences browser and browse to the destination spreadsheet and worksheet. Append Values works with an empty worksheet; headers are optional. Source fired_at text is preserved exactly without assigning a timezone that is absent from the webhook. Includes its own fictional Hamburg subscriber example with German characters in unused merge fields. Only email and subscription-event metadata are copied; names, interests, signup IPs and other merge fields are excluded. Use a sheet whose access is appropriate for subscriber email addresses. RAW input prevents formula-looking source strings from being interpreted as formulas. Wait for Connected before creating a test subscription. New subscribe events can include resubscriptions, so separate legitimate events for one address can create multiple rows. Existing contacts are not backfilled. Unsubscribe, cleaned, email-change and profile events do not update or remove past rows: this is not a current eligible-recipient list or marketing-consent record. No campaigns or messages are sent and no new audience membership is created by this template. Manual reruns can duplicate rows.

  1. 1. Mailchimp · Subscribe
  2. 2. Google Sheets · Append subscription event to the register
View template →Use template
PipedriveSlackPipedrive → Slack1 templateNotify Slack about new Pipedrive deals

Pipedrive · 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. 1. Pipedrive · Create Deal
  2. 2. Slack · Notify the new deal channel
View template →Use template
TypeformSlackTypeform → Slack1 templateNotify Slack about new Typeform responses

Typeform · 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. 1. Typeform · Form Response
  2. 2. Slack · Notify the form response channel
View template →Use template
CalendlySlackCalendly → Slack1 templateNotify Slack about new Calendly bookings

Calendly · 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. 1. Calendly · New Booking
  2. 2. Slack · Notify the booking channel
View template →Use template
GitLabSlackGitLab → Slack1 templateNotify Slack about new GitLab merge requests
Explore GitLab → Slack integrations →

GitLab · 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. 1. GitLab · Merge Request
  2. 2. Slack · Notify the review channel
View template →Use template
AirtableSlackAirtable → Slack1 templateNotify Slack about new Airtable records
Explore Airtable → Slack integrations →

Airtable · 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. 1. Airtable · Record Created
  2. 2. Slack · Announce the new record
View template →Use template
SlackDiscordSlack → Discord1 templateShare Slack announcements in Discord
Explore Slack → Discord integrations →

Slack · 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. 1. Slack · New Keyword Mention
  2. 2. Discord · Share the announcement
View template →Use template
SlackLinearSlack → Linear1 templateCreate Linear issues from Slack issue messages
Explore Slack → Linear integrations →

Slack · 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. 1. Slack · New Keyword Mention
  2. 2. Linear · Capture the Slack issue
View template →Use template
SlackClickUpSlack → ClickUp1 templateCreate ClickUp tasks from Slack task messages
Explore Slack → ClickUp integrations →

Slack · 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. 1. Slack · New Keyword Mention
  2. 2. ClickUp · Capture the Slack task
View template →Use template
Google CalendarSlackGoogle Calendar → Slack2 templatesAnnounce Google Calendar event changes in Slack · Announce new Google Calendar events in Slack
Explore Google Calendar → Slack integrations →

Google 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. 1. Google Calendar · Updated Event
  2. 2. Slack · Notify the channel about the event change
View template →Use template

Google 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. 1. Google Calendar · New Event
  2. 2. Slack · Notify the planning channel
View template →Use template
SlackGoogle CalendarSlack → Google Calendar1 templateCreate Google Calendar events from marked Slack messages
Explore Slack → Google Calendar integrations →

Slack · 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. 1. Slack · New Keyword Mention
  2. 2. Google Calendar · Create an event from the marked message
View template →Use template
HubSpotGmailHubSpot → Gmail1 templateSend Gmail notifications for new HubSpot contacts
Explore HubSpot → Gmail integrations →

HubSpot · Gmail

Send Gmail notifications for new HubSpot contacts

Email a selected reviewer when a new contact is created in HubSpot. Use this to notify an onboarding owner who follows CRM intake from their inbox. Connect HubSpot and Gmail, enter a fixed recipient address, then test with one fictional contact. Each plain-text email includes the contact ID, HubSpot account ID, creation event ID and a direct link to the CRM record. The instant trigger listens only for contact.creation events received after activation. Includes its own fictional contact-created example. HubSpot creation webhooks provide record IDs, not the complete contact profile, so contact names, email addresses, company details and other properties are not copied. Opening the record link requires existing HubSpot access. Existing contacts, later property edits, merges and deletions are not imported or synchronized. The recipient is configured by you; this does not email the new contact or send a marketing campaign. No contact permissions are changed. Emails are sent from the connected Gmail account and appear in Sent. No HTML, Cc, Bcc or attachments are configured. Gmail limits apply; manual reruns or ambiguous provider retries can resend a notification. Use your own email address for the first test.

  1. 1. HubSpot · Contact Creation
  2. 2. Gmail · Email the new HubSpot contact notification
View template →Use template
SlackGmailSlack → Gmail1 templateEmail marked Slack messages with Gmail
Explore Slack → Gmail integrations →

Slack · 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. 1. Slack · New Keyword Mention
  2. 2. Gmail · Email the marked Slack message
View template →Use template
GitHubGmailGitHub → Gmail3 templatesEmail published GitHub releases with Gmail · Email new GitHub pull requests with Gmail
Explore GitHub → Gmail integrations →

GitHub · Gmail

Email published GitHub releases with Gmail

Keep release reviewers informed with a plain-text email when a GitHub release is published. Each message contains the tag, optional title, repository, author, publication time, pre-release flag, original link and complete release notes. Connect the FastHook GitHub App, browse to the repository to watch, connect Gmail and enter a fixed recipient address. The published action filter is already selected; published pre-releases are included. Drafts, edits, deletions and other release actions do not send another email. Includes its own fictional English Dresden handoff example with German Unicode. Only new publication webhooks after activation are processed, not existing releases. This does not confirm deployment success, download assets or synchronize later note changes. Release notes remain literal Markdown in plain text; binary assets, source code and attachments are excluded. Emails are sent from your connected Gmail account and appear in Sent. Recipients can read the copied notes; opening a private release still requires GitHub access. No public sharing, HTML, Cc or Bcc is configured. Gmail sending limits apply. Manual reruns, ambiguous provider retries, or unpublishing and republishing can send duplicate emails. Use your own email address for the first test.

  1. 1. GitHub · Release
  2. 2. Gmail · Email the release reviewer
View template →Use template

GitHub · Gmail

Email new GitHub pull requests with Gmail

Give reviewers an inbox summary when a GitHub pull request is opened. Each email includes the PR number and title, repository, author, source and target branches, draft flag, creation time and source link. Connect the FastHook GitHub App, browse to the repository to watch, connect Gmail and enter a fixed recipient address. The opened action filter is already selected; draft PRs are included. Edits, new commits, reviews, closed and reopened PRs do not send another email. Includes its own fictional Hamburg onboarding example with German Unicode. Emails are sent from your connected Gmail account and appear in Sent. PR bodies, code changes, comments and attachments are not copied. This processes new webhook events after activation, not existing PRs, and does not assign reviewers or synchronize review status. The recipient can read the title and branch details; opening a private PR still requires GitHub access. Messages use plain text, with no HTML, Cc or Bcc configured. Gmail sending limits apply. Manual reruns or retries after ambiguous provider failures can resend a notification. Use your own email address for the first test.

  1. 1. GitHub · Pull Request
  2. 2. Gmail · Email the pull request reviewer
View template →Use template

GitHub · Gmail

Email new GitHub issues with Gmail

Let project reviewers follow newly opened GitHub issues from their inbox. Each email includes the issue number and title, repository, author, creation time and source link. Connect the FastHook GitHub App, browse to the repository to watch, connect Gmail and enter a fixed recipient address. The opened action filter is already selected; edits, comments, closed and reopened issues do not send another email. Includes its own fictional Bremen documentation example with German Unicode. Emails are sent from your connected Gmail account and appear in Sent. Issue bodies, attachments and labels are not copied. This workflow processes new webhook events after activation, not existing issues, and does not synchronize later changes or replies. The recipient can read the issue title and repository details; opening a private issue still requires GitHub access. Messages use plain text, with no HTML, Cc or Bcc configured. Gmail sending limits apply. Manual reruns or retries after ambiguous provider failures can resend a notification. Use your own email address for the first test.

  1. 1. GitHub · Issues
  2. 2. Gmail · Email the issue reviewer
View template →Use template
Google DriveGmailGoogle Drive → Gmail1 templateEmail new Google Drive files with Gmail
Explore Google Drive → Gmail integrations →

Google Drive · Gmail

Email new Google Drive files with Gmail

Send an email when a new file is created in a selected Google Drive folder. Each message includes its name, file type, creation timestamp and a direct Drive link. Connect Google Drive, browse to the folder to watch, connect Gmail and enter a fixed recipient address. Leaving the folder empty watches the connected Drive. Only direct children are monitored; subfolders are not scanned. Detection uses creation time, so moving an older file into the folder is not guaranteed to trigger. Polling may include files created roughly one minute before setup; older files and later edits are not imported. Includes its own fictional Leipzig handoff example with German Unicode. Emails are plain text and appear in the connected Gmail account's Sent folder. File contents, descriptions, owners and attachments are not copied. Recipients can see the file name and link, but Drive sharing permissions stay unchanged. Gmail sending limits apply. Manual reruns or retries after ambiguous provider failures can resend a notification. Use your own email address for the first test.

  1. 1. Google Drive · New Files
  2. 2. Gmail · Email the new file notification
View template →Use template
Google CalendarGmailGoogle Calendar → Gmail1 templateEmail new Google Calendar events with Gmail
Explore Google Calendar → Gmail integrations →

Google Calendar · Gmail

Email new Google Calendar events with Gmail

Send an email when a new event is added to your selected Google Calendar. Each message includes the event title, start, end and a direct calendar link. Connect Google Calendar, browse to the calendar to watch, connect Gmail and enter a fixed recipient address. Includes its own fictional Dresden planning example with German Unicode. Timed events preserve the original timestamps and timezone offsets; all-day events use dates, with an exclusive end date. The first poll establishes a baseline: create new events afterwards. Existing events, later edits and cancellations are not synchronized. This announces event creation rather than sending an upcoming-event reminder. Emails are plain text, sent from your connected Gmail account and visible in Sent. Descriptions, attendee addresses and attachments are not copied. The recipient can read the event title and times; opening the source link still requires calendar access. Gmail sending limits apply. Manual reruns or retries after ambiguous provider failures can resend a notification. Use your own email address for the first test.

  1. 1. Google Calendar · New Event
  2. 2. Gmail · Email the event notification
View template →Use template
TrelloGmailTrello → Gmail1 templateEmail new Trello cards with Gmail
Explore Trello → Gmail integrations →

Trello · Gmail

Email new Trello cards with Gmail

Send an email when a new card is created on a selected Trello board. The message includes the card name, board, list, creation time and direct card link, so reviewers can follow project activity from their inbox. Connect Trello and Gmail, browse to the board to watch and enter a fixed recipient address. The email is sent from your connected Gmail account and appears in Sent. Includes its own fictional Stuttgart review example with German Unicode. 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, copies, moves and later edits do not send an email. Card descriptions, attachments and members are not copied. The recipient can see the card title and board details; opening the card still requires Trello access. Messages use plain text, with no HTML, Cc or Bcc configured. Gmail sending limits apply. A manual rerun or a retry after an ambiguous provider failure can resend a message; this is a notification, not a two-way sync or an exactly-once delivery guarantee. Use your own address for the first test.

  1. 1. Trello · Create Card
  2. 2. Gmail · Email the card reviewer
View template →Use template
GitHubGoogle DriveGitHub → Google Drive3 templatesSave published GitHub release notes in Google Drive · Save new GitHub pull requests as Google Drive text files

GitHub · Google Drive

Save published GitHub release notes in Google Drive

Archive published GitHub release notes as UTF-8 text files in Google Drive. Each file contains the tag, optional release title, full notes, repository, author, publication time, pre-release flag and original GitHub link. Connect GitHub and Google Drive, browse to a repository and optionally select a destination folder. The Actions filter is prefilled with published; stable releases and published pre-releases are included. Leaving Parent folder empty saves to My Drive. Filenames use repository and release IDs, so tags containing slashes or German characters do not become folder paths. Includes its own fictional English Nürnberg release example. Only new publication events received after activation are processed; existing releases are not imported. Drafts, edits and deleted releases do not create or update files. Markdown remains plain source text; release assets, source code and binaries are not downloaded. This is a release-notes snapshot, not a deployment check or synchronized backup. Files inherit destination folder access; no public sharing is added. Manual reruns or unpublishing and republishing a release can create duplicates.

  1. 1. GitHub · Release
  2. 2. Google Drive · Archive GitHub release notes
View template →Use template

GitHub · Google Drive

Save new GitHub pull requests as Google Drive text files

Create a UTF-8 text file in Google Drive whenever a GitHub pull request is opened. Files include the PR title, full description, repository, author, creation time, draft status, source and target branches, and original PR link. Connect GitHub and Google Drive, browse to a repository and optionally select a destination folder. The Actions filter is prefilled with opened; draft PRs are included. Leaving Parent folder empty saves to My Drive. Filenames use the repository ID and PR number. Includes its own fictional English Freiburg example with German characters. Only new opened events received after activation are processed; existing PRs are not imported. Edits, new commits, reviews, closed and reopened PRs do not create or update files. Markdown remains plain source text; code changes, comments and linked attachments are not downloaded. This is a one-time snapshot, not a code backup, reviewer assignment or two-way synchronization. Files inherit destination folder access; no public sharing is added. Manual reruns can create duplicate files.

  1. 1. GitHub · Pull Request
  2. 2. Google Drive · Save GitHub pull request as a text file
View template →Use template

GitHub · Google Drive

Save new GitHub issues as Google Drive text files

Create a UTF-8 text file in Google Drive whenever a GitHub issue is opened. Files include the issue title, full description, repository, author, creation time and original issue link. Connect GitHub and Google Drive, browse to a repository and optionally select a destination folder. The Actions filter is prefilled with opened. Leaving Parent folder empty saves to My Drive. Each filename uses the repository ID and issue number to distinguish issues across repositories. Includes its own fictional English Leipzig example. Only new opened events received after activation are processed; existing issues are not imported. Edits, comments, closed and reopened issues do not create or update files. Markdown remains plain source text; linked attachments are not downloaded. This is a one-time snapshot, not an issue backup or two-way synchronization. Files inherit destination folder access; no public sharing is added. Manual reruns can create duplicate files.

  1. 1. GitHub · Issues
  2. 2. Google Drive · Save GitHub issue as a text file
View template →Use template
StripeNotionStripe → Notion7 templatesCreate Notion review pages for failed Stripe payments · Create Notion review pages for new Stripe refunds
Explore Stripe → Notion integrations →

Stripe · Notion

Create Notion review pages for failed Stripe payments

Keep a review page in Notion for each failed Stripe PaymentIntent attempt. Select an accessible parent with Browse; the new child page records PaymentIntent ID, attempted amount in Stripe minor units, currency, event Unix seconds, live mode and Event ID, followed by three follow-up prompts. Each failed attempt creates its own page, including repeat failures for the same PaymentIntent. Check current status in Stripe before taking action: a later retry may already have succeeded. Amounts are not converted; 2900 EUR means 29.00 EUR, while 2900 JPY means 2900 JPY. Includes a fictional English Würzburg workshop example with German characters. Earlier failures are not imported and later success does not update or close the page. Customer contacts, card details, client secrets, raw errors and metadata are excluded. Pages inherit parent access. Creates child pages, not database items or invoice dunning schedules. This workflow does not retry payments, issue refunds or contact customers. Test in Stripe sandbox first. Manual reruns can duplicate pages.

  1. 1. Stripe · Payment Intent Payment Failed
  2. 2. Notion · Create the failed payment review page
View template →Use template

Stripe · Notion

Create Notion review pages for new Stripe refunds

Track each new Stripe refund in a Notion child page under a parent selected with Browse. Records the refund ID, individual refund amount in Stripe minor units, currency, status at creation, event time, live mode and event ID, followed by three review prompts. Two partial refunds create separate pages with their individual amounts, not the payment's cumulative refunded total. A refund.created event can be pending; creation does not confirm that the customer has received the money. Check current status in Stripe. Interpret minor units using the currency: 1000 EUR means 10.00 EUR, while 1000 JPY means 1000 JPY. Includes a fictional English Düsseldorf workshop example with German characters. Uses child pages, not database items. Earlier refunds and later status changes are not imported or synchronized. Customer contacts, card details, refund instructions, reasons and metadata are excluded. Pages inherit parent access. Logs refunds without issuing refunds or sending messages. Test in Stripe sandbox first. Manual reruns can duplicate pages.

  1. 1. Stripe · Refund Created
  2. 2. Notion · Create the refund review page
View template →Use template

Stripe · Notion

Create Notion review pages for successful Stripe payments

Keep a Notion payment review page for each successful Stripe PaymentIntent, including payments without an invoice. Browse to a parent page; each child page records PaymentIntent ID, Amount received (Stripe minor units), Currency, Event created (Unix seconds), Live mode and Event ID, followed by a Payment review section and three reconciliation prompts. Listens only for payment_intent.succeeded; failed, pending and canceled payments do not create pages. Uses amount_received rather than the requested amount: 4900 EUR minor units means 49.00 EUR, while 4900 JPY means 4900 JPY. Check the currency before interpreting amounts. Includes its own fictional English Stuttgart workshop example with German characters. These are child pages, not database items. Existing payments and later refunds, disputes, invoice changes and bank payouts are not imported or synchronized. Success does not prove settlement in your bank or net revenue. Customer contacts, card details, client secrets and metadata are excluded. Pages inherit parent access. The template does not charge customers, issue refunds, fulfill orders or send messages. Test in Stripe sandbox first; Live mode false identifies test data. Manual reruns can duplicate pages.

  1. 1. Stripe · Payment Intent Succeeded
  2. 2. Notion · Create the payment review page
View template →Use template

Stripe · Notion

Create Notion review pages for canceled Stripe subscriptions

Open a Notion cancellation review page when a Stripe subscription actually ends. Choose a parent page through Browse; each child page records Subscription ID, final status, currency, event Unix seconds, live mode and Event ID, followed by an editable Cancellation review section and three offboarding prompts. This gives an owner a place to check outstanding obligations and record a decision before changing access. The trigger listens only for customer.subscription.deleted. Setting cancel_at_period_end schedules cancellation and emits an update; the page is created when the subscription ends. Includes its own fictional English Frankfurt ended-trial example. Ended trials and paid subscriptions are included without assuming voluntary churn or lost revenue. The event timestamp identifies the termination notification, not an earlier cancellation request. Review current Stripe details and your retention policy before acting. Multiple prices are supported without inferring MRR from the first item. This creates child pages, not database items or updates to onboarding pages. Existing cancellations and later changes are not imported or synchronized. Customer contacts, cancellation feedback and comments, payment details and metadata are excluded. Pages inherit parent access. The workflow does not cancel subscriptions, issue refunds, revoke access or contact customers. Test in Stripe sandbox first; Live mode false marks test data. Manual reruns can duplicate pages.

  1. 1. Stripe · Customer Subscription Deleted
  2. 2. Notion · Create the subscription offboarding review page
View template →Use template

Stripe · Notion

Create Notion onboarding pages for new Stripe subscriptions

Create a dedicated Notion onboarding page when a Stripe subscription is created. Connect Stripe and Notion, then browse to a parent page your Notion integration can access. Each child page contains Subscription ID, status at creation, currency, event Unix seconds, live mode and Event ID, plus editable Onboarding notes and three prepared review prompts. This gives an onboarding owner a place to record an agreed plan before provisioning access. Listens only for customer.subscription.created and includes its own fictional English Leipzig studio trial example. Trials and incomplete subscriptions also produce pages: creation is not proof of payment or entitlement. Review current subscription status in Stripe and apply your access policy before granting anything. Subscriptions may have multiple prices; no first-item total or MRR is inferred. This is a creation snapshot, not a synchronized subscriber database. Existing subscriptions, renewals, later changes and cancellations are not imported or synchronized. Customer contacts, private descriptions, payment details and metadata are not copied. Pages inherit parent access. The workflow does not create subscriptions, charge customers, send messages or grant access. Test in Stripe sandbox first; Live mode false identifies test events. Manual reruns can create duplicate pages.

  1. 1. Stripe · Customer Subscription Created
  2. 2. Notion · Create the subscription onboarding page
View template →Use template

Stripe · Notion

Create Notion pages for paid Stripe invoices

Keep a Notion child page for each new invoice.paid event from Stripe. Connect Stripe and Notion, then browse to an accessible parent page. Each page title contains the invoice number and Stripe invoice ID; its prepared content records Invoice ID, Amount paid in Stripe minor units, Currency, Event created in Unix seconds, Live mode and Event ID, followed by Reconciliation notes. This gives your team a place to review an invoice event and add internal notes. Includes a fictional English Frankfurt workshop example. Only events received after activation are processed; existing invoices, later edits and refunds are not imported or synchronized. Amounts stay in original minor units: 1900 EUR means 19.00 EUR, while 1900 JPY means 1900 JPY. Zero-value invoices are supported. Invoice Paid can also mean customer balance or a payment recorded outside Stripe; it does not prove a new card charge or bank payout. Customer contact information, billing addresses, card details, invoice PDFs, hosted invoice URLs and metadata are not copied. Pages inherit access from the selected Notion parent. This creates child pages, not database rows or a full accounting ledger. Test with a fictional Stripe sandbox invoice first. Manual reruns can create another page.

  1. 1. Stripe · Invoice Paid
  2. 2. Notion · Create the paid invoice review page
View template →Use template

Stripe · Notion

Create Notion onboarding pages for new Stripe customers

Create a customer onboarding page in Notion when a new Stripe customer is created. Connect Stripe and Notion, then browse to an accessible parent page. Each child page title includes the customer name, email and Stripe customer ID, followed by Onboarding, Notes and Follow-up sections ready for your team. Customer ID identifies the page even when name or email is missing. Includes its own fictional English sandbox example with German characters. Only customer.created events after activation are processed; historical customers and later edits are not imported or synchronized. Creating a customer does not confirm a payment or subscription. No payment details, addresses, tax IDs, descriptions or metadata are copied. Access follows the selected Notion parent, so choose one appropriate for customer contact information. This creates child pages, not database rows. Test with a fictional Stripe sandbox customer first.

  1. 1. Stripe · Customer Created
  2. 2. Notion · Create customer onboarding page
View template →Use template
StripeTrelloStripe → Trello7 templatesCreate Trello review tasks for new Stripe refunds · Create Trello offboarding tasks for canceled Stripe subscriptions
Explore Stripe → Trello integrations →

Stripe · Trello

Create Trello review tasks for new Stripe refunds

Put new Stripe refunds in a Trello review queue. Choose a board and list with Browse; each refund.created event creates a card with Refund ID, individual refund amount in Stripe minor units, currency, status at creation, event time, live mode and Event ID, followed by four manual review prompts. Two partial refunds create separate tasks with their own amounts, not the payment's cumulative refunded total. Creation can be pending and does not confirm that the customer has received the money; check current status in Stripe. For currency minor units, 700 EUR means 7.00 EUR, while 700 JPY means 700 JPY. Includes its own fictional English Köln workshop example with German characters. Earlier refunds and later status changes are not imported or synchronized. Customer contacts, card details, refund reasons, instructions and metadata are excluded. Cards inherit board visibility. The workflow logs refunds without issuing refunds, contacting customers or closing cards automatically. Test in Stripe sandbox first. Manual reruns can duplicate tasks.

  1. 1. Stripe · Refund Created
  2. 2. Trello · Create the refund review task
View template →Use template

Stripe · Trello

Create Trello offboarding tasks for canceled Stripe subscriptions

Queue a Trello offboarding review when a Stripe subscription actually ends. Select a board and list with Browse; each customer.subscription.deleted event creates a card containing Subscription ID, final status, currency, event Unix seconds, live mode and Event ID, plus four review prompts. Scheduling cancel_at_period_end only emits an update and does not create a card until termination. Includes a fictional English Bremen studio ended-trial example with German characters. Ended trials and paid subscriptions are included without assuming voluntary churn or lost revenue. The event time is the termination notification, not the earlier cancellation request. Multiple prices are supported without inferring MRR from the first item. Review current Stripe details, outstanding invoices and your retention policy before changing access. Existing cancellations and later edits are not imported or synchronized; onboarding cards are not updated. Customer contacts, cancellation feedback/comments, private descriptions, payment details and metadata are excluded. Cards inherit board visibility. The template creates a review task; it does not cancel subscriptions, issue refunds, revoke access or contact customers. Test in Stripe sandbox first. Manual reruns can duplicate cards.

  1. 1. Stripe · Customer Subscription Deleted
  2. 2. Trello · Create the subscription offboarding task
View template →Use template

Stripe · Trello

Create Trello review cards for successful Stripe payments

Give successful Stripe payments a place in your Trello review queue. Choose a board and list with Browse; each new payment_intent.succeeded event creates a card with PaymentIntent ID, Amount received (Stripe minor units), Currency, Event created (Unix seconds), Live mode and Event ID, followed by four manual review prompts. Includes payments without an invoice and its own fictional English Dresden workshop example with German characters. Uses amount_received rather than the requested amount: 4900 EUR minor units means 49.00 EUR, while 4900 JPY means 4900 JPY. Failed, pending and canceled payments do not create cards. Check Stripe and delivery requirements before approving fulfillment; payment success does not confirm settlement in your bank. Existing payments and later refunds, disputes and payouts are not imported or synchronized. Customer contacts, card details, client secrets and metadata are excluded. Cards inherit board visibility, so select a board appropriate for payment records. This workflow does not charge customers, issue refunds, fulfill orders or send messages. Test with a fictional Stripe sandbox payment first; Live mode false identifies test data. Manual reruns can duplicate cards.

  1. 1. Stripe · Payment Intent Succeeded
  2. 2. Trello · Create the successful payment review task
View template →Use template

Stripe · Trello

Create Trello onboarding tasks for new Stripe subscriptions

Start a manual onboarding queue when a Stripe subscription is created. Connect Stripe and Trello, then browse to your board and list. Each card records Subscription ID, status at creation, currency, event Unix seconds, live mode and Event ID, followed by a short onboarding review checklist. Listens only for customer.subscription.created and includes its own fictional English Stuttgart studio trial example. Trials and incomplete subscriptions also create cards: subscription creation is not proof of payment or permission to grant access. Verify current subscription status and your onboarding policy in Stripe before provisioning anything. A subscription may contain multiple prices; this task does not infer a total, paid revenue or MRR from the first item. Existing subscriptions, renewals, status changes and cancellations are not imported or synchronized. No customer contacts, payment details or metadata are copied. Cards inherit board visibility. The workflow does not create subscriptions, charge customers, grant access or send messages. Test in Stripe sandbox first; Live mode false identifies test events. Manual reruns can duplicate cards.

  1. 1. Stripe · Customer Subscription Created
  2. 2. Trello · Create the subscription onboarding task
View template →Use template

Stripe · Trello

Create Trello cards for paid Stripe invoices

Turn newly paid Stripe invoices into Trello review tasks. Connect Stripe and Trello, then browse to your board and list. Each card records Invoice ID, amount paid in original Stripe minor units, currency, event Unix time, live-mode flag and Event ID, plus a short handoff checklist. Listens only for invoice.paid and includes an independent fictional English Hamburg invoice example. Paid invoices can include zero-value invoices, customer balance or payments recorded outside Stripe; a card is not proof of a new card charge, payout or an order ready to ship. Verify the invoice and delivery requirements in Stripe before fulfilling anything. Amounts are not converted: 1900 EUR means 19.00 EUR, while 1900 JPY means 1900 JPY. Only future events create cards. Existing invoices, edits, refunds and disputes are not imported or synchronized, and recurring paid invoices can create separate tasks. No customer contacts, addresses, payment details, invoice PDFs, hosted links or metadata are copied. Cards inherit board visibility. The workflow does not charge customers, send messages, ship orders or issue refunds. Test in Stripe sandbox first; Live mode false identifies test events. Manual reruns can duplicate cards.

  1. 1. Stripe · Invoice Paid
  2. 2. Trello · Create the paid invoice review task
View template →Use template

Stripe · Trello

Create Trello follow-up cards for failed Stripe payments

Create a Trello follow-up card when a Stripe PaymentIntent payment attempt fails. Connect Stripe and Trello, then browse to a board and list for payment review. The card contains the PaymentIntent ID, attempted amount in original Stripe minor units, currency, event creation time in Unix seconds, event ID and live-mode flag, followed by a short review checklist. Assign an owner in Trello and check the latest payment status in Stripe before contacting anyone: a later retry may already have succeeded. Each new failed-attempt event creates a separate card, even for the same PaymentIntent. Existing failures are not imported, and later success does not update or close the card. Amounts are not converted: 2900 EUR means 29.00 EUR, while 2900 JPY means 2900 JPY. This does not retry charges, issue refunds, send customer messages or implement invoice retry schedules. No customer contact details, card data, client secrets, raw error messages or metadata are copied. Cards inherit board visibility. Includes a fictional English Nürnberg workshop example. Test in Stripe sandbox first; Live mode false identifies sandbox events. Manual reruns can create duplicate cards.

  1. 1. Stripe · Payment Intent Payment Failed
  2. 2. Trello · Create the payment review card
View template →Use template

Stripe · Trello

Create Trello onboarding cards for new Stripe customers

Start a customer onboarding card in Trello when a new customer is created in Stripe. Each card includes the customer name, email, customer ID, event ID and live-mode flag. Connect Stripe and Trello, then browse to the destination board and list. Includes a fictional English sandbox example with German characters. Only customer.created events received after activation are processed; existing customers and later edits are not imported or synchronized. A new customer record does not mean a payment or subscription exists. Customer ID remains in the card title even if the name is blank, and name or email may be empty. No payment details, addresses, tax IDs or metadata are copied. Choose a private board appropriate for customer contact information. Test with a fictional Stripe sandbox customer first; Live mode false identifies sandbox events.

  1. 1. Stripe · Customer Created
  2. 2. Trello · Create a customer onboarding card
View template →Use template
TrelloGoogle CalendarTrello → Google Calendar1 templateSchedule next-day reviews for new Trello cards
Explore Trello → Google Calendar integrations →

Trello · Google Calendar

Schedule next-day reviews for new Trello cards

Reserve a 30-minute review in Google Calendar when a new Trello card is created. Connect Trello and Google Calendar, browse to the source board and destination calendar, then keep the prepared date mappings. Two Formatter steps set the review to exactly 24 hours after the Trello creation timestamp and its end 30 minutes later. Adjust the +1 day and +30 minutes expressions if your team needs a different interval. Each event uses the card name in its title and includes the card ID and a Trello link. Includes its own fictional English Hannover planning example with German characters. Publish and wait for the Trello webhook to show Instant before creating cards; registration can take up to 15 minutes. This listens for createCard only: existing cards, copies, moves, later edits and due-date changes are not synchronized. The schedule uses creation time, not the card due date, business hours or working days. UTC calculations preserve the instant; Google Calendar displays it in your calendar timezone, and daylight-saving changes can shift the local clock time. No availability check is performed, so reviews may overlap. Descriptions, comments, attachments and member details are not copied. No attendees or invitation emails are added; the selected calendar's normal visibility and reminders apply, and the Trello link still requires board access. Test on a dedicated calendar first. Manual reruns can create duplicate events.

  1. 1. Trello · Create Card
  2. 2. Formatter · Set review to 24 hours after creation
  3. 3. Formatter · End review 30 minutes later
  4. 4. Google Calendar · Create the card review event
View template →Use template
StripeGoogle SheetsStripe → Google Sheets7 templatesLog canceled Stripe subscriptions in Google Sheets · Log new Stripe subscriptions in Google Sheets
Explore Stripe → Google Sheets integrations →

Stripe · Google Sheets

Log canceled Stripe subscriptions in Google Sheets

Maintain a cancellation register when Stripe subscriptions actually end. Append Values saves Subscription ID, Final status, Currency, Event created (Unix seconds), Live mode and Event ID in columns A-F. Choose a spreadsheet and worksheet through Browse; a blank worksheet works without headers. Listens only for customer.subscription.deleted and includes an independent fictional English München canceled-trial example. Setting cancel_at_period_end merely schedules cancellation and sends an update; the row arrives when the subscription ends. Covers ended trials and paid subscriptions without assuming customer intent or calculating lost revenue from the first price. The event timestamp records the end notification, not the earlier cancellation request. RAW preserves numbers and boolean sandbox flags. This is a future-event register, not an update to existing subscription rows or a historical import. Review Stripe for the cancellation cause and outstanding invoices. No customer contacts, cancellation comments, payment details or metadata are copied. Choose worksheet access carefully. Test in Stripe sandbox first; Live mode false identifies test events. The workflow does not cancel subscriptions, issue refunds, revoke access or send messages. Manual reruns can duplicate rows.

  1. 1. Stripe · Customer Subscription Deleted
  2. 2. Google Sheets · Append the ended subscription to the cancellation register
View template →Use template

Stripe · Google Sheets

Log new Stripe subscriptions in Google Sheets

Keep a creation register of Stripe subscriptions in Google Sheets, including trials. Append Values writes Subscription ID, Status at creation, Currency, Event created (Unix seconds), Live mode and Event ID into columns A-F. Connect Stripe and Google Sheets, then browse to a spreadsheet and worksheet. An empty worksheet works immediately; column headers are optional. Listens only for customer.subscription.created and includes its own fictional English Düsseldorf trial example. Status is a snapshot at creation: a trialing or incomplete subscription is not proof of payment. Subscriptions can contain several prices, so this register does not treat the first price as a total or calculate MRR. RAW input preserves numbers and boolean sandbox flags. Existing subscriptions, renewals, status changes and cancellations are not imported or synchronized. No customer contacts, payment details or metadata are copied. Choose a worksheet with appropriate access. Test with Stripe sandbox first; Live mode false identifies test events. This workflow does not create subscriptions, charge customers, grant access or send messages. Manual reruns can duplicate rows.

  1. 1. Stripe · Customer Subscription Created
  2. 2. Google Sheets · Append the new subscription to the register
View template →Use template

Stripe · Google Sheets

Log new Stripe refunds in Google Sheets

Record newly created Stripe refunds in Google Sheets, including partial refunds. Append Values writes Refund ID, This refund amount (Stripe minor units), Currency, Event created (Unix seconds), Live mode, Event ID and Status at creation into columns A-G. Connect Stripe and Google Sheets, then browse to a spreadsheet and worksheet. Headers are optional: an empty worksheet works immediately. Listens only for refund.created. Includes its own fictional English Köln sandbox example with German characters. Two partial refunds produce separate rows containing their own amounts, not the accumulated refunded total. For EUR and USD, 1000 minor units means 10.00; for JPY, 1000 means 1000. Values use RAW input and preserve numbers and sandbox flags. Refund creation does not confirm funds have reached the customer. Status is a snapshot at creation, not the current status; review Stripe for subsequent pending, failed, canceled or completed outcomes. Existing refunds and later updates are not imported or synchronized. Customer contacts, card details, instructions email, metadata and destination details are not copied. This template does not issue refunds or contact customers. Test with Stripe sandbox first; Live mode false identifies test data. Manual reruns can duplicate rows. This is a refund creation register, not a settlement report.

  1. 1. Stripe · Refund Created
  2. 2. Google Sheets · Append new refund to the register
View template →Use template

Stripe · Google Sheets

Log successful Stripe payments in Google Sheets

Record successful Stripe PaymentIntents in Google Sheets, including payments without an invoice. Append Values writes PaymentIntent ID, Amount received (Stripe minor units), Currency, Event created (Unix seconds), Live mode and Event ID into columns A-F. Connect Stripe and Google Sheets, then browse to a spreadsheet and worksheet. Headers are optional: an empty worksheet works immediately. Listens only for payment_intent.succeeded. Includes its own fictional English Leipzig sandbox example with German characters. Uses amount_received, not the requested amount: 4900 EUR minor units means 49.00 EUR, while 4900 JPY means 4900 JPY. Values use RAW input and preserve numbers and sandbox flags. Failed, pending and canceled payments do not trigger this workflow. Existing payments, later refunds, disputes and bank payouts are not imported or synchronized. Payment success does not mean funds have reached your bank. Customer contacts, card details, client secrets and metadata are not copied. This template does not charge customers or manage invoice collection. Test with Stripe sandbox first; Live mode false identifies test data. Manual reruns can duplicate rows. This is a payment event register, not a net revenue or settlement report.

  1. 1. Stripe · Payment Intent Succeeded
  2. 2. Google Sheets · Append successful payment to the register
View template →Use template

Stripe · Google Sheets

Log failed Stripe payments in Google Sheets

Record each failed Stripe PaymentIntent payment attempt in Google Sheets. Append Values writes PaymentIntent ID, Attempted amount (Stripe minor units), Currency, Event created (Unix seconds), Live mode and Event ID into columns A-F. Connect Stripe and Google Sheets, then browse to a spreadsheet and worksheet. Headers are optional: an empty worksheet works immediately. Listens only for payment_intent.payment_failed. Includes its own fictional English Hannover sandbox example with German characters. Amounts use the attempted amount, not amount received: 2900 EUR minor units means 29.00 EUR, while 2900 JPY means 2900 JPY. Values use RAW input and preserve numbers and sandbox flags. A failed attempt is not necessarily a permanent failure; a later attempt can succeed. Separate failed attempts on the same payment can produce separate rows. Successful, pending and canceled payments do not trigger this workflow. Existing payments and later outcomes are not imported or synchronized. Customer contact information, card details, client secrets, metadata and raw error objects are not copied. This template does not retry charges, contact customers, issue refunds or manage invoice collection. Test with Stripe sandbox first; Live mode false identifies test data. Manual reruns can duplicate rows. This is an attempt register, not a current payment-status report.

  1. 1. Stripe · Payment Intent Payment Failed
  2. 2. Google Sheets · Append failed payment attempt to the register
View template →Use template

Stripe · Google Sheets

Log paid Stripe invoices in Google Sheets

Record paid Stripe invoices in Google Sheets with one row per invoice.paid event. Append Values writes Invoice ID, Amount paid (Stripe minor units), Currency, Event created (Unix seconds), Live mode and Event ID into columns A-F. Connect Stripe and Google Sheets, then browse to a spreadsheet and worksheet. Headers are optional: an empty worksheet works immediately. Includes its own fictional English Frankfurt invoice example. Values use RAW input and preserve numeric amounts, zero values and sandbox flags. Amounts are not converted or divided by 100: 1900 EUR minor units means 19.00 EUR, while 1900 JPY means 1900 JPY. Paid invoices can include zero-value invoices, customer balance and payments recorded outside Stripe; a row is not proof of a new card charge or bank payout. Only new invoice.paid events after activation are recorded. Existing invoices, later edits, refunds, drafts and open invoices are not synchronized. Customer names, emails, card details, metadata, invoice PDFs and hosted invoice links are not copied. Test with Stripe sandbox first; Live mode false identifies test data. Manual reruns can duplicate rows. This is an event register, not a complete accounting ledger.

  1. 1. Stripe · Invoice Paid
  2. 2. Google Sheets · Append paid invoice to the register
View template →Use template

Stripe · Google Sheets

Log new Stripe customers in Google Sheets

Keep a customer register in Google Sheets when a new customer is created in Stripe. Append Values writes Customer ID, Name, Email, Created (Unix seconds), Live mode and Event ID into columns A-F in that order. Connect Stripe and Google Sheets, then browse to the destination spreadsheet and worksheet. Headers are optional: an empty worksheet works immediately, or add your own header row. Includes a fictional English sandbox customer with German characters. The instant trigger listens only for customer.created events after activation; existing customers and later edits are not imported or synchronized. A customer record does not mean a payment or subscription was created. Name and email may be blank. Values use RAW input, so names starting with an equals sign remain text. No payment details, addresses, tax IDs or metadata are copied. Use a private worksheet: customer names and emails are visible to everyone who can access it. Test with a fictional customer in Stripe sandbox first; Live mode distinguishes sandbox from live events.

  1. 1. Stripe · Customer Created
  2. 2. Google Sheets · Append customer to the register
View template →Use template
Google SheetsAsanaGoogle Sheets → Asana1 templateCreate Asana tasks from new Google Sheets rows
Explore Google Sheets → Asana integrations →

Google Sheets · Asana

Create Asana tasks from new Google Sheets rows

Turn each newly appended spreadsheet row into an Asana task. Prepare TaskName and Description headers in row 1, connect Google Sheets and Asana, browse to the source spreadsheet and worksheet, and select an Asana workspace and optionally a project. The prepared mappings copy the task title and plain-text description, including line breaks and German characters. A Filter skips rows without a task name; the description may be empty. Use this for a project intake list, workshop preparation or an internal task backlog. Activate and let the first poll establish a baseline before appending complete rows. Existing rows and later edits are not imported or synchronized. Skipped rows are not queued; append a new complete row instead. Keep headers stable and do not delete or reorder rows while active. Tasks have no assignee, due date or custom fields unless you configure these optional inputs. Without a project selection, the task is created in the selected workspace. Includes a fictional English example. Test with a dedicated worksheet and project first. Manual reruns and ambiguous provider failures can create another task; this is a one-way task creation workflow, not a two-way synchronization.

  1. 1. Google Sheets · New Row Added
  2. 2. Filter · Only create tasks with a name
  3. 3. Asana · Create the row as an Asana task
View template →Use template
Google SheetsGmailGoogle Sheets → Gmail1 templateSend personalized Gmail emails from new Google Sheets rows
Explore Google Sheets → Gmail integrations →

Google Sheets · Gmail

Send personalized Gmail emails from new Google Sheets rows

Send one plain-text Gmail email for each new spreadsheet row. Prepare To, Subject and Body headers in row 1, then append one complete message per row. Use a single valid recipient address in To and non-empty Subject and Body cells. Connect Google Sheets and Gmail with permission to send email, browse to the source spreadsheet and worksheet, and keep the prepared mappings. Each row supplies its own recipient, subject and message, so workshop confirmations, internal updates and individual follow-ups can use different text. Includes a fictional English workshop example with German characters and line breaks. Activate and let the first poll establish a baseline before adding rows. Existing rows and later edits are not sent; a prepared Filter stops rows with missing To, Subject or Body cells. Skipped rows are not drafts or a pending queue, so prepare the full row before appending it. Do not delete or reorder rows while active. Emails are sent from the connected Gmail mailbox and recorded in Sent. HTML, attachments, Cc, Bcc and automatic signatures are not included. Only share the source worksheet with people allowed to send email from this account. Use a test worksheet and your own address for the first run. Gmail sending limits apply. This is individual message delivery, not a bulk campaign, scheduled digest or unsubscribe manager. Message IDs do not guarantee exactly-once delivery: manual reruns or ambiguous provider failures can send another email.

  1. 1. Google Sheets · New Row Added
  2. 2. Filter · Only send complete message rows
  3. 3. Gmail · Send the row as a plain-text email
View template →Use template
Google CalendarGoogle DriveGoogle Calendar → Google Drive1 templateCreate Google Drive meeting notes for new Calendar events

Google Calendar · Google Drive

Create Google Drive meeting notes for new Calendar events

Create a UTF-8 meeting-notes text file in Google Drive whenever a new Google Calendar event is created. Each file includes the event title, a link to the current calendar schedule, and Agenda, Notes and Action items sections. Connect Google Calendar and Google Drive, browse to a calendar and optionally select a destination folder. The primary calendar is preselected; leaving Parent folder empty saves to My Drive. Activate and let the first poll establish a baseline before creating events. Existing events are not imported; later edits and cancellations are not synchronized. Timed and all-day events are supported. Dates are not copied, so the calendar link remains the source for the current schedule. Includes a fictional English Bremen workshop example with German characters. Descriptions, attendees, locations and attachments are not copied. Files inherit the destination folder access; no public sharing is added. Creates plain-text files, not Google Docs documents. Manual reruns can create duplicate files.

  1. 1. Google Calendar · New Event
  2. 2. Google Drive · Create meeting-notes text file
View template →Use template
SlackTelegram BotSlack → Telegram Bot1 templateSend Telegram alerts for marked Slack messages
Explore Slack → Telegram Bot integrations →

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. 1. Slack · New Keyword Mention
  2. 2. Telegram Bot · Send marked Slack message to Telegram
View template →Use template
SlackGoogle DriveSlack → Google Drive1 templateArchive Slack messages as Google Drive text files
Explore Slack → Google Drive integrations →

Slack · 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. 1. Slack · New Keyword Mention
  2. 2. Google Drive · Save Slack message as a text file
View template →Use template
SlackGoogle SheetsSlack → Google Sheets1 templateLog Slack feedback in Google Sheets
Explore Slack → Google Sheets integrations →

Slack · 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. 1. Slack · New Keyword Mention
  2. 2. Google Sheets · Append feedback to the log
View template →Use template
SlackNotionSlack → Notion1 templateSave Slack notes as Notion pages
Explore Slack → Notion integrations →

Slack · 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. 1. Slack · New Keyword Mention
  2. 2. Notion · Save the Slack note
View template →Use template
SlackTrelloSlack → Trello1 templateCreate Trello cards from Slack task messages
Explore Slack → Trello integrations →

Slack · 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. 1. Slack · New Keyword Mention
  2. 2. Trello · Capture the Slack task
View template →Use template
GitHubGoogle SheetsGitHub → Google Sheets3 templatesLog published GitHub releases in Google Sheets · Log new GitHub pull requests in Google Sheets

GitHub · Google Sheets

Log published GitHub releases in Google Sheets

Keep a release register in Google Sheets when a GitHub release is published. Append Values writes Release tag, Title, Repository, Author, Release URL, Published at (UTC) and Pre-release into columns A-G in that order. Connect the FastHook GitHub App and Google Sheets, browse to the repository, then select a destination spreadsheet and worksheet. The Actions filter is prefilled with published. Both stable releases and published pre-releases are included. Draft releases, edits and deleted releases do not add rows. Headers are optional; an empty worksheet works immediately. Includes an independent fictional English release example. RAW input keeps titles starting with an equals sign as text. Only new publication events after activation are processed; existing releases are not imported and later changes are not synchronized. This is a release register, not deployment verification. Release notes, assets and source code are not copied. Select a worksheet with appropriate access for repository details. Manual reruns or unpublishing and republishing a release can create duplicate rows.

  1. 1. GitHub · Release
  2. 2. Google Sheets · Append published release to the register
View template →Use template

GitHub · Google Sheets

Log new GitHub pull requests in Google Sheets

Keep a pull request register in Google Sheets whenever a GitHub PR is opened. Append Values writes PR number, Title, Repository, Author, PR URL, Created at (UTC), Source branch, Target branch and Draft into columns A-I in that order. Connect the FastHook GitHub App and Google Sheets, browse to the repository, then choose a destination spreadsheet and worksheet. The Actions filter is prefilled with opened. Draft PRs are included with their draft flag. Edits, commits, reviews, closed and reopened PRs do not add another row. Headers are optional: an empty worksheet works immediately, or add your own header row. Includes an independent fictional English example with German characters. Only new events after activation are processed; existing PRs are not imported and later status changes are not synchronized. RAW input keeps titles beginning with an equals sign as text. PR bodies, code, comments and attachments are not copied. Select a worksheet with appropriate access for repository details. Manual reruns can create duplicate rows.

  1. 1. GitHub · Pull Request
  2. 2. Google Sheets · Append pull request to the register
View template →Use template

GitHub · Google Sheets

Log new GitHub issues in Google Sheets

Keep an issue register in Google Sheets whenever a new GitHub issue is opened. Append Values writes Issue number, Title, Repository, Author, Issue URL and Created at (UTC) into columns A-F in that order. Connect the FastHook GitHub App and Google Sheets, browse to the repository, then choose a destination spreadsheet and worksheet. The Actions filter is prefilled with opened: edits, comments, closed and reopened issues do not add rows. Headers are optional; an empty worksheet works immediately, or add your own header row. Includes a fictional English example with German characters. Only new events received after activation are processed; existing issues are not imported and later status changes are not synchronized. Values use RAW input, so issue titles starting with an equals sign remain text. Issue bodies, comments and attachments are not copied. Select a worksheet with appropriate access for the repository details.

  1. 1. GitHub · Issues
  2. 2. Google Sheets · Append issue to the register
View template →Use template
GitHubNotionGitHub → Notion3 templatesCreate Notion pages for published GitHub releases · Create Notion review pages for new GitHub pull requests

GitHub · Notion

Create Notion pages for published GitHub releases

Keep a release journal in Notion: create a child page when a GitHub release is published. Each page includes the release tag and optional title, repository, author, publication time, pre-release flag, clickable GitHub link, and Review notes and Follow-up sections. Connect the FastHook GitHub App and Notion, browse to the repository to track, then choose an accessible parent Notion page. The Actions filter is prefilled with published. Both stable releases and published pre-releases are included. Draft releases, edits and deleted releases do not create pages. Includes an independent fictional English release example. Release notes, assets and source code are not copied. Only new publication events after activation are processed; existing releases are not imported. This creates child pages, not database rows or deployment verification, and does not synchronize later changes. Page details become visible to people with access to the selected parent. Manual workflow reruns or unpublishing and republishing a release can create duplicates.

  1. 1. GitHub · Release
  2. 2. Notion · Create a release journal page
View template →Use template

GitHub · Notion

Create Notion review pages for new GitHub pull requests

Create a Notion review page when a GitHub pull request is opened. Each child page includes the PR title and number, repository, author, source and target branches, a clickable GitHub link, and Review notes and Follow-up sections. Connect the FastHook GitHub App and Notion, browse to the repository to track, then choose an accessible parent Notion page. The Actions filter is prefilled with opened. Draft PRs are included. Edits, new commits, reviews, closed and reopened PRs do not create another page. Includes an independent fictional English example with German characters. Only new webhook events received after activation are processed; existing PRs are not imported. This is one-way child page creation, not database rows, reviewer assignment or status synchronization. PR bodies, code changes, comments and attachments are not copied. Page details become visible to people with access to the selected Notion parent. Manual workflow reruns can create duplicates.

  1. 1. GitHub · Pull Request
  2. 2. Notion · Create a Notion pull request review page
View template →Use template

GitHub · Notion

Create Notion triage pages for new GitHub issues

Create a Notion triage page when a new GitHub issue is opened. Each child page includes the issue title, repository, author and source link, plus Triage and Notes sections for your team. Connect the FastHook GitHub App and Notion, select a repository, then browse to an accessible parent Notion page. The Actions filter is prefilled with opened, so edits, comments, closed and reopened issues do not create pages. Includes a fictional English example with German characters. Only new events received after activation are processed; existing issues are not imported. This is one-way page creation, not status synchronization. Issue bodies, comments and attachments are not copied. Titles and repository details become visible to everyone with access to the selected Notion parent. This creates child pages, not database rows.

  1. 1. GitHub · Issues
  2. 2. Notion · Create a Notion issue triage page
View template →Use template
GitHubTrelloGitHub → Trello3 templatesCreate Trello follow-up cards for published GitHub releases · Create Trello review cards from new GitHub pull requests

GitHub · Trello

Create Trello follow-up cards for published GitHub releases

Turn published GitHub releases into Trello cards for release checks and follow-up tasks. Connect the FastHook GitHub App and Trello, browse to the repository to track, then select a destination board and list. Each card includes the release tag, optional title, repository, author, pre-release flag, publication time and GitHub 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 create cards. Includes an independent fictional English release example. Release notes, assets and source code are not copied. Only new publication events after activation are processed; existing releases are not imported. This creates a tracking card; it does not deploy code, verify deployment or synchronize later changes. Card details become visible to members of the destination board. Manual workflow reruns or unpublishing and republishing a release can create duplicate cards.

  1. 1. GitHub · Release
  2. 2. Trello · Create release follow-up card
View template →Use template

GitHub · Trello

Create Trello review cards from new GitHub pull requests

Turn newly opened GitHub pull requests into Trello cards for your review queue. Each card includes the PR title, number, repository, author, source and target branches, draft flag, creation time and GitHub link. Connect the FastHook GitHub App and Trello, browse to the repository to track, then choose a destination board and list. The Actions filter is prefilled with opened. Draft pull requests are included, with their draft flag shown in the description. Edits, new commits, reviews, closed and reopened PRs do not create another card. Includes an independent fictional English review example. Only new webhook events after activation are processed; existing PRs are not imported. This is one-way card creation, not review assignment or status synchronization. PR bodies, code changes and attachments are not copied. Card details become visible to members of the destination board. Manual workflow reruns can create duplicate cards.

  1. 1. GitHub · Pull Request
  2. 2. Trello · Create pull request review card
View template →Use template

GitHub · Trello

Create Trello cards from new GitHub issues

Turn newly opened GitHub issues into Trello cards for your triage queue. Each card includes the issue title, number, repository, author and a link back to GitHub. Connect the FastHook GitHub App and Trello, select the repository you want to track, then choose a destination board and list. The Actions filter is prefilled with opened: edits, comments, closed and reopened issues do not create cards. Includes a fictional English issue example. Only new webhook events received after activation are processed; existing issues are not imported. This is one-way card creation, not status synchronization. Issue bodies and attachments are not copied. Issue titles and repository details become visible to members of the destination board.

  1. 1. GitHub · Issues
  2. 2. Trello · Create issue triage card
View template →Use template
GitHubTelegram BotGitHub → Telegram Bot3 templatesSend Telegram alerts for published GitHub releases · Send Telegram alerts for new GitHub pull requests

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. 1. GitHub · Release
  2. 2. Telegram Bot · Notify the team about a published release
View template →Use template

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. 1. GitHub · Pull Request
  2. 2. Telegram Bot · Notify the Telegram pull request chat
View template →Use template

GitHub · 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. 1. GitHub · Issues
  2. 2. Telegram Bot · Notify the Telegram issue chat
View template →Use template
GitHubSlackGitHub → Slack3 templatesSend Slack alerts for published GitHub releases · Send new GitHub pull requests to Slack
Explore GitHub → Slack integrations →

GitHub · 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. 1. GitHub · Release
  2. 2. Slack · Notify the team about a published release
View template →Use template

GitHub · 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. 1. GitHub · Pull Request
  2. 2. Slack · Notify the team about a new pull request
View template →Use template

GitHub · 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. 1. GitHub · Issues
  2. 2. Slack · Notify the issue channel
View template →Use template
StripeSlackStripe → Slack7 templatesSend Slack alerts for paid Stripe invoices · Send Slack alerts for canceled Stripe subscriptions
Explore Stripe → Slack integrations →

Stripe · 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. 1. Stripe · Invoice Paid
  2. 2. Slack · Notify the team about a paid invoice
View template →Use template

Stripe · 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. 1. Stripe · Customer Subscription Deleted
  2. 2. Slack · Notify the team about an ended subscription
View template →Use template

Stripe · 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. 1. Stripe · Customer Subscription Created
  2. 2. Slack · Notify the team about a new subscription
View template →Use template

Stripe · 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. 1. Stripe · Refund Created
  2. 2. Slack · Notify the team about a new refund
View template →Use template

Stripe · 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. 1. Stripe · Payment Intent Payment Failed
  2. 2. Slack · Notify the team about a failed payment
View template →Use template

Stripe · 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. 1. Stripe · Payment Intent Succeeded
  2. 2. Slack · Notify the payment alerts channel
View template →Use template

Stripe · 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. 1. Stripe · Customer Created
  2. 2. Slack · Notify the customer onboarding channel
View template →Use template
StripeGoogle DriveStripe → Google Drive1 templateCreate Google Drive folders for new Stripe customers

Stripe · Google Drive

Create Google Drive folders for new Stripe customers

Prepare a document folder when a new customer is created in Stripe. Connect Stripe and Google Drive, optionally choose a writable parent folder, then publish. Without a parent, folders are created in My Drive. The folder name includes the Stripe Customer ID and customer name; the ID remains even when the name is blank. Includes its own fictional sandbox customer with German characters. Only customer.created events received after activation are processed. Creating a customer does not confirm payment or a subscription. Existing customers and later edits are not imported or synchronized. This creates an empty folder; it does not copy invoices, payment details, email addresses, tax IDs or metadata, or attach the folder to Stripe. Folder access follows its destination; sharing permissions are not changed. Test with a fictional sandbox customer first. Manually rerunning an event can create another folder with the same name.

  1. 1. Stripe · Customer Created
  2. 2. Google Drive · Create customer document folder
View template →Use template
HubSpotGoogle DriveHubSpot → Google Drive1 templateCreate Google Drive folders for new HubSpot contacts

HubSpot · Google Drive

Create Google Drive folders for new HubSpot contacts

Prepare an empty document folder whenever a new contact is created in HubSpot. Connect HubSpot and Google Drive, optionally browse to a writable parent folder, then publish. Without a parent folder, the folder is created in My Drive. Names follow HubSpot {portal ID} - Contact {contact ID}, so contacts from different accounts remain distinguishable. HubSpot creation webhooks provide IDs, not contact names or email addresses. Includes its own fictional contact-created example. Only contact.creation events received after activation are processed; existing contacts and later edits, merges or deletions are not synchronized. This creates folders only: it does not copy documents, attach the folder to the CRM record, invite the contact or change sharing permissions. Access follows the destination folder. Test with one fictional contact first. Manually rerunning an event can create another folder with the same name.

  1. 1. HubSpot · Contact Creation
  2. 2. Google Drive · Create contact document folder
View template →Use template
HubSpotGoogle SheetsHubSpot → Google Sheets1 templateLog new HubSpot contacts in Google Sheets
Explore HubSpot → Google Sheets integrations →

HubSpot · Google Sheets

Log new HubSpot contacts in Google Sheets

Log each new HubSpot contact in a Google Sheets worksheet. Connect HubSpot and Google Sheets, then browse to your spreadsheet and worksheet. Append Values writes five columns in this order: A Contact ID, B HubSpot record URL, C Event time (Unix milliseconds), D Event ID, E Portal ID. An empty worksheet works; optional headers can be added in row 1 before activation. Values are written as RAW data and new rows are inserted after the existing table. Only contact.creation events received after activation are processed. Existing contacts and later edits, merges or deletions are not synchronized. HubSpot creation webhooks contain record IDs, not names or email addresses, so contact profile fields are not included. The CRM link requires existing HubSpot access. Includes its own fictional event sample. Test with one fictional contact first.

  1. 1. HubSpot · Contact Creation
  2. 2. Google Sheets · Log the new HubSpot contact
View template →Use template
HubSpotTelegram BotHubSpot → Telegram Bot1 templateSend Telegram alerts for new HubSpot contacts

HubSpot · 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. 1. HubSpot · Contact Creation
  2. 2. Telegram Bot · Notify the CRM alerts chat
View template →Use template
HubSpotNotionHubSpot → Notion1 templateCreate Notion follow-up pages for new HubSpot contacts

HubSpot · Notion

Create Notion follow-up pages for new HubSpot contacts

Create a Notion follow-up page when a new contact is created in HubSpot. Connect HubSpot and Notion, then browse to an accessible parent page. Each child page includes the contact ID, a direct link to its HubSpot record and editable Overview, Notes and Follow-up sections. Uses the visual page content editor. Only contact.creation events received after activation are processed; existing contacts, later edits, merges and deletions are not imported or synchronized. Creation webhooks provide record IDs, not the full contact profile, so names and email addresses are not copied. Opening the CRM link requires existing HubSpot access. Includes its own fictional contact-created example. Access follows the selected Notion parent; choose one appropriate for CRM notes. This creates child pages, not database rows, and does not contact the person or change CRM permissions. Test with a fictional contact first.

  1. 1. HubSpot · Contact Creation
  2. 2. Notion · Create a CRM follow-up page
View template →Use template
HubSpotTrelloHubSpot → Trello1 templateCreate Trello follow-up cards for new HubSpot contacts

HubSpot · Trello

Create Trello follow-up cards for new HubSpot contacts

Create a Trello follow-up card whenever a new contact is created in HubSpot. Connect HubSpot and Trello, then browse to a board and list. Each card contains the contact ID, a direct HubSpot record link and an editable follow-up plan. Only contact.creation events received after activation create cards; existing contacts, later edits, merges and deletions are not imported or synchronized. HubSpot creation webhooks provide record IDs, not contact names or email addresses, so these profile fields are not copied. Opening the record link requires existing HubSpot access. Includes its own fictional contact-created example. Choose a board appropriate for CRM follow-up and test with one fictional contact first. This workflow does not contact the person, assign an owner automatically, or change CRM permissions.

  1. 1. HubSpot · Contact Creation
  2. 2. Trello · Create a CRM follow-up card
View template →Use template
HubSpotSlackHubSpot → Slack1 templateSend Slack alerts for new HubSpot contacts
Explore HubSpot → Slack integrations →

HubSpot · 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. 1. HubSpot · Contact Creation
  2. 2. Slack · Notify the CRM contacts channel
View template →Use template
StripeTelegram BotStripe → Telegram Bot1 templateSend Telegram alerts for new Stripe customers

Stripe · 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. 1. Stripe · Customer Created
  2. 2. Telegram Bot · Notify the customer alerts chat
View template →Use template
StripeHubSpotStripe → HubSpot1 templateCreate HubSpot contacts for new Stripe customers

Stripe · HubSpot

Create HubSpot contacts for new Stripe customers

Create one HubSpot contact from the email address on each new Stripe customer. Connect Stripe and HubSpot, then activate the workflow. Customers without an email address are skipped. Use a valid unique email; invalid or existing emails may fail, and this template does not upsert or update contacts. The customer.created event is the only trigger. Creating a customer does not confirm a payment or subscription. No marketing subscriptions are configured. Historical customers are not imported and later customer updates are not synchronized. Includes a fictional English sandbox example for Lina Müller using a valid example.com address. Only email is copied; names, phone numbers, addresses, metadata and payment details are not transferred. Test with a fictional Stripe sandbox customer first.

  1. 1. Stripe · Customer Created
  2. 2. HubSpot · Create CRM contact
View template →Use template
GmailNotionGmail → Notion1 templateCreate Notion notes for matching Gmail emails

Gmail · Notion

Create Notion notes for matching Gmail emails

Capture important emails as Notion notes. New inbox messages matching the prefilled Gmail search subject:"[Notes]" create a child page with the subject, a clickable Gmail conversation link and Summary, Notes and Follow-up sections. Connect Gmail and Notion, review the search query, then browse to an accessible parent Notion page. Includes its own fictional English project email with German characters. Only newly received matching inbox messages are processed; historical messages and later label changes are not imported. Each matching message creates a page, including replies that still match the search. This is one-way note creation, not email synchronization or a database-row import. Email bodies, sender addresses and attachments are not copied. The Gmail link requires access to the connected mailbox; select that account if you use several Google accounts. Page access follows the selected Notion parent. The template does not reply, forward, label or delete emails.

  1. 1. Gmail · New Email Matching Search
  2. 2. Notion · Create email notes page
View template →Use template
Google SheetsNotionGoogle Sheets → Notion1 templateCreate Notion project pages from new Google Sheets rows

Google Sheets · Notion

Create Notion project pages from new Google Sheets rows

Turn a spreadsheet project intake list into Notion project pages. Put Project in row 1 and append one complete project name per row. Each child page uses that name and includes a clickable source spreadsheet link plus Overview, Tasks and Notes sections. Connect Google Sheets and Notion, browse to the spreadsheet and worksheet, then choose an accessible parent Notion page. Activate and allow the first poll to establish a baseline before adding rows. Only newly appended rows are processed; existing rows and later edits are not imported or synchronized. Keep the Project header unchanged and do not delete or reorder rows while active. A non-empty Project value is required. Separate rows create separate pages even when project names match. Includes its own fictional English project example with German characters. Only the project name and source link are copied, not other columns or attachments. This creates child pages rather than database rows and does not write page links back to the sheet. Page access follows the selected Notion parent.

  1. 1. Google Sheets · New Row Added
  2. 2. Notion · Create project brief
View template →Use template
Google DriveNotionGoogle Drive → Notion1 templateCreate Notion review pages for new Google Drive files

Google Drive · Notion

Create Notion review pages for new Google Drive files

Build a document review library in Notion whenever a new file is created in Google Drive. Each child page includes the file name, a clickable Drive link and Review, Notes and Action items sections. Connect Google Drive and Notion, browse to the folder to watch, then select an accessible parent Notion page. Leaving the folder empty watches the connected Drive. Only direct children of the selected folder are monitored; subfolders are not scanned. Detection uses creation time: moving an older file into the folder is not guaranteed to create a page. Polling may include files created roughly one minute before setup; older files, later edits and deletions are not synchronized. Includes its own fictional English document example with German characters. File contents, descriptions and permissions are not copied or changed. The Drive link still requires existing file access. Page access follows the selected Notion parent. This creates child pages, not database rows.

  1. 1. Google Drive · New Files
  2. 2. Notion · Create document review page
View template →Use template
Google CalendarNotionGoogle Calendar → Notion1 templateCreate Notion meeting notes for new Google Calendar events

Google Calendar · Notion

Create Notion meeting notes for new Google Calendar events

Prepare a Notion meeting-notes page whenever a new Google Calendar event is created. Each child page includes the event title, a clickable calendar link and Agenda, Notes and Action items sections. Connect Google Calendar and Notion, choose a calendar, then browse to an accessible parent Notion page. The primary calendar is preselected. Activate and let the first poll establish a baseline before creating events. Only events created afterwards are processed; existing events, later edits and cancellations are not synchronized. Timed and all-day events are supported. Use the calendar link for the current time and schedule; no potentially stale time is copied into the page. Includes a fictional English workshop example with German characters. Event descriptions, attendee lists, locations and attachments are not copied. Page access follows the selected Notion parent. This creates child pages, not database rows.

  1. 1. Google Calendar · New Event
  2. 2. Notion · Create a meeting-notes page
View template →Use template
TrelloNotionTrello → Notion1 templateCreate Notion project pages for new Trello cards

Trello · Notion

Create Notion project pages for new Trello cards

Start a project brief in Notion whenever a new card is created on your Trello board. The new page uses the card title and includes Overview, Tasks and Notes headings ready for your team to fill in. Connect Trello and Notion, select a board, and browse to the parent Notion page that the integration can access. Publish and wait for the Trello webhook to connect before creating a card; registration can take up to 15 minutes. Includes a fictional English project example with German characters. Only new card creation after activation is processed; existing cards, copies, moves and later edits are not synchronized. Card descriptions, comments and attachments are not copied. Each distinct new card creates a separate page, even when titles match. Page access follows the selected parent in Notion. This creates child pages, not database rows.

  1. 1. Trello · Create Card
  2. 2. Notion · Create a Notion project brief
View template →Use template
Google SheetsTelegram BotGoogle Sheets → Telegram Bot2 templatesSend Telegram notifications for new Google Sheets rows · Turn Google Sheets leads into Trello cards and Telegram alerts

Google 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. 1. Google Sheets · New Row Added
  2. 2. Telegram Bot · Notify the Telegram requests chat
View template →Use template

Google 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. 1. Google Sheets · New Row Added
  2. 2. Trello · Create lead card
  3. 3. Telegram Bot · Send lead notification
View template →Use template
GmailSlackGmail → Slack1 templateSend Slack alerts for matching Gmail emails
Explore Gmail → Slack integrations →

Gmail · 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. 1. Gmail · New Email Matching Search
  2. 2. Slack · Notify the email alerts channel
View template →Use template
Google DriveSlackGoogle Drive → Slack1 templateSend Slack notifications for new Google Drive files
Explore Google Drive → Slack integrations →

Google 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. 1. Google Drive · New Files
  2. 2. Slack · Announce the new Drive file
View template →Use template
Google SheetsSlackGoogle Sheets → Slack1 templateSend Slack notifications for new Google Sheets rows
Explore Google Sheets → Slack integrations →

Google 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. 1. Google Sheets · New Row Added
  2. 2. Slack · Notify the requests channel
View template →Use template
TrelloSlackTrello → Slack1 templateSend new Trello cards to a Slack channel
Explore Trello → Slack integrations →

Trello · 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. 1. Trello · Create Card
  2. 2. Slack · Notify the project channel
View template →Use template
Google SheetsHubSpotGoogle Sheets → HubSpot1 templateCreate HubSpot contacts from new Google Sheets rows
Explore Google Sheets → HubSpot integrations →

Google Sheets · HubSpot

Create HubSpot contacts from new Google Sheets rows

Turn new spreadsheet leads into HubSpot contacts. Use Email, FirstName, LastName and Company headers in row 1, then append one complete contact per row. Connect Google Sheets and HubSpot, select the spreadsheet and worksheet, and keep the prepared property mappings. Use a valid, unique email for each new contact. This template creates contacts; it does not update existing contacts or merge duplicate emails. HubSpot may reject a contact whose email already exists. Activate and let the first poll establish a baseline before appending rows. Existing rows and later edits are not imported; avoid deleting or reordering rows while active. Includes a fictional English example with German characters. No marketing subscription or email campaign is configured by this template. Contact data is copied to the connected HubSpot account.

  1. 1. Google Sheets · New Row Added
  2. 2. HubSpot · Create CRM contact
View template →Use template
Google SheetsGoogle CalendarGoogle Sheets → Google Calendar1 templateCreate Google Calendar events from new Google Sheets rows
Explore Google Sheets → Google Calendar integrations →

Google Sheets · Google Calendar

Create Google Calendar events from new Google Sheets rows

Turn a spreadsheet schedule into Google Calendar events. Add Title, Start and End headers in row 1, then append one complete event per row. Start and End must be RFC 3339 timestamps with a time-zone offset, for example 2026-09-22T10:00:00+02:00 and 2026-09-22T11:00:00+02:00. End must be later than Start. Connect Google Sheets and Google Calendar with permission to create events, select the spreadsheet and worksheet, and choose a writable destination calendar. Includes its own fictional English planning example. Activate and let the first poll establish a baseline before adding rows. Existing rows and later edits are not imported; do not delete or reorder rows while active. Each new row creates a separate event. This is one-way event creation, not calendar synchronization or a conflict checker. It does not add attendees, send invitations or write event IDs back to the sheet. Calendar visibility and default reminders follow the destination calendar.

  1. 1. Google Sheets · New Row Added
  2. 2. Google Calendar · Create scheduled event
View template →Use template
GmailTelegram BotGmail → Telegram Bot2 templatesSend Telegram alerts for matching Gmail emails · Gmail attachments to Drive and Telegram
Explore Gmail → Telegram Bot integrations →

Gmail · 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. 1. Gmail · New Email Matching Search
  2. 2. Telegram Bot · Send priority email alert
View template →Use template

Gmail · 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. 1. Gmail · New Attachment Received
  2. 2. Google Drive · Create sender/date folder
  3. 3. Google Drive · Upload attachment
  4. 4. Google Drive · Make attachment public
  5. 5. Telegram Bot · Send public link to Telegram
View template →Use template
Google DriveGoogle SheetsGoogle Drive → Google Sheets1 templateLog new Google Drive files in Google Sheets

Google Drive · Google Sheets

Log new Google Drive files in Google Sheets

Keep a searchable file register in Google Sheets when new files are created in Google Drive. Each file adds one row with File ID, File name, MIME type, Created and Drive URL. Uses Append Values to write these five values in columns A-E in that order. Column headers are optional: an empty worksheet works immediately, or you can add your own header row. Connect Google Drive and Google Sheets, choose a folder to watch, and select the destination spreadsheet and worksheet. Leaving the folder empty watches the connected Drive. Includes its own fictional English file example. Values are written as plain text; file contents and permissions are never copied or changed. A Drive link still requires existing access. Folder monitoring covers direct children only and uses creation time: moving an older file into the folder may not trigger a row. Polling can include files from roughly the minute before setup; older files, later edits and deletions are not synchronized. Use a private worksheet for the file metadata. This is an append-only register, not a live inventory mirror.

  1. 1. Google Drive · New Files
  2. 2. Google Sheets · Append Values
View template →Use template
GmailGoogle SheetsGmail → Google Sheets2 templatesLog matching Gmail emails in Google Sheets · Import Gmail CSV attachments into Google Sheets
Explore Gmail → Google Sheets integrations →

Gmail · Google Sheets

Log matching Gmail emails in Google Sheets

Build a searchable correspondence register from new inbox emails matching your Gmail search. Each matching email adds one row with Message ID, Sender, Subject, Received and Gmail URL. Prepare these exact headers in columns A-E, connect Gmail and Google Sheets, select the spreadsheet and worksheet, and review the prefilled search subject:"[Log]" before activating. Includes its own fictional English enquiry example. Values are written as plain text, preserving punctuation and preventing spreadsheet formula interpretation. Only newly received matching inbox messages are processed; historical messages and later label changes are not imported. Email bodies and attachments are not copied. This is an append-only register, not a two-way sync. Use a private worksheet because sender and subject information is copied there.

  1. 1. Gmail · New Email Matching Search
  2. 2. Google Sheets · Log matching email
View template →Use template

Gmail · Google Sheets

Import Gmail CSV attachments into Google Sheets

Import every row from a Gmail CSV attachment into Google Sheets. Formatter parses the file and maps id, name, email, amount and note to columns A–E. Choose your spreadsheet and worksheet with these headers, or adjust the mappings for your CSV. Includes a three-row CSV example. Only activate after checking the Gmail filter and destination.

  1. 1. Gmail · New Attachment Received
  2. 2. Formatter · Import CSV attachment
  3. 3. Google Sheets · Create Multiple Spreadsheet Rows
View template →Use template
TrelloGoogle DriveTrello → Google Drive1 templateCreate Google Drive project folders for new Trello cards

Trello · Google Drive

Create Google Drive project folders for new Trello cards

Prepare a project workspace in Google Drive whenever a new card is created on your Trello board. The folder takes the card name and is created inside the parent folder you choose. Connect Trello and Google Drive, select a board and optionally a writable destination folder, then publish. With no parent folder selected, folders are created in My Drive. Includes its own fictional English project example. Wait for the Trello trigger to show Connected before creating a card; initial webhook registration can take up to 15 minutes. Only new card creation after activation is processed. Existing cards, copies and later renames are not synchronized. Each distinct card creates a separate folder, even when card names match. This template creates an empty folder and does not copy files, add card attachments or change sharing permissions. Folder access follows its destination in Drive.

  1. 1. Trello · Create Card
  2. 2. Google Drive · Create project folder
View template →Use template
Google DriveTrelloGoogle Drive → Trello1 templateCreate Trello review cards for new Google Drive files

Google Drive · Trello

Create Trello review cards for new Google Drive files

Build a document review queue in Trello when new files are created in Google Drive. Each card uses the file name and includes a direct Drive link plus review instructions. Connect Google Drive and Trello, choose the folder to watch, then select a board and list. Leaving the folder empty watches the connected Drive. Includes a separate fictional English design-brief example. Only direct children of the selected folder are watched. Detection uses creation time: moving older files into the folder is not guaranteed to create a card. Polling can include files from roughly the minute before setup; older files and later edits are not synchronized. Cards have no automatic assignee or due date. The Drive link does not grant access; reviewers need existing file permissions.

  1. 1. Google Drive · New Files
  2. 2. Trello · Create document review card
View template →Use template
Google DriveTelegram BotGoogle Drive → Telegram Bot1 templateSend Telegram alerts for new Google Drive files

Google 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. 1. Google Drive · New Files
  2. 2. Telegram Bot · Announce new Drive file
View template →Use template
Google CalendarTrelloGoogle Calendar → Trello1 templateCreate Trello preparation cards for new Google Calendar events
Explore Google Calendar → Trello integrations →

Google Calendar · Trello

Create Trello preparation cards for new Google Calendar events

Turn newly scheduled Google Calendar events into Trello preparation cards. Each card contains the event title and a direct link to its current schedule and details. Connect Google Calendar and Trello, choose a calendar, then select the destination board and list. The primary calendar is preselected. Includes its own English workshop example and supports timed and all-day events. The first poll establishes a baseline; only events created afterwards are processed. Existing events and later edits are not synchronized. Cards have no automatic due date, attendees or assignees. Use the event link for the authoritative meeting time.

  1. 1. Google Calendar · New Event
  2. 2. Trello · Create meeting preparation card
View template →Use template
TrelloGoogle SheetsTrello → Google Sheets1 templateLog new Trello cards in Google Sheets
Explore Trello → Google Sheets integrations →

Trello · Google Sheets

Log new Trello cards in Google Sheets

Keep a searchable spreadsheet log of new Trello cards. Each new card adds one row with Card ID, Card name, Board, List, Created at and Card URL. Connect Trello and Google Sheets, choose a board, and select a worksheet with these six headers in columns A-F. Mappings are already prepared; adjust them if your headers differ. Values are written as plain text. Includes its own English example card. Tracks new card creation after activation, not existing cards, copied cards or later updates. Initial webhook registration can take up to 15 minutes. Confirm the trigger is connected before creating your first card.

  1. 1. Trello · Create Card
  2. 2. Google Sheets · Log new card
View template →Use template
Google CalendarTelegram BotGoogle Calendar → Telegram Bot1 templateSend Telegram alerts for new Google Calendar events

Google 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. 1. Google Calendar · New Event
  2. 2. Telegram Bot · Announce new calendar event
View template →Use template
TrelloTelegram BotTrello → Telegram Bot1 templateSend Telegram alerts for new Trello cards

Trello · 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. 1. Trello · Create Card
  2. 2. Telegram Bot · Notify about new card
View template →Use template
GmailTrelloGmail → Trello1 templateCreate Trello tasks from matching Gmail emails
Explore Gmail → Trello integrations →

Gmail · Trello

Create Trello tasks from matching Gmail emails

Turn new inbox emails matching your Gmail search into Trello tasks. The email subject becomes the card title; sender, date, message body and a Gmail link are included in its description. Connect Gmail and Trello, review the prefilled Gmail search subject:"[Task]", then choose a Trello board and list. Includes an English example request. Processes newly received matching inbox messages, not historical mail or later label changes. Email content is copied to the selected board: use a private test list first.

  1. 1. Gmail · New Email Matching Search
  2. 2. Trello · Create email task
View template →Use template
Google SheetsTrelloGoogle Sheets → Trello1 templateTurn Google Sheets leads into Trello cards and Telegram alerts
Explore Google Sheets → Trello integrations →

Google 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. 1. Google Sheets · New Row Added
  2. 2. Trello · Create lead card
  3. 3. Telegram Bot · Send lead notification
View template →Use template
GmailGoogle DriveGmail → Google Drive2 templatesSave Gmail attachments to Google Drive · Gmail attachments to Drive and Telegram
Explore Gmail → Google Drive integrations →

Gmail · Google Drive

Save Gmail attachments to Google Drive

Save each new Gmail attachment in Google Drive, organized by sender and received date, then make the uploaded file readable by anyone with its link. Connect Gmail and Google Drive, review sharing settings, and activate the workflow.

  1. 1. Gmail · New Attachment Received
  2. 2. Google Drive · Create sender/date folder
  3. 3. Google Drive · Upload attachment
  4. 4. Google Drive · Share uploaded file
View template →Use template

Gmail · 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. 1. Gmail · New Attachment Received
  2. 2. Google Drive · Create sender/date folder
  3. 3. Google Drive · Upload attachment
  4. 4. Google Drive · Make attachment public
  5. 5. Telegram Bot · Send public link to Telegram
View template →Use template