How to Route Gmail Support Emails to Slack with Pipedream

pipedream.com > Workflows > New Workflow

Create a new Pipedream Workflow

Go to pipedream.com and sign in. From the left sidebar click 'Workflows', then click the blue 'New Workflow' button in the top right. Give the workflow a name like 'Gmail Support → Slack' so it's easy to find later. You'll land on the workflow canvas with a prompt to choose a trigger.

1. 1Click 'Workflows' in the left sidebar
2. 2Click the blue 'New Workflow' button
3. 3Type a name: 'Gmail Support → Slack'
4. 4Click 'Save' or press Enter to confirm the name

Workflow Canvas > Add Trigger > Gmail > New Email

Add the Gmail New Email trigger

Click the 'Add Trigger' block. In the search bar type 'Gmail' and select the Gmail app. Choose the trigger called 'New Email'. This trigger uses Pipedream's Gmail push integration, which creates a Gmail watch via Google's API — it fires within seconds of a message arriving, not on a polling interval.

1. 1Click the 'Add Trigger' block
2. 2Type 'Gmail' in the search bar
3. 3Click the Gmail app icon
4. 4Select 'New Email' from the trigger list

Trigger Panel > Gmail > Connect Account > Google OAuth

Connect your Gmail support account

In the trigger panel, click 'Connect Account' under the Gmail section. A Google OAuth popup appears — sign in with the Google account that owns your support inbox (e.g. [email protected]), not your personal account. After signing in, grant Pipedream the requested Gmail scopes. Back in the trigger panel, set the 'Label' field to 'INBOX' or a specific Gmail label you've created for support emails.

1. 1Click 'Connect Account' in the Gmail trigger panel
2. 2Select or add the support Google account in the OAuth popup
3. 3Grant all requested permissions and click 'Continue'
4. 4Set the Label dropdown to 'INBOX' or your support-specific label

Trigger Panel > Generate Test Event > Select Event

Test the trigger with a real email

Click 'Generate Test Event' at the bottom of the trigger panel. Pipedream will either fetch the most recent email in the inbox or prompt you to send a test email to the connected address. Send a real test email with a realistic subject line like 'Order #8821 not delivered'. Once Pipedream detects it, click 'Select' next to the event to use it as sample data for the remaining steps.

1. 1Click 'Generate Test Event'
2. 2Send a test email to the connected support address if prompted
3. 3Wait for the event to appear in the list (usually under 30 seconds)
4. 4Click 'Select' next to the test event

Workflow Canvas > + > Run Node.js Code

Add a Node.js code step to parse and format the email

Click the '+' button below the trigger to add a new step. Choose 'Run Node.js code'. This step extracts the sender name, email address, subject, and a truncated body preview from the raw Gmail payload. You'll write the parsing logic here so the Slack message is clean and readable rather than dumping raw JSON into the channel.

1. 1Click the '+' button below the Gmail trigger
2. 2Click 'Run Node.js code' from the step options
3. 3Clear the default code in the editor
4. 4Paste your formatting code (see Pro Tip section below)

Paste this into the Node.js code step (step 5). It handles both plain-text and multipart HTML emails, decodes the Base64url body, truncates the preview to 300 characters, extracts sender name and email separately, formats the received timestamp, and returns a clean object that the Slack Block Kit step consumes directly. Replace the `export default` function contents with this code.

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

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

    // Extract headers
    const getHeader = (name) =>
      headers.find(h => h.name.toLowerCase() === name.toLowerCase())?.value || '';

    const fromRaw = getHeader('From');
    const subject = getHeader('Subject') || '(no subject)';
    const toAddress = getHeader('To');
    const dateRaw = getHeader('Date');

    // Parse sender name and email from 'From' header
    const fromMatch = fromRaw.match(/^(.+?)\s*<(.+?)>$/);
    const senderName = fromMatch ? fromMatch[1].trim().replace(/^"|"$/g, '') : fromRaw;
    const senderEmail = fromMatch ? fromMatch[2] : fromRaw;

    // Recursively find plain text body in potentially nested MIME parts
    function findPlainText(part) {
      if (part.mimeType === 'text/plain' && part.body?.data) {
        return Buffer.from(part.body.data, 'base64url').toString('utf-8');
      }
      if (part.parts) {
        for (const child of part.parts) {
          const result = findPlainText(child);
          if (result) return result;
        }
      }
      return null;
    }

    const rawBody = findPlainText(message.payload) || '';
    const bodyPreview = rawBody.replace(/\s+/g, ' ').trim().slice(0, 300) +
      (rawBody.length > 300 ? '...' : '');

    // Format timestamp
    const receivedAt = message.internalDate
      ? new Date(parseInt(message.internalDate)).toLocaleString('en-US', {
          month: 'short', day: 'numeric', year: 'numeric',
          hour: 'numeric', minute: '2-digit', timeZoneName: 'short'
        })
      : dateRaw;

    // Build Gmail deep link
    const threadId = message.threadId;
    const gmailLink = `https://mail.google.com/mail/u/0/#all/${threadId}`;

    // Deduplication guard using Pipedream data store
    const db = $.service.db;
    const seen = await db.get('seen_message_ids') || [];
    if (seen.includes(message.id)) {
      $.flow.exit('Duplicate message — already processed');
    }
    const updated = [message.id, ...seen].slice(0, 100);
    await db.set('seen_message_ids', updated);

    return {
      senderName,
      senderEmail,
      subject,
      bodyPreview: bodyPreview || '(no body content)',
      receivedAt,
      gmailLink,
      threadId,
      toAddress,
      messageId: message.id
    };
  }
});

Code Step Panel > Test > Return Value

Test the code step output

