How to Route Gmail Support Emails to Slack with Power Automate

make.powerautomate.com > Create > Automated cloud flow

Open Power Automate and create a new Automated cloud flow

Go to make.powerautomate.com and sign in. In the left sidebar click 'Create', then select 'Automated cloud flow' from the three options presented. Give the flow a name like 'Gmail Support to Slack Router'. You will be prompted to choose a trigger immediately — search for 'Gmail' in the search box. This is an Automated flow, meaning it runs every time the trigger condition is met rather than on a schedule.

1. 1Click 'Create' in the left sidebar
2. 2Select 'Automated cloud flow'
3. 3Enter flow name: 'Gmail Support to Slack Router'
4. 4In the trigger search box type 'Gmail'
5. 5Select the Gmail connector from the results

Flow canvas > Trigger: When a new email arrives (V3)

Configure the Gmail trigger for your support inbox

Select the trigger 'When a new email arrives (V3)'. Power Automate will immediately prompt you to sign in to a Gmail account — use the shared support inbox account, not your personal Gmail. Once connected, set the 'Label/Mailbox' field to 'INBOX' and the 'From' field to a filter like '[email protected]' if you only want emails sent to that alias, or leave it blank to catch all inbound. Set 'Include Attachments' to No unless your team needs file visibility in Slack.

1. 1Select 'When a new email arrives (V3)' as the trigger
2. 2Click 'Sign in' and authenticate with the support Gmail account
3. 3Set 'Label/Mailbox' to INBOX
4. 4Set 'To' filter to your support address (e.g. [email protected])
5. 5Set 'Include Attachments' to No

Flow canvas > + New step > Control > Condition

Add a Condition to filter out automated/noreply emails

Click '+ New step', search for 'Condition', and select the 'Condition' Control action. This prevents bot emails, auto-replies, and newsletter subscriptions from flooding your Slack channel. Set the left value to the dynamic content 'From' from the Gmail trigger. Set the condition to 'does not contain' and enter 'noreply' in the right field. Add a second row with 'From does not contain auto-reply' using an 'And' operator. If the condition is true, subsequent steps fire. If false, the flow terminates.

1. 1Click '+ New step'
2. 2Search 'Condition' and select it under Control
3. 3Click the left value box and pick dynamic content 'From'
4. 4Set operator to 'does not contain'
5. 5Type 'noreply' in the right value box
6. 6Click '+ Add' > 'Add row' and repeat with 'auto-reply'

Flow canvas > If yes branch > + Add an action > Data Operation > Compose

Add a Compose action to build the formatted Slack message

Inside the 'If yes' branch, click '+ Add an action', search for 'Compose', and select the 'Data Operation – Compose' action. This is where you assemble the message text before sending to Slack. In the Inputs field, type your message template and insert dynamic content tokens from the Gmail trigger. Use a format your team can scan quickly: the sender name, subject, time received, and a trimmed body preview. You will reference the output of this Compose step in the Slack action next.

1. 1Inside 'If yes', click '+ Add an action'
2. 2Search 'Compose' and select 'Data Operation – Compose'
3. 3Click into the Inputs field
4. 4Type your message template (see field mapping below for exact tokens)
5. 5Insert dynamic content: From, Subject, Received Time, Body Preview

Flow canvas > If yes branch > + Add an action > Data Operation > Compose (Name Parser)

Parse the sender's display name from the From field

The Gmail 'From' field returns a string like 'Jane Doe <[email protected]>'. To show only the display name in Slack, add another Compose action before your message Compose. In the Inputs field, use a Power Automate expression to extract just the name portion. This makes your Slack message read 'From: Jane Doe' instead of 'From: Jane Doe <[email protected]>', which looks messy in a formatted card.

1. 1Click '+ Add an action' above your message Compose
2. 2Search 'Compose' and add a second Compose action
3. 3Rename it 'Parse Sender Name' by clicking the three-dot menu > Rename
4. 4In Inputs, switch to Expression tab and enter: if(contains(triggerOutputs()?['body/from'], '<'), trim(first(split(triggerOutputs()?['body/from'], '<'))), triggerOutputs()?['body/from'])
5. 5Click OK

Flow canvas > If yes branch > + Add an action > Slack > Post message (V2)

Connect to Slack and add the Post Message action

