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. Gmail · New Email Matching Search
- 2. Discord · Notify the email channel
View template →Use templateHubSpot · 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. HubSpot · Contact Creation
- 2. Gmail · Email the new HubSpot contact notification
View template →Use templateSlack · Gmail
Email marked Slack messages with Gmail
Send a Gmail email when someone marks a Slack message with [Email]. Use this to pass selected channel updates to reviewers who follow work from their inbox. Connect Slack, select source channels through Browse, connect Gmail and enter a fixed recipient address. The [Email] keyword is prefilled, matched anywhere without case sensitivity, and bot messages are ignored. Each plain-text email contains the complete message, author ID, channel ID, original Slack timestamp and source channel link. Includes its own fictional English Hannover handoff example with German Unicode. Add FastHook to the source channel before activation. Leaving Channels empty watches every channel accessible to the Slack connection; matching human thread replies also send email. Only new matching messages are processed, not historical messages, edits or deletions. Mentions and Slack formatting remain literal source text. Files, attachments and surrounding thread history are not copied. This creates an email notification, not a Slack reply or synchronized conversation. Email recipients can read the copied message; opening the source channel still requires Slack access. Emails are sent from the connected Gmail account and appear in Sent. No HTML, Cc or Bcc is configured. Gmail limits apply and manual reruns or ambiguous provider retries can resend a message. Use your own email address for the first test.
- 1. Slack · New Keyword Mention
- 2. Gmail · Email the marked Slack message
View template →Use templateGitHub · 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. GitHub · Release
- 2. Gmail · Email the release reviewer
View template →Use templateGitHub · 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. GitHub · Pull Request
- 2. Gmail · Email the pull request reviewer
View template →Use templateGoogle 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. Google Drive · New Files
- 2. Gmail · Email the new file notification
View template →Use templateGoogle 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. Google Calendar · New Event
- 2. Gmail · Email the event notification
View template →Use templateGitHub · 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. GitHub · Issues
- 2. Gmail · Email the issue reviewer
View template →Use templateTrello · 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. Trello · Create Card
- 2. Gmail · Email the card reviewer
View template →Use templateGoogle 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. Google Sheets · New Row Added
- 2. Filter · Only send complete message rows
- 3. Gmail · Send the row as a plain-text email
View template →Use templateGmail · 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. Gmail · New Email Matching Search
- 2. Notion · Create email notes page
View template →Use templateGmail · Slack
Send Slack alerts for matching Gmail emails
Stay informed about priority inbox messages without forwarding whole emails. New Gmail messages matching the prefilled search subject:"[Alert]" produce a plain-text Slack alert with the subject, sender, received date and Gmail conversation link. Connect Gmail and Slack, review the search query and choose a channel where the FastHook bot can post. Includes its own fictional English alert. Only newly received matching inbox messages are processed; this is not a historical import, label-change monitor or two-way sync. Email bodies and attachments are not forwarded. The Gmail link requires access to the same mailbox; select that Google account if you use multiple accounts. Subject and sender details are shared with everyone in the selected channel. Each new matching message produces one alert, including replies that still match the search.
- 1. Gmail · New Email Matching Search
- 2. Slack · Notify the email alerts channel
View template →Use templateGmail · Telegram Bot
Send Telegram alerts for matching Gmail emails
Stay informed about priority inbox messages without forwarding whole emails. New Gmail messages matching the prefilled search subject:"[Alert]" produce a plain-text Telegram alert with the subject, sender, received date and Gmail conversation link. Connect Gmail and Telegram, review the search query and choose a private chat where your bot can send messages. Includes its own fictional English alert. Only newly received matching inbox messages are processed; this is not a historical import, label-change monitor or two-way sync. Email bodies and attachments are not forwarded. The Gmail link requires access to the same mailbox; select that Google account if you use multiple accounts. Subject and sender details are shared with everyone in the selected chat. Each new matching message produces one alert, including replies that still match the search.
- 1. Gmail · New Email Matching Search
- 2. Telegram Bot · Send priority email alert
View template →Use templateGmail · 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. Gmail · New Email Matching Search
- 2. Google Sheets · Log matching email
View template →Use templateGmail · 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. Gmail · New Email Matching Search
- 2. Trello · Create email task
View template →Use templateGmail · 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. Gmail · New Attachment Received
- 2. Formatter · Import CSV attachment
- 3. Google Sheets · Create Multiple Spreadsheet Rows
View template →Use templateGmail · 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. Gmail · New Attachment Received
- 2. Google Drive · Create sender/date folder
- 3. Google Drive · Upload attachment
- 4. Google Drive · Share uploaded file
View template →Use templateGmail · Google Drive · Telegram Bot
Gmail attachments to Drive and Telegram
Save every new Gmail attachment in a sender/date folder, make the uploaded file public, and send its link to Telegram.
- 1. Gmail · New Attachment Received
- 2. Google Drive · Create sender/date folder
- 3. Google Drive · Upload attachment
- 4. Google Drive · Make attachment public
- 5. Telegram Bot · Send public link to Telegram
View template →Use template
