How to Broadcast Gmail Project Updates to Slack with Pipedream

pipedream.com > Workflows > New Workflow

Create a new Pipedream Workflow

Log into pipedream.com and click 'New Workflow' in the top-right corner. Give the workflow a clear name — 'Gmail → Slack Project Broadcaster' works well. You'll land on the workflow canvas with an empty trigger slot at the top. Pipedream workflows run top-to-bottom: trigger fires, then each step executes in order.

1. 1Go to pipedream.com and sign in
2. 2Click the blue 'New Workflow' button in the top-right
3. 3Type 'Gmail → Slack Project Broadcaster' in the workflow name field
4. 4Press Enter to confirm the name

Workflow Canvas > Add Trigger > Gmail > New Email

Add Gmail as the trigger source

Click the grey 'Add Trigger' block. Search for 'Gmail' in the app search bar and select it. Choose the 'New Email' trigger — this fires every time a new email arrives that matches your filter criteria. Pipedream uses Gmail's push notification API (not polling), so the trigger fires within 5–15 seconds of email delivery.

1. 1Click the grey 'Add Trigger' block on the canvas
2. 2Type 'Gmail' in the search bar
3. 3Select 'Gmail' from the results
4. 4Choose 'New Email' from the trigger list

Gmail Trigger > Connected Account > Connect Account

Connect your Gmail account

In the trigger configuration panel, click 'Connect Account' under the Connected Account field. A Google OAuth window will open — sign in with the Gmail account that receives project-related emails. Grant Pipedream the requested Gmail scopes. After connecting, the account email address appears in the dropdown and the field shows a green checkmark.

1. 1Click 'Connect Account' in the Gmail trigger panel
2. 2Select your Google account in the OAuth popup
3. 3Click 'Allow' to grant Gmail read access
4. 4Confirm the connected account appears in the dropdown

Gmail Trigger > Label > [your label name]

Filter emails by Gmail label

In the trigger's Label field, type the name of the Gmail label you use for project emails — for example, 'Project-Alpha'. If you manage multiple projects, you'll build separate workflows per label, or use a label prefix like 'Project-' and handle routing in a code step. Leave the Search Query field blank unless you need additional filtering (e.g., specific senders). Click 'Save and continue'.

1. 1Click into the 'Label' field in the trigger config
2. 2Type your exact Gmail label name (case-sensitive)
3. 3Leave the Search Query field blank unless you need sender filtering
4. 4Click 'Save and continue'

Gmail Trigger > Generate Test Event

Load a test email event

Click 'Generate Test Event' to pull a recent email from Gmail matching your label. Pipedream fetches the last matching message and displays its raw payload in the event inspector on the right side of the canvas. Expand the payload to confirm you can see fields like `subject`, `from`, `snippet`, `body`, and `labelIds`. You'll reference these field paths in later steps.

1. 1Click 'Generate Test Event' in the trigger panel
2. 2Wait 3–5 seconds for Pipedream to fetch from Gmail
3. 3Click the event in the inspector panel to expand the payload
4. 4Verify 'subject', 'from', and 'snippet' fields are visible

Workflow Canvas > + Add Step > Run Node.js code

Add a Node.js code step to build the Slack message

Click '+ Add Step' below the trigger, then select 'Run Node.js code'. This step extracts the relevant email fields and builds a formatted Slack Block Kit message. Using a code step here — rather than a pre-built action — lets you truncate the body snippet, strip HTML characters, and format the sender name cleanly. Paste the code from the Pro Tip section into the code editor.

1. 1Click '+ Add Step' below the Gmail trigger block
2. 2Click 'Run Node.js code' from the step type options
3. 3Clear the default placeholder code in the editor
4. 4Paste the Pro Tip code into the editor

Paste this into the Node.js code step (Step 6) — it extracts the Gmail event fields, strips HTML entities from the snippet, maps the Gmail label to the correct Slack channel, and returns a Block Kit payload ready to pass directly into the Slack 'Send Message' action. The `labelToChannelMap` object is where you add new projects — update it and redeploy without touching anything else.

