New Keyword Mention
Watch new human messages containing [Email] anywhere without case sensitivity. Matching human thread replies qualify and bots are ignored. Empty Channels watches all channels accessible to the connection.
Workflow template
Email Slack messages containing [Email] to a fixed reviewer through Gmail. Include the full text, author and channel IDs, original timestamp and source-channel link as plain text.
How it works
Watch new human messages containing [Email] anywhere without case sensitivity. Matching human thread replies qualify and bots are ignored. Empty Channels watches all channels accessible to the connection.
Send to your fixed recipient from the connected Gmail account. Use the Slack timestamp in the subject and include the full original message, author/channel IDs, timestamp and channel URL in a plain-text body.
The result
Slack email request 1789664400.000101
A Slack message was marked for email. [Email] Hannover handoff — Grüße: please review the release checklist before the afternoon shift. Author ID: UEXAMPLE101 Channel ID: CEXAMPLE101 Message timestamp: 1789664400.000101 Source channel: https://app.slack.com/client/TEXAMPLE101/CEXAMPLE101
Fictional message. Your configured recipient can read the copied text; the channel link still requires Slack access. The sent email appears in the connected Gmail account’s Sent folder.
Before activation
Connect Slack, use Browse to choose source channels and add FastHook before activation. Retain [Email], ignored bots and case-insensitive matching. Review the broader scope if Channels remains empty.
Select the sending Gmail connection and enter a recipient allowed to receive the copied channel text. Use your own address for the first test. No HTML, Cc or Bcc is configured.
Activate and post a new human Slack message containing [Email]. Compare the subject, complete body and source metadata in the inbox and Gmail Sent. Verify the source-channel link with an account that has Slack access.
Source formatting stays literal. Mentions and Slack formatting remain as source text in a plain-text email. Files, attachments and surrounding thread history are not copied. The URL opens the channel rather than a specific message.
This is notification rather than conversation sync. Only new matching messages and matching human replies qualify. Existing messages, edits, deletions and bots are excluded. The workflow does not reply in Slack or synchronize later conversation changes.
The connected Gmail account sends the notice. Messages appear in Sent and Gmail sending limits apply. Manual reruns or ambiguous provider retries can resend a message. Review Sent if the outcome is uncertain before retrying.
No. You configure a fixed recipient in the Gmail action. The message’s author ID is included as metadata, not used as a recipient address.
No. The full matching message is sent as literal plain text with source metadata. Files, attachments and surrounding thread history are not copied, although a new matching human reply can send its own email.
It opens the source Slack channel rather than an exact-message permalink. The recipient can read the email, but still needs Slack access to open that channel.
Yes. Gmail limits apply and manual reruns or ambiguous provider retries can resend the notice. Check Sent before retrying an uncertain result; later Slack edits do not update an already sent email.