Slack logo
Gmail logo

Workflow template

Email marked Slack messages with Gmail

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

From an email-marked Slack message to a reviewer’s inbox

1 Trigger · 1 Action
Slack1 · Trigger

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.

Gmail2 · Action

Email the marked Slack message

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

A plain-text email containing the marked channel update

Example Gmail Slack handoff

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

Set up your workflow

  1. Select the Slack channels and marker

    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.

  2. Connect Gmail and set the fixed recipient

    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.

  3. Post a fictional email request

    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.

Details and limitations
  • 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.

Questions about this template

Does the Slack author choose the email recipient?

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.

Are Slack formatting, attachments and threads converted?

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.

Where does the source link go?

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.

Can the same request be emailed twice?

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.

Explore connected apps