export default defineComponent({
  async run({ steps, $ }) {
    const email = steps.trigger.event;

export default defineComponent({
  async run({ steps, $ }) {
    const email = steps.trigger.event;

    // Map Gmail labels to Slack channel names
    const labelToChannelMap = {
      'Project-Alpha': '#proj-alpha',
      'Project-Beta': '#proj-beta',
      'Project-Gamma': '#proj-gamma',
    };

    // Find the matching project label from the email's label list
    const projectLabel = email.labelIds?.find(label => labelToChannelMap[label]);
    const channelName = projectLabel ? labelToChannelMap[projectLabel] : '#general-projects';

    // Clean the snippet: strip HTML tags and decode common HTML entities
    const rawSnippet = email.snippet || 'No preview available.';
    const cleanSnippet = rawSnippet
      .replace(/<[^>]+>/g, '')
      .replace(/&nbsp;/g, ' ')
      .replace(/&amp;/g, '&')
      .replace(/&lt;/g, '<')
      .replace(/&gt;/g, '>')
      .replace(/&quot;/g, '"')
      .trim()
      .slice(0, 400);

    // Format sender display name
    const from = email.from || 'Unknown Sender';
    const senderDisplay = from.replace(/<([^>]+)>/, '(<$1>)').trim();

    // Format the received timestamp
    const receivedDate = email.date
      ? new Date(email.date).toLocaleString('en-US', {
          month: 'short', day: 'numeric', year: 'numeric',
          hour: 'numeric', minute: '2-digit', timeZoneName: 'short'
        })
      : 'Unknown time';

    // Build Slack Block Kit message
    const slackBlocks = [
      {
        type: 'header',
        text: { type: 'plain_text', text: '📧 New Project Email', emoji: true }
      },
      {
        type: 'section',
        fields: [
          { type: 'mrkdwn', text: `*From:*\n${senderDisplay}` },
          { type: 'mrkdwn', text: `*Channel:*\n${channelName}` }
        ]
      },
      {
        type: 'section',
        text: { type: 'mrkdwn', text: `*Subject:* ${email.subject || '(no subject)'}` }
      },
      { type: 'divider' },
      {
        type: 'section',
        text: {
          type: 'mrkdwn',
          text: `${cleanSnippet}${rawSnippet.length > 400 ? '…' : ''}`
        }
      },
      {
        type: 'context',
        elements: [
          { type: 'mrkdwn', text: `Received: ${receivedDate} · Message ID: ${email.id}` }
        ]
      }
    ];

    return { channelName, slackBlocks, senderDisplay, receivedDate };
  }
});

Code Step > Test

Test the code step

Click 'Test' on the code step. Pipedream re-runs the step using the test event data loaded from Gmail in Step 5. The return value appears in the inspector panel on the right. Check that `slackBlocks`, `channelName`, and `senderDisplay` all have the expected values. If the snippet is showing HTML tags (e.g., ` `), the code step strips those — confirm the output looks clean.

1. 1Click the 'Test' button inside the code step
2. 2Wait 2–3 seconds for the step to execute
3. 3Expand the 'Return Value' section in the right inspector
4. 4Verify slackBlocks, channelName, and senderDisplay are populated correctly

Paste this into the Node.js code step (Step 6) — it extracts the Gmail event fields, strips HTML entities from the snippet, maps the Gmail label to the correct Slack channel, and returns a Block Kit payload ready to pass directly into the Slack 'Send Message' action. The `labelToChannelMap` object is where you add new projects — update it and redeploy without touching anything else.

export default defineComponent({
  async run({ steps, $ }) {
    const email = steps.trigger.event;

export default defineComponent({
  async run({ steps, $ }) {
    const email = steps.trigger.event;

    // Map Gmail labels to Slack channel names
    const labelToChannelMap = {
      'Project-Alpha': '#proj-alpha',
      'Project-Beta': '#proj-beta',
      'Project-Gamma': '#proj-gamma',
    };

    // Find the matching project label from the email's label list
    const projectLabel = email.labelIds?.find(label => labelToChannelMap[label]);
    const channelName = projectLabel ? labelToChannelMap[projectLabel] : '#general-projects';

    // Clean the snippet: strip HTML tags and decode common HTML entities
    const rawSnippet = email.snippet || 'No preview available.';
    const cleanSnippet = rawSnippet
      .replace(/<[^>]+>/g, '')
      .replace(/&nbsp;/g, ' ')
      .replace(/&amp;/g, '&')
      .replace(/&lt;/g, '<')
      .replace(/&gt;/g, '>')
      .replace(/&quot;/g, '"')
      .trim()
      .slice(0, 400);

    // Format sender display name
    const from = email.from || 'Unknown Sender';
    const senderDisplay = from.replace(/<([^>]+)>/, '(<$1>)').trim();

    // Format the received timestamp
    const receivedDate = email.date
      ? new Date(email.date).toLocaleString('en-US', {
          month: 'short', day: 'numeric', year: 'numeric',
          hour: 'numeric', minute: '2-digit', timeZoneName: 'short'
        })
      : 'Unknown time';

    // Build Slack Block Kit message
    const slackBlocks = [
      {
        type: 'header',
        text: { type: 'plain_text', text: '📧 New Project Email', emoji: true }
      },
      {
        type: 'section',
        fields: [
          { type: 'mrkdwn', text: `*From:*\n${senderDisplay}` },
          { type: 'mrkdwn', text: `*Channel:*\n${channelName}` }
        ]
      },
      {
        type: 'section',
        text: { type: 'mrkdwn', text: `*Subject:* ${email.subject || '(no subject)'}` }
      },
      { type: 'divider' },
      {
        type: 'section',
        text: {
          type: 'mrkdwn',
          text: `${cleanSnippet}${rawSnippet.length > 400 ? '…' : ''}`
        }
      },
      {
        type: 'context',
        elements: [
          { type: 'mrkdwn', text: `Received: ${receivedDate} · Message ID: ${email.id}` }
        ]
      }
    ];

    return { channelName, slackBlocks, senderDisplay, receivedDate };
  }
});

Workflow Canvas > + Add Step > Slack > Send Message

Add the Slack 'Send Message' action

Click '+ Add Step' below the code step and search for 'Slack'. Select the 'Send Message' action. Connect your Slack workspace via the Connected Account dropdown — this opens a Slack OAuth screen where you authorize Pipedream to post messages. In the Channel field, reference the output from your code step: click the '{}' icon and select `steps.build_slack_message.$return_value.channelName`. In the Blocks field, select `steps.build_slack_message.$return_value.slackBlocks`.

1. 1Click '+ Add Step' below the code step
2. 2Search for 'Slack' and select it
3. 3Choose 'Send Message' from the action list
4. 4Click 'Connect Account' and authorize your Slack workspace
5. 5Set Channel to `steps.build_slack_message.$return_value.channelName`
6. 6Set Blocks to `steps.build_slack_message.$return_value.slackBlocks`

Slack Action > Test

Test the Slack action

Click 'Test' on the Slack action step. Pipedream sends the formatted Block Kit message to your Slack channel using the test event data. Switch to Slack and look for the message in the target channel — it should appear within 5 seconds. Verify the sender name, subject, timestamp, and body snippet all display correctly. If the message posts but Block Kit formatting looks broken, check the slackBlocks JSON structure in the inspector.

1. 1Click 'Test' inside the Slack action step
2. 2Open Slack and navigate to your target project channel
3. 3Confirm the message appears with correct formatting
4. 4Check the inspector for any error responses from the Slack API

Workflow Canvas > Deploy

Deploy the workflow

Click the grey 'Deploy' button in the top-right of the workflow canvas. Pipedream registers the Gmail push notification subscription and activates the workflow. The status indicator in the top bar changes from 'Inactive' to 'Active' with a green dot. From this point, every new email with your label triggers the workflow and posts to Slack automatically — no manual intervention needed.

1. 1Click the grey 'Deploy' button in the top-right corner
2. 2Confirm the status indicator turns green and shows 'Active'
3. 3Send a test email to your Gmail with the project label applied
4. 4Verify the Slack message appears within 30 seconds

Workflow > Runs Tab > Settings > Notifications

Monitor runs in the Pipedream inspector

Navigate to your workflow and click the 'Runs' tab to see every execution. Each run shows the Gmail payload that triggered it, the output of your code step, and the Slack API response. If a run fails, the failing step is highlighted in red with the error message. Set up error notifications under Settings > Notifications to get an email when the workflow errors — critical for catching Gmail subscription lapses or Slack token expiry.

1. 1Click the 'Runs' tab at the top of your workflow
2. 2Click any run to expand its step-by-step execution details
3. 3Navigate to Settings > Notifications
4. 4Enable email alerts for workflow errors