Click '+ Add an action' after your message Compose step. Search 'Slack' and select the Slack connector. Choose the action 'Post message (V2)'. Power Automate will prompt you to sign in to Slack — use a bot token or sign in with the Slack account that owns the bot you want to post as. Set 'Channel Name' to your target support channel (e.g. #support-inbox). In the 'Message Text' field, select the output of your message Compose step from dynamic content.

1. 1Click '+ Add an action'
2. 2Search 'Slack' and select the Slack connector
3. 3Choose 'Post message (V2)'
4. 4Click 'Sign in' and authenticate your Slack workspace
5. 5Set 'Channel Name' to your support channel (e.g. #support-inbox)
6. 6In 'Message Text', pick the output of your message Compose from dynamic content

Flow canvas > If yes branch > + Add an action > SharePoint > Get items

Add a unique identifier to prevent duplicate posts

Power Automate's Gmail polling can occasionally fire twice for the same email, especially during service hiccups. To guard against this, add a 'Create item' action to a SharePoint list or use a Compose + Condition pattern to check whether the email Message ID has already been processed. At minimum, log the Gmail Message ID to a SharePoint list before posting to Slack, then add a condition at the top of the 'If yes' branch that checks if that ID already exists in the list. If it does, skip the Slack post.

1. 1Click '+ Add an action' at the top of the 'If yes' branch
2. 2Search 'SharePoint' and select 'Get items'
3. 3Set Site Address and List Name to your deduplication tracking list
4. 4Set Filter Query to: MessageId eq 'dynamic content: Message ID'
5. 5Add a Condition below it: if 'value' length is greater than 0, skip (go to 'If no')
6. 6At the end of your Slack post step, add SharePoint 'Create item' to log the Message ID

Flow canvas > If yes branch > Compose (Message Template) > Inputs

Format the Slack message with urgency tagging

Go back to your message Compose step and update the template to include a priority tag based on subject keywords. Use a Power Automate expression to check if the subject contains words like 'urgent', 'down', or 'broken' and prepend a red emoji to the message. This gives your team an instant visual cue without any manual triage. The expression runs inside your Compose Inputs field.

1. 1Click into your message Compose step
2. 2Switch the Inputs field to Expression mode
3. 3Enter the urgency prefix expression (see pro_tip_code below)
4. 4Append your existing dynamic content tokens after the expression result
5. 5Switch back to Dynamic Content mode and confirm tokens still appear as chips

Flow canvas > Test (top right) > Manually > Send email > Check Run history

Test the flow end-to-end with a real email

Click 'Save' in the top right, then click 'Test' and select 'Manually' to trigger a test run. Send a real email to your support inbox from an external address. Wait up to 5 minutes for the Gmail poll to fire. Watch the flow run detail panel — each step turns green on success or red on failure. Verify the Slack message lands in the correct channel with correct sender name, subject, received time, and body preview.

1. 1Click 'Save' in the top right toolbar
2. 2Click 'Test', select 'Manually', then click 'Test'
3. 3Send a test email to your support address from a personal email
4. 4Wait 1–5 minutes for the poll to trigger
5. 5Click 'Run history' in the left sidebar to see the run detail

My flows > [Flow name] > three-dot menu > Settings

Set the flow to run automatically and monitor with alerts

Your flow is already live once saved and tested — Automated cloud flows run continuously without any further toggle. To get notified of failures, click the three-dot menu on the flow card in 'My flows' and select 'Edit run-only users' to confirm ownership. Then go to 'Manage > Analytics' and enable 'Send email notifications on flow failure' in Flow settings. This sends a failure alert to the flow owner's email within 30 minutes of a failed run.

1. 1Go to 'My flows' in the left sidebar
2. 2Find your flow and click the three-dot menu
3. 3Select 'Settings'
4. 4Under 'Run only users', confirm the support account has access
5. 5Toggle on 'Send email notification when this flow fails'
6. 6Click 'Done'

Paste this expression into the Inputs field of your urgency-tagging Compose action (Step 8). It checks the subject for urgency keywords and returns a formatted Slack message header with a color-coded emoji prefix. Switch the Inputs field to Expression mode by clicking the 'fx' button on the right side of the field before pasting.

if(
  or(
    contains(toLower(triggerOutputs()?['body/subject']), 'urgent'),

if(
  or(
    contains(toLower(triggerOutputs()?['body/subject']), 'urgent'),
    contains(toLower(triggerOutputs()?['body/subject']), 'down'),
    contains(toLower(triggerOutputs()?['body/subject']), 'broken'),
    contains(toLower(triggerOutputs()?['body/subject']), 'critical'),
    contains(toLower(triggerOutputs()?['body/subject']), 'outage')
  ),
  concat(
    '🔴 *URGENT* Support Email\n',
    '*From:* ', outputs('Parse_Sender_Name'), ' (', triggerOutputs()?['body/from'], ')\n',
    '*Subject:* ', triggerOutputs()?['body/subject'], '\n',
    '*Received:* ', formatDateTime(triggerOutputs()?['body/receivedDateTime'], 'MMM dd, yyyy h:mm tt UTC'), '\n',
    '*Preview:* ', substring(replace(triggerOutputs()?['body/bodyPreview'], '\r\n', ' '), 0, min(300, length(triggerOutputs()?['body/bodyPreview'])))
  ),
  concat(
    'New Support Email\n',
    '*From:* ', outputs('Parse_Sender_Name'), ' (', triggerOutputs()?['body/from'], ')\n',
    '*Subject:* ', triggerOutputs()?['body/subject'], '\n',
    '*Received:* ', formatDateTime(triggerOutputs()?['body/receivedDateTime'], 'MMM dd, yyyy h:mm tt UTC'), '\n',
    '*Preview:* ', substring(replace(triggerOutputs()?['body/bodyPreview'], '\r\n', ' '), 0, min(300, length(triggerOutputs()?['body/bodyPreview'])))
  )
)