Click 'Test' in the code step panel. Pipedream runs the function against the sample email you selected in step 4. Check the 'Return Value' tab on the right side of the editor. You should see clean, decoded values for each field. If `bodyPreview` is empty, the email might use `payload.parts` instead of `payload.body` — multipart emails (HTML + plain text) structure their content differently.

1. 1Click the 'Test' button in the code step
2. 2Click the 'Return Value' tab in the right panel
3. 3Confirm `senderName`, `senderEmail`, `subject`, and `bodyPreview` all have readable values
4. 4If any field is empty, check the 'Logs' tab for errors

Paste this into the Node.js code step (step 5). It handles both plain-text and multipart HTML emails, decodes the Base64url body, truncates the preview to 300 characters, extracts sender name and email separately, formats the received timestamp, and returns a clean object that the Slack Block Kit step consumes directly. Replace the `export default` function contents with this code.

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

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

    // Extract headers
    const getHeader = (name) =>
      headers.find(h => h.name.toLowerCase() === name.toLowerCase())?.value || '';

    const fromRaw = getHeader('From');
    const subject = getHeader('Subject') || '(no subject)';
    const toAddress = getHeader('To');
    const dateRaw = getHeader('Date');

    // Parse sender name and email from 'From' header
    const fromMatch = fromRaw.match(/^(.+?)\s*<(.+?)>$/);
    const senderName = fromMatch ? fromMatch[1].trim().replace(/^"|"$/g, '') : fromRaw;
    const senderEmail = fromMatch ? fromMatch[2] : fromRaw;

    // Recursively find plain text body in potentially nested MIME parts
    function findPlainText(part) {
      if (part.mimeType === 'text/plain' && part.body?.data) {
        return Buffer.from(part.body.data, 'base64url').toString('utf-8');
      }
      if (part.parts) {
        for (const child of part.parts) {
          const result = findPlainText(child);
          if (result) return result;
        }
      }
      return null;
    }

    const rawBody = findPlainText(message.payload) || '';
    const bodyPreview = rawBody.replace(/\s+/g, ' ').trim().slice(0, 300) +
      (rawBody.length > 300 ? '...' : '');

    // Format timestamp
    const receivedAt = message.internalDate
      ? new Date(parseInt(message.internalDate)).toLocaleString('en-US', {
          month: 'short', day: 'numeric', year: 'numeric',
          hour: 'numeric', minute: '2-digit', timeZoneName: 'short'
        })
      : dateRaw;

    // Build Gmail deep link
    const threadId = message.threadId;
    const gmailLink = `https://mail.google.com/mail/u/0/#all/${threadId}`;

    // Deduplication guard using Pipedream data store
    const db = $.service.db;
    const seen = await db.get('seen_message_ids') || [];
    if (seen.includes(message.id)) {
      $.flow.exit('Duplicate message — already processed');
    }
    const updated = [message.id, ...seen].slice(0, 100);
    await db.set('seen_message_ids', updated);

    return {
      senderName,
      senderEmail,
      subject,
      bodyPreview: bodyPreview || '(no body content)',
      receivedAt,
      gmailLink,
      threadId,
      toAddress,
      messageId: message.id
    };
  }
});

Workflow Canvas > + > Slack > Send Message to Channel

Add the Slack step to post the message

Click '+' below the code step and search for 'Slack'. Select the Slack app and choose the action 'Send Message to Channel'. Connect your Slack workspace via the Connected Accounts flow. In the 'Channel' field, type or select your support channel name (e.g. #support-queue). Set the 'Message Text' field using the outputs from your code step.

1. 1Click '+' below the code step
2. 2Search for 'Slack' and select the Slack app
3. 3Choose 'Send Message to Channel'
4. 4Click 'Connect Account' and authorize Pipedream in your Slack workspace
5. 5Select your support channel from the Channel dropdown

Slack Step Panel > Blocks field > {} variable picker

Build the Slack message with Block Kit formatting

In the Slack step, use the 'Blocks' field rather than the plain 'Message Text' field. Block Kit lets you format the support ticket summary with bold headers, field rows, and a direct link to Gmail. Reference the outputs from your code step using Pipedream's variable picker — click the `{}` icon next to any field to browse available values from previous steps.

1. 1Click inside the 'Blocks' field in the Slack step
2. 2Click the '{}' variable picker icon
3. 3Select values from your code step: `steps.nodejs.$return_value.senderName`, `subject`, `bodyPreview`
4. 4Paste the Block Kit JSON structure from the Pro Tip section
5. 5Replace hardcoded strings with the variable references

Workflow Canvas > Test Workflow (top toolbar)

Test the full workflow end-to-end

Click 'Test Workflow' at the top of the canvas. Pipedream runs all steps sequentially using the sample event from step 4. Watch the step indicators — each one turns green when it succeeds. Then open your #support-queue Slack channel and confirm the message appeared with correct sender, subject, and body preview. Check that the Gmail link in the message opens the correct thread.

1. 1Click 'Test Workflow' in the top toolbar
2. 2Watch each step turn green in sequence
3. 3Open your Slack workspace and navigate to #support-queue
4. 4Confirm the message shows the correct sender name, email, subject, and preview

Workflow Canvas > Deploy (top right button)

Deploy and enable the workflow

Click the 'Deploy' button in the top right corner of the workflow canvas. Pipedream activates the Gmail push subscription and the workflow goes live. The status indicator next to the workflow name changes from 'Paused' to 'Active'. From this point, every new email arriving in the connected Gmail inbox triggers the workflow in real time — no polling interval, no delay beyond Gmail's own push latency (typically under 10 seconds).

1. 1Click the blue 'Deploy' button in the top right
2. 2Confirm the deployment in the dialog if prompted
3. 3Verify the workflow status shows 'Active' in the left sidebar