How fast will the Slack alert arrive after a VIP ticket is created in Help Scout?

Expect 1-3 minutes on a standard Power Automate Premium plan. The Help Scout connector polls rather than receiving a true webhook push, so there is always some lag. On higher-load periods or lower-tier plans, it can stretch to 5 minutes. If you need under 60 seconds, use Zapier or Make instead.

Can I trigger the alert based on the customer's company instead of a tag?

Yes. In Step 5, change the Condition field from 'Tags' to 'Organization' from the Parse JSON outputs, and enter the exact company name. This works well if you maintain a list of named accounts by company rather than tagging contacts. The downside: you'll need one condition per company name, or use an array of contains() expressions.

What happens if a VIP customer replies to an existing ticket — does that also trigger an alert?

No. The 'When a new conversation is created' trigger only fires for brand new tickets, not for replies or status updates on existing ones. If you also want alerts on VIP replies, you need a second flow using the 'When a conversation is updated' trigger with an additional filter for new customer replies.

Can I filter by both VIP tag AND ticket priority (e.g. only Urgent tickets)?

Yes, but you'll need to add a second Condition inside the first 'If yes' branch. The outer condition checks the VIP tag; the inner condition checks whether the ticket subject or a custom field contains 'Urgent'. Power Automate doesn't support AND logic natively in a single Condition card for different field types.

Intermediate~15 min setupCommunication & SupportVerified April 2026

How to Send Help Scout VIP Ticket Alerts to Slack with Power Automate

When a high-priority customer creates a support ticket in Help Scout, Power Automate checks their account tag and instantly posts a formatted alert to a Slack channel so your team can respond first.

Steps and UI details are based on platform versions at time of writing — check each platform for the latest interface.

Power Automate

Also on:Make Zapier N8n Pipedream

Best for

Support teams inside Microsoft 365 environments who need VIP customer tickets flagged in Slack without writing any code

Not ideal for

Teams that need sub-30-second alert latency — Power Automate's Help Scout connector polls every 1-3 minutes, so use Zapier or Make with webhooks if speed is critical

Sync type

real-time

Use case type

notification

Real-World Example

💡

A 20-person SaaS company tags enterprise accounts as 'VIP' in Help Scout. Before this flow, the support team had no way to know a $50K/year customer was waiting — tickets sat in the general queue for 45 minutes on busy days. Now, the moment a VIP ticket lands, a Slack message hits #vip-support with the customer name, subject line, and a direct link to the conversation, and the on-call rep picks it up in under 5 minutes.

What Will This Cost?

Drag the slider to your expected monthly volume.

Monthly workflow runs

/mo

505005K50K

Each platform counts differently — Zapier: 1 task per trigger. Make: 1 operation per module per record. n8n: 1 execution per run.

cheapest

Power Automatethis guide

$30/mo if billed monthly

Pipedream

$29/mo

Basic plan

Prices shown for annual billing. Based on published pricing as of April 2026.

Estimated ROI

1000

min saved/mo

$583

labor value/mo

Free

no platform cost

Based on ~2 min manual effort per operation at $35/hr fully loaded labor cost.

Implementation

Skip the setup

Import this workflow directly into Power Automate

Copy the pre-built Power Automate blueprint and paste it straight into Power Automate. All modules, filters, and field mappings are already configured — you just need to connect your accounts.

Before You Start

Make sure you have everything ready.

Help Scout account with Manager or Owner role — required to authorize the Power Automate connector via OAuth

Help Scout customers tagged with a consistent VIP or priority label (e.g. 'VIP', 'Enterprise') — the condition filter in Step 5 depends on this

Slack workspace admin access or permission to authorize third-party OAuth apps — needed to connect the Slack connector in Step 6

A dedicated Slack channel for VIP alerts already created (e.g. #vip-support) — the flow posts to this channel by name

Power Automate account with access to premium connectors — the Help Scout connector is a premium connector and requires a Power Automate Premium or per-flow plan

Field Mapping

Map these fields between your apps.

Field	API Name	Description
Required
Customer ID	`customerId`	Unique identifier for the Help Scout customer — used to look up full customer details including tags in the 'Get customer' action
Customer First Name	`firstName`	Customer's first name pulled from Help Scout contact record — included in the Slack message so the support rep knows who they're dealing with immediately
Customer Last Name	`lastName`	Customer's last name — combined with First Name in the Slack message for full identification
Customer Tags	`tags`	Comma-separated list of tags on the customer record — this is the field the Condition step checks to identify VIP accounts
Ticket Subject	`subject`	Subject line of the new Help Scout conversation — gives the support team immediate context on what the VIP customer needs without opening the ticket
Ticket Web URL	`webUrl`	Direct link to the conversation in the Help Scout web app — the most important field in the Slack message because it lets reps jump straight to the ticket in one click

4 optional fields▸ show

Customer Organization	`organization`	Company name associated with the customer in Help Scout — critical for VIP workflows where the account relationship matters more than the individual contact
Ticket Status	`status`	Current status of the conversation (active, pending, closed) — useful to include in the Slack message so reps don't rush to a ticket that was auto-closed
Mailbox Name	`mailboxId`	The Help Scout mailbox the ticket arrived in — relevant if your team routes Enterprise and SMB tickets to different mailboxes and you want that context in the alert
Created At Timestamp	`createdAt`	When the ticket was created in Help Scout — including this in the Slack message shows how long the ticket has been waiting if there's any polling delay

Step-by-Step Setup

make.powerautomate.com > My flows > + New flow > Automated cloud flow

Create a new Automated cloud flow in Power Automate

Go to make.powerautomate.com and sign in with your Microsoft account. In the left sidebar click 'My flows', then click '+ New flow' at the top of the page. Select 'Automated cloud flow' from the dropdown — this is the flow type that fires when an external event happens, which is what you need here. Give your flow a name like 'Help Scout VIP Ticket → Slack Alert' so it's easy to find later.

1Sign in at make.powerautomate.com
2Click 'My flows' in the left sidebar
3Click '+ New flow' near the top right
4Select 'Automated cloud flow' from the menu
5Enter the flow name and click 'Create'

✓ What you should see: A blank flow canvas opens with a prompt to choose your trigger. You should see the trigger search bar in the center of the screen.

⚠

Common mistake — Do not pick 'Instant cloud flow' — that requires a manual button press and won't fire automatically when tickets arrive.

Flow canvas > Search connectors and triggers > Help Scout > When a new conversation is created

Set the Help Scout 'New Conversation' trigger

In the trigger search bar, type 'Help Scout' and select the Help Scout connector. Choose the trigger named 'When a new conversation is created'. This trigger polls Help Scout every 1-3 minutes for new conversations. You will be prompted to create a Help Scout connection — click 'Sign in' and authenticate with your Help Scout account credentials.

1Type 'Help Scout' in the trigger search bar
2Select the 'Help Scout' connector from the results
3Click 'When a new conversation is created'
4Click 'Sign in' to create a new Help Scout connection
5Authenticate with your Help Scout admin credentials

✓ What you should see: The trigger card appears on the canvas with a green checkmark and your Help Scout account email shown under the connection name.

⚠

Common mistake — The Help Scout connector in Power Automate uses OAuth2 and requires your Help Scout account to have Manager or Owner role — a restricted agent account will fail authentication silently.

Power Automate

click +

search apps

Slack

Set the Help Scout 'New Conv…

Slack

module added

Trigger card > Mailbox dropdown

Configure the trigger to watch the correct mailbox

Inside the trigger card, click the 'Mailbox' dropdown and select the specific Help Scout mailbox where VIP tickets arrive. If your team uses multiple mailboxes (e.g. 'Support', 'Enterprise'), pick the right one now — you can only filter one mailbox per flow. Leave all other fields at their defaults for now; filtering by customer tag happens in the next step.

1Click inside the 'Mailbox' dropdown on the trigger card
2Select the mailbox where enterprise or VIP tickets arrive
3Leave 'Status' and 'Assigned To' fields blank

✓ What you should see: The trigger card shows your selected mailbox name in the Mailbox field. No other fields need to be filled at this stage.

Flow canvas > + New step > Help Scout > Get customer

Add a 'Get customer details' action to retrieve account tags

Click '+ New step' below the trigger. Search for 'Help Scout' again and select the action 'Get customer'. This fetches full customer data — including tags — for the person who submitted the ticket. In the 'Customer Id' field, click the dynamic content picker (the lightning bolt icon) and select 'Customer Id' from the trigger outputs. This connects the ticket's customer to the lookup.

1Click '+ New step' below the trigger card
2Search 'Help Scout' in the action search bar
3Select 'Get customer' from the list
4Click the 'Customer Id' field
5Open the dynamic content panel and select 'Customer Id' from the trigger outputs

✓ What you should see: The 'Get customer' action card shows the Customer Id field populated with the blue dynamic content token labeled 'Customer Id'.

⚠

Common mistake — If you see multiple 'Customer Id' options in dynamic content, pick the one listed under the trigger name — not one from a prior action, which could be from a different context.

Flow canvas > + New step > Control > Condition

Add a Condition to check for the VIP tag

Click '+ New step' and choose 'Condition' from the Control category. This is how you filter so only VIP tickets trigger the Slack alert. In the left field of the condition, click the dynamic content picker and select 'Tags' from the 'Get customer' action outputs. Set the operator to 'contains'. In the right field, type the exact tag name you use in Help Scout for high-priority customers — for example 'VIP' or 'Enterprise'. Tag matching is case-sensitive.

1Click '+ New step'
2Select 'Control' from the categories, then click 'Condition'
3Click the left field of the condition row
4In the dynamic content panel, select 'Tags' under 'Get customer'
5Set the middle dropdown to 'contains'
6Type your VIP tag name exactly as it appears in Help Scout in the right field

✓ What you should see: The condition card shows three sections: 'If yes', 'If no', and your configured rule. The condition row should read: Tags contains VIP (or your chosen tag).

⚠

Common mistake — Help Scout tags are returned as a comma-separated string in this connector, not an array. If a customer has multiple tags like 'VIP, Enterprise', the 'contains' operator still works correctly — but if you use partial tag names (e.g. 'VI' to match 'VIP'), you risk false positives.

Slack

trigger

filter

Condition

matches criteria?

yes — passes through

no — skipped

Help Scout

notified

Condition > If yes > Add an action > Slack > Post message

Build the Slack connection inside the 'If yes' branch

Inside the 'If yes' branch of the condition, click 'Add an action'. Search for 'Slack' and select the Slack connector. Choose the action 'Post message'. Click 'Sign in' to create a Slack connection — this opens an OAuth window where you authorize Power Automate to post to your Slack workspace. Select the correct workspace from the dropdown if you belong to multiple.

1Click 'Add an action' inside the 'If yes' branch only
2Search 'Slack' in the action picker
3Select 'Post message' from the Slack connector
4Click 'Sign in' to create a new Slack connection
5Authorize Power Automate in the Slack OAuth popup
6Select the correct workspace if prompted

✓ What you should see: The Slack action card appears inside the 'If yes' branch with your Slack workspace name shown in the connection field and two required fields visible: Channel Name and Message Text.

⚠

Common mistake — Power Automate's Slack connector posts as the OAuth-authenticated user by default — your teammates will see your name as the sender, not a bot name. If you want a bot identity, you need to use the Slack HTTP action with a bot token instead.

Slack action card > Channel Name + Message Text fields

Configure the Slack channel and message content

In the 'Channel Name' field, type the exact Slack channel name where alerts should go — for example #vip-support. Do not include the # symbol in the field itself; just type the name. In the 'Message Text' field, build your alert using dynamic content tokens from earlier steps. A clear message should include: the customer's full name, their company, the ticket subject, and a direct link to the conversation in Help Scout.

1Type your channel name in the 'Channel Name' field (e.g. vip-support)
2Click inside the 'Message Text' field
3Open dynamic content and insert 'First Name' and 'Last Name' from 'Get customer'
4Add 'Subject' from the trigger outputs
5Add 'Web Url' from the trigger outputs to include a clickable link
6Optionally add 'Organization' from 'Get customer' for company context

✓ What you should see: The Message Text field shows a mix of static text and blue dynamic content tokens. A preview might look like: '🚨 VIP Ticket from [First Name] [Last Name] ([Organization]): [Subject] — [Web Url]'.

⚠

Common mistake — Map fields using the variable picker — don't type field names manually. Hand-typed variable names often have invisible spacing errors that produce blank output.

Flow canvas > Between trigger and Condition > + > Data Operation > Parse JSON

Add a Parse JSON step to safely extract nested customer fields

The 'Get customer' action returns some fields — like organization and phone — nested inside a JSON object. To reliably access them, click '+ New step' before the Condition step (use the + button between trigger and condition), search for 'Data Operation', and add 'Parse JSON'. Paste the Help Scout customer schema into the Schema field. This ensures dynamic content tokens for nested fields like 'organization name' appear cleanly in later steps instead of requiring manual expression syntax.

1Click the + icon between the 'Get customer' action and the Condition card
2Search 'Data Operation' and select 'Parse JSON'
3In the 'Content' field, select 'Body' from the 'Get customer' action via dynamic content
4Click 'Generate from sample' and paste a sample Help Scout customer API response
5Click 'Done' to generate the schema

✓ What you should see: The Parse JSON card shows a populated schema with fields like 'firstName', 'lastName', 'organization', and 'tags'. These fields now appear as clean tokens in the dynamic content panel for all subsequent steps.

⚠

Common mistake — If you skip this step and try to access nested fields directly, Power Automate will require you to write expressions like body('Get_customer')?['organization']?['name'] manually for every field — tedious and error-prone.

Slack fields

text

user

channel

thread_ts

available as variables:

1.props.text

1.props.user

1.props.channel

1.props.ts

1.props.thread_ts

Flow canvas > Save > Test > Manually

Test the flow with a real Help Scout test ticket

Click 'Save' at the top of the canvas, then click 'Test' in the top-right corner. Select 'Manually' and click 'Test'. Now go to Help Scout and create a new test conversation from a customer contact that already has your VIP tag applied. Return to Power Automate — within 1-3 minutes the flow should trigger. You'll see each step turn green with a checkmark if it succeeded, or red with an error message if something failed.

1Click 'Save' at the top of the canvas
2Click 'Test' in the top-right corner
3Select 'Manually' and click 'Test'
4Open Help Scout and create a new conversation from a VIP-tagged customer
5Return to Power Automate and wait up to 3 minutes for the run to appear

✓ What you should see: The flow run history shows all steps with green checkmarks. Your #vip-support Slack channel receives a message with the customer name, ticket subject, and a Help Scout link.

⚠

Common mistake — If you test with a customer who is not tagged as VIP, the flow will run but exit at the 'If no' branch — this is correct behavior. Make sure your test customer has the exact tag you configured in Step 5.

Power Automate

▶ Test flow

executed

✓

Slack

✓

Help Scout

🔔 notification

received

make.powerautomate.com > My flows > [Your Flow] > Toggle On

Set the flow to run automatically and review run frequency

Power Automate's Help Scout trigger polls on a schedule rather than receiving real-time webhook pushes. The default polling interval is typically 1-3 minutes. You cannot manually change this interval — it's set by the connector tier and your Power Automate plan. To verify the flow is active, go to 'My flows', find your flow, and confirm the toggle is set to 'On'. Check the run history after 24 hours to confirm it's firing consistently.

1Go to make.powerautomate.com > My flows
2Find your flow in the list
3Confirm the toggle next to the flow name is set to 'On'
4Click into the flow and review the '28 day run history' panel

✓ What you should see: The flow appears in 'My flows' with a green 'On' status indicator. The run history panel shows recent successful runs timed 1-3 minutes after test tickets were created.

Slack action card > ... menu > Configure run after

Add error handling for failed Slack posts

Click the three-dot menu on the Slack 'Post message' action card and select 'Configure run after'. Check the 'has failed' box in addition to 'is successful'. Then add a parallel branch action — for example, send an email via Outlook to a support manager — so critical alerts don't silently vanish if the Slack connection breaks. This takes 3 minutes to set up and saves you from blind spots during Slack outages.

1Click the '...' (three-dot) menu on the Slack action card
2Select 'Configure run after'
3Check the 'has failed' checkbox
4Click the + button to add a parallel action in the failure branch
5Add 'Send an email (V2)' via the Outlook connector as a fallback alert

✓ What you should see: The Slack action card now shows a small branching icon indicating it has a 'run after' configuration. The canvas shows a parallel path that triggers only when the Slack post fails.

This expression formats the Help Scout 'createdAt' timestamp into a readable time string and builds the full Slack message body in one expression — paste it into the 'Message Text' field of the Slack action using the Expression tab (not the Dynamic content tab) in Power Automate's formula editor.

JavaScript — Code Stepconcat(

▸ Show code

concat(
  '🚨 VIP Ticket — ',
  outputs('Parse_JSON')?['firstName'],

... expand to see full code

concat(
  '🚨 VIP Ticket — ',
  outputs('Parse_JSON')?['firstName'],
  ' ',
  outputs('Parse_JSON')?['lastName'],
  ' (',
  outputs('Parse_JSON')?['organization'],
  ')',
  '
Subject: ',
  triggerOutputs()?['body/subject'],
  '
Status: ',
  toUpper(triggerOutputs()?['body/status']),
  '
Opened: ',
  formatDateTime(triggerOutputs()?['body/createdAt'], 'yyyy-MM-dd HH:mm UTC'),
  '
',
  triggerOutputs()?['body/webUrl']
)

Going live

Production Checklist

Before you turn this on for real, confirm each item.

Confirm the Help Scout OAuth connection is authenticated with an account that has Manager or Owner role — restricted accounts cause silent auth failures

Test the Condition step with a customer who has the VIP tag AND one who does not — verify the 'If no' branch exits cleanly without posting to Slack

Verify the Slack channel name in the action matches the exact channel name in your workspace — Power Automate won't warn you if the channel doesn't exist, it will just fail silently

Set up the error handling fallback from Step 11 before going live — you don't want VIP alerts disappearing during a Slack outage

Check the flow's run history after the first 24 hours in production to confirm polling is firing consistently and not being throttled by your Power Automate plan tier

Applies when: polling

Add a 'Terminate' action in the 'If no' branch with status set to 'Cancelled' and a clear reason — this keeps your run history clean and distinguishes intentional skips from real failures

Document which Help Scout tag string the flow checks so future team members don't accidentally create tickets that bypass the filter by misspelling the tag

Troubleshooting

Common errors and how to fix them.

Frequently Asked Questions

Common questions about this workflow.

Analysis

VerdictWhy n8n for this workflow

Use Power Automate for this if your team already lives inside Microsoft 365 and you want the flow managed alongside your other IT automations in the same admin portal. Power Automate's audit logs, connection governance, and DLP policies make it the right call for companies with IT compliance requirements — something Zapier and Make can't match out of the box. The Help Scout connector exists and works. The Slack connector exists and works. Setup takes about 30 minutes including testing. The one scenario where you'd skip Power Automate: if your team needs alerts in under 60 seconds and isn't locked into the Microsoft ecosystem — pick Make instead, which supports Help Scout webhooks for near-instant triggers.

Cost

The real cost math: Power Automate Premium runs $15/user/month. The Help Scout connector is premium-only, so you can't avoid that tier. Each flow run consumes approximately 2-3 actions (trigger check, Get customer, Slack post). At 200 VIP tickets per month, you're at roughly 600 actions — well inside the 40,000 action/user/month ceiling on Premium. The per-flow plan is $100/month and covers unlimited runs for a single flow, which only makes sense if you have more than 6 users sharing this flow. Zapier's equivalent setup costs $49/month (Professional plan required for multi-step zaps with filters). Make handles the same volume for around $9/month on the Core plan. Power Automate is the most expensive option here unless you already own Premium licenses for other reasons.

Tradeoffs

Zapier has a cleaner setup experience for this specific use case — the filter step is a single UI element, and their Help Scout trigger averages under 2 minutes. Make supports Help Scout webhooks on their paid plan, meaning true real-time delivery and zero polling lag — that's a genuine technical advantage over Power Automate. n8n lets you self-host for free and build far more complex VIP routing logic, but you're maintaining infrastructure. Pipedream has the best developer experience if someone on your team writes JavaScript — you can parse the full Help Scout payload and apply complex tag logic in 20 lines. Power Automate is still right if compliance, SSO, and Microsoft admin governance matter more than speed or cost — and for many mid-market and enterprise teams, they do.

Three things you'll hit after setup. First: the Help Scout 'tags' field comes back as a plain comma-separated string, not a JSON array — if you try to use array functions like length() or first() on it, the flow will error. Use contains() string expressions only. Second: Slack connection tokens expire if the authenticating user's Slack account is deactivated or if workspace admins revoke third-party app permissions during a security audit — the flow fails silently with a 401 error and you won't know until a VIP ticket goes unnoticed. Set up the email fallback in Step 11. Third: Power Automate charges action runs even for polling attempts that find no new tickets — at the default polling frequency, you'll accumulate roughly 1,440 'empty' trigger checks per day. This doesn't approach any practical plan limits, but it does show up in your run history and can make logs harder to read. Use the 28-day run history view filtered by 'Succeeded with no actions triggered' to separate noise from real runs.

Ideas for what to build next

→
Add ticket assignment in the same flow — Extend the 'If yes' branch to also auto-assign the VIP ticket to a specific Help Scout agent or team using the 'Update conversation' action — so the alert and the assignment happen in a single automated step.
→
Build a daily VIP ticket digest — Create a second Scheduled cloud flow that runs every morning at 8am, queries Help Scout for all open VIP conversations older than 4 hours, and posts a summary list to Slack — catches anything that slipped through the real-time alert.
→
Escalate to a manager if unresponded after 30 minutes — Build a companion flow triggered on a schedule that checks whether VIP tickets created in the last 30 minutes still have no replies in Help Scout, and sends a second Slack DM directly to the support manager — closes the response accountability loop.