Beginner~8 min setupCommunication & SupportVerified April 2026
Slack logo
Help Scout logo

How to Send Help Scout VIP Alerts to Slack with Zapier

Zapier watches Help Scout for new conversations from tagged VIP customers and fires an instant Slack message to your support channel with ticket details and a direct link.

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

Best for

Support teams who need to respond within minutes when a high-value customer opens a ticket in Help Scout.

Not ideal for

Teams with hundreds of VIP tickets per day — at that volume, a digest via Make costs less and reduces Slack noise.

Sync type

real-time

Use case type

notification

Real-World Example

💡

A 12-person SaaS company uses this to ping #vip-support in Slack the moment any customer tagged 'Enterprise' or 'Priority' opens a Help Scout conversation. Before this Zap, support leads checked Help Scout every 30-45 minutes and routinely missed tickets from $50K+ accounts for over an hour. Now the first response time on VIP tickets dropped from 62 minutes to under 8.

What Will This Cost?

Drag the slider to your expected monthly volume.

/mo
505005K50K

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

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

Before You Start

Make sure you have everything ready.

Help Scout account with at least one active mailbox and permission to install third-party integrations
Slack workspace with permission to add apps and post to the target alert channel
Zapier account on a plan that supports multi-step Zaps (the Filter step requires a paid plan or trial)
VIP or priority tags already created and consistently applied in Help Scout so the filter has something to match against
A dedicated Slack channel for VIP alerts already created and accessible to the support team

Field Mapping

Map these fields between your apps.

FieldAPI Name
Required
Customer Name
Customer Email
Conversation Subject
Tags
Web URL
Slack Channel
4 optional fields▸ show
Mailbox Name
Assigned To
Created At
Bot Username

Step-by-Step Setup

1

zapier.com > Dashboard > Create Zap

Create a new Zap in Zapier

Log into zapier.com and click the orange 'Create Zap' button in the left sidebar. The Zap editor opens in a two-panel view — the left panel shows your step list and the right panel shows configuration options. You'll build this Zap with one trigger, one filter, and one action. Name the Zap something like 'Help Scout VIP → Slack Alert' at the top so it's easy to find later.

  1. 1Log into zapier.com
  2. 2Click 'Create Zap' in the left sidebar
  3. 3Click the Zap name field at the top and type 'Help Scout VIP → Slack Alert'
  4. 4Click the 'Trigger' step in the left panel to start configuration
What you should see: You should see a blank Zap editor with a 'Trigger' step highlighted and an empty right-side configuration panel.
2

Zap Editor > Trigger > App & Event

Set Help Scout as the trigger app

In the trigger configuration panel, type 'Help Scout' into the app search field. Select 'Help Scout' from the results — the icon is a blue speech bubble. You'll then choose the event that fires the Zap. This workflow uses the 'New Conversation' event, which fires via webhook the moment a ticket is created in Help Scout.

  1. 1Click the 'App & Event' tab in the trigger panel
  2. 2Type 'Help Scout' in the search field
  3. 3Select 'Help Scout' from the dropdown
  4. 4Under 'Trigger Event', select 'New Conversation'
  5. 5Click 'Continue'
What you should see: You should see 'Help Scout — New Conversation' displayed in the trigger step and a 'Continue' button that is now active.
Common mistake — Help Scout offers both 'New Conversation' and 'New Customer' triggers. Pick 'New Conversation' — 'New Customer' fires on account creation, not ticket creation, and the filter in Step 4 won't have ticket fields to check.
Zapier
+
click +
search apps
Slack
SL
Slack
Set Help Scout as the trigge…
Slack
SL
module added
3

Zap Editor > Trigger > Account

Connect your Help Scout account

Zapier will ask you to connect a Help Scout account. Click 'Sign in to Help Scout' and a popup will open asking you to authorize Zapier via OAuth. Log in with the Help Scout credentials that have Inbox access — ideally a dedicated integration account, not a personal one. Once authorized, Zapier pulls your available mailboxes.

  1. 1Click 'Sign in to Help Scout'
  2. 2In the popup, enter your Help Scout email and password
  3. 3Click 'Authorize' to grant Zapier read access
  4. 4Select the correct mailbox from the 'Mailbox' dropdown (e.g., 'Support')
  5. 5Click 'Continue'
What you should see: You should see your Help Scout account name appear with a green checkmark and the mailbox selector populated with your inboxes.
Common mistake — If you have multiple Help Scout mailboxes, Zapier will only monitor the one you select here. If VIP tickets arrive across multiple mailboxes, you'll need a separate Zap per mailbox or upgrade to a plan that supports multi-step Zaps with routers.
Zapier settings
Connection
Choose a connection…Add
click Add
Slack
Log in to authorize
Authorize Zapier
popup window
Connected
green checkmark
4

Zap Editor > Trigger > Test

Test the Help Scout trigger

Click 'Test trigger' to pull in sample conversation data from Help Scout. Zapier fetches the three most recent conversations from your selected mailbox and displays each field — subject, customer email, status, tags, assignee, and conversation URL. Check that the 'Tags' field is present in the returned data. You'll use it in the next step to filter for VIP tickets only.

  1. 1Click 'Test trigger'
  2. 2Wait 5-10 seconds for Zapier to fetch sample data
  3. 3Expand the sample result and scroll to find the 'Tags' field
  4. 4Confirm at least one sample conversation has a tag value
  5. 5Click 'Continue with selected record'
What you should see: You should see a table of conversation fields. The 'Tags' row should show values like 'enterprise' or 'vip' if any of your recent tickets carry those tags.
Common mistake — If the Tags field is blank for all three samples, Zapier won't let you set up the filter correctly in the next step. Go to Help Scout, add a tag to a recent test conversation, then return and re-run the test.
Zapier
▶ Turn on & test
executed
Slack
Help Scout
Help Scout
🔔 notification
received
5

Zap Editor > + > Filter by Zapier

Add a Filter step to catch only VIP tickets

Click the '+' icon between the trigger and action steps to add a new step. Choose 'Filter' from the built-in tools list. This is Zapier's native conditional logic — no extra app connection needed. Set the filter to check whether the Tags field from Help Scout contains your VIP identifier. If the condition is false, the Zap stops here and no Slack message fires.

  1. 1Click the '+' button below the trigger step
  2. 2Select 'Filter' from the built-in tools
  3. 3In the first dropdown, select 'Tags' from the Help Scout data
  4. 4In the condition dropdown, select '(Text) Contains'
  5. 5In the value field, type your VIP tag exactly as it appears in Help Scout (e.g., 'enterprise')
  6. 6To add a second tag condition, click 'OR' and repeat for 'vip' or 'priority'
What you should see: You should see a green 'Your Zap would not have been filtered out' message if your sample ticket carries a matching tag, confirming the filter logic is correct.
Common mistake — Tag matching is case-sensitive in Zapier's Filter. If Help Scout stores the tag as 'Enterprise' (capital E) and you type 'enterprise', the filter will never pass. Check your exact tag casing in Help Scout under Conversations > Tags before setting this up.
Slack
SL
trigger
filter
Condition
matches criteria?
yes — passes through
no — skipped
Help Scout
HE
notified
6

Zap Editor > Action > App & Event

Add Slack as the action app

Click the '+' button below the Filter step to add the action. Search for 'Slack' and select it. For the action event, choose 'Send Channel Message' — this posts a formatted message to a specific Slack channel rather than a DM. This is the right choice for team-visible priority alerts.

  1. 1Click the '+' button below the Filter step
  2. 2Type 'Slack' in the app search and select it
  3. 3Under 'Action Event', select 'Send Channel Message'
  4. 4Click 'Continue'
What you should see: You should see 'Slack — Send Channel Message' listed as your action step with the account connection prompt ready.
7

Zap Editor > Action > Account

Connect your Slack workspace

Click 'Sign in to Slack' and authorize Zapier via the Slack OAuth popup. Zapier requests permission to post messages on your behalf. Use an account that has access to your #vip-support or equivalent alert channel. After authorization, Zapier lists your available channels in the Channel dropdown.

  1. 1Click 'Sign in to Slack'
  2. 2Select your workspace in the OAuth popup
  3. 3Click 'Allow' to grant Zapier posting permissions
  4. 4Return to the Zap editor and confirm your workspace name appears
  5. 5Click 'Continue'
What you should see: You should see your Slack workspace name with a green checkmark and the action configuration fields now visible.
Common mistake — Zapier posts messages as the connected Slack user by default. If you want messages to appear from a bot name like 'Support Bot', you must check 'Send as a bot?' in the message configuration and set a bot username — otherwise the message shows your personal name.
8

Zap Editor > Action > Configure

Configure the Slack message fields

Select your alert channel from the Channel dropdown (e.g., #vip-support). Then build the message text using Help Scout data fields from your trigger. Click into the Message Text field and use Zapier's field picker (the blue insert button) to pull in dynamic values. Write a message that gives your team everything they need at a glance — customer name, email, ticket subject, tag, and a clickable link to the conversation.

  1. 1Select the target channel from the 'Channel' dropdown (e.g., #vip-support)
  2. 2Click into the 'Message Text' field
  3. 3Type ':rotating_light: *VIP Ticket Alert*' as the header line
  4. 4On new lines, insert dynamic fields: Customer Name, Customer Email, Subject, Tags, and Conversation URL using the blue insert button
  5. 5Set 'Send as a bot?' to Yes and enter a bot name like 'Support Alert'
  6. 6Leave 'Message Type' as 'In Channel' so the whole team sees it
What you should see: The Message Text field should show a mix of static text and purple-highlighted dynamic field tokens like '{Customer Name}' and '{Conversation URL}'.
Common mistake — The Conversation URL field from Help Scout links directly to the ticket in your Help Scout dashboard. Do not use the 'Thread Reply' message type here — threading hides the alert from anyone not already watching that thread, defeating the purpose of a channel-wide alert.
Message template
📬 New entry: {{1.name}}
Email: {{1.email}}
Details: {{1.description}}
Slack fields
text
user
channel
ts
thread_ts
available as variables:
1.props.text
1.props.user
1.props.channel
1.props.ts
1.props.thread_ts
9

Zap Editor > Action > Test

Test the Slack action

Click 'Test action' to send a real Slack message using your sample Help Scout data. Switch to Slack and check your alert channel — the message should appear within 10-15 seconds. Confirm all dynamic fields rendered correctly: customer name shows a real name (not a field token), the URL is clickable, and the tags are visible. If a field shows blank, the sample ticket was missing that value — that's a data issue in Help Scout, not a Zap error.

  1. 1Click 'Test action'
  2. 2Open Slack and navigate to your alert channel
  3. 3Confirm the test message arrived with correct field values
  4. 4Click the conversation URL in Slack to verify it opens the right Help Scout ticket
  5. 5Return to Zapier and click 'Continue' if the test looks correct
What you should see: A Slack message should appear in your alert channel showing real customer data from the Help Scout sample, with a working link to the ticket.
10

Zap Editor > Publish

Turn on the Zap

Click 'Publish' in the top-right corner of the Zap editor. Zapier will show a confirmation screen asking you to review the trigger, filter, and action one more time. Toggle the Zap from Off to On. The Zap is now live and listening for new Help Scout conversations via webhook — no delay, no polling interval.

  1. 1Click the 'Publish' button in the top-right corner
  2. 2Review the summary screen to confirm trigger, filter, and action are correct
  3. 3Click 'Publish & Turn On'
  4. 4Confirm the Zap status shows 'On' with a green toggle
What you should see: You should see the Zap listed on your dashboard with a green 'On' status. The trigger type should show 'Instant' confirming the webhook is active.
11

Help Scout > New Conversation + Zapier > Task History

Validate with a live VIP ticket

Create a real test conversation in Help Scout from a customer account that carries your VIP tag. You can do this by sending a test email to your support inbox from a tagged customer address, or by manually creating a conversation and adding the VIP tag before saving. Check Slack within 90 seconds — the alert should arrive. If it doesn't appear within 3 minutes, check Zapier's Task History for filter failures or connection errors.

  1. 1In Help Scout, click 'New Conversation' and fill in a test customer's details
  2. 2Add your VIP tag (e.g., 'enterprise') to the conversation before creating it
  3. 3Click 'Create Conversation'
  4. 4Switch to Slack and watch your alert channel for 60-90 seconds
  5. 5If no message arrives, go to zapier.com > Zap History and check for filter stops or errors
What you should see: A Slack alert should appear in your channel within 90 seconds with the correct customer name, subject, tags, and a working Help Scout link.
Common mistake — Tags must be applied at conversation creation time to trigger the filter correctly. If a support agent creates the ticket first and adds the VIP tag afterward, the Zap has already fired without the tag — the filter will have blocked it. Train your team to tag conversations before or during creation.

This Code by Zapier step replaces the basic Filter step and adds two things the native filter can't do: case-insensitive tag matching across a list of VIP tiers, and urgency detection based on keywords in the ticket subject. Paste this into a 'Code by Zapier' step (JavaScript mode) inserted between the Help Scout trigger and the Slack action. Map 'urgency_label' and 'age_label' from the code output into your Slack message template.

JavaScript — Code Step// Zapier Code by Zapier step (JavaScript)
▸ Show code
// Zapier Code by Zapier step (JavaScript)
// Place this BETWEEN the Help Scout trigger and the Slack action
// It replaces the basic Filter step with richer logic:

... expand to see full code

// Zapier Code by Zapier step (JavaScript)
// Place this BETWEEN the Help Scout trigger and the Slack action
// It replaces the basic Filter step with richer logic:
// - Matches multiple VIP tags case-insensitively
// - Calculates ticket age in minutes for SLA context
// - Sets an urgency label to prepend to the Slack message

const tags = (inputData.tags || '').toLowerCase();
const subject = (inputData.subject || '').toLowerCase();
const createdAt = new Date(inputData.created_at);
const now = new Date();
const ageMinutes = Math.round((now - createdAt) / 60000);

const vipTags = ['enterprise', 'vip', 'priority', 'platinum'];
const isVip = vipTags.some(tag => tags.includes(tag));

if (!isVip) {
  throw new Error('Not a VIP ticket — Zap stopped by code filter');
}

const urgencyKeywords = ['urgent', 'critical', 'down', 'production', 'outage', 'broken'];
const isUrgent = urgencyKeywords.some(kw => subject.includes(kw));

const urgencyLabel = isUrgent ? ':fire: URGENT VIP' : ':rotating_light: VIP';
const ageLabel = ageMinutes < 5 ? 'Just created' : `${ageMinutes} min ago`;

return [{
  is_vip: true,
  urgency_label: urgencyLabel,
  age_label: ageLabel,
  matched_tags: vipTags.filter(tag => tags.includes(tag)).join(', ')
}];

Going live

Production Checklist

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

Troubleshooting

Common errors and how to fix them.

Frequently Asked Questions

Common questions about this workflow.

Analysis

VerdictWhy Zapier for this workflow

Use Zapier for this if your support team has no developer resources and needs this running today. Setup is under 20 minutes, the filter configuration is visual, and the Help Scout webhook fires within seconds of ticket creation. Two other good reasons: Zapier's Task History UI makes it easy for non-technical team leads to debug failed alerts without opening a terminal, and the Slack app integration is mature with no quirks around bot naming or channel targeting. The one scenario where you'd skip Zapier: if you need the alert to also update a CRM, log to a spreadsheet, and page an on-call engineer simultaneously — that kind of multi-branch logic is painful to build in Zapier and cheap in Make or n8n.

Cost

The cost math is straightforward. This Zap uses 2 tasks per run: one for the Filter step and one for the Slack action. A team with 200 VIP tickets per month burns 400 tasks. Zapier's Starter plan includes 750 tasks/month at $19.99/month, so you have headroom. At 400 VIP tickets/month you'd hit 800 tasks and need the Professional plan at $49/month. Make handles the same volume on its free tier (1,000 operations/month) or its Core plan at $9/month — roughly $480/year cheaper at scale. For most teams under 300 VIP tickets per month, Zapier's price is fine given the time savings in setup and maintenance.

Tradeoffs

Here's how the alternatives compare for this specific workflow. Make has a 'Watch Conversations' Help Scout module with built-in tag filtering in the module config — no separate filter step needed, which saves one operation per run. n8n lets you self-host and run unlimited workflows at a fixed server cost, which matters if you're paranoid about ticket data leaving your infrastructure. Power Automate has a Help Scout connector but it's a premium connector requiring a per-user plan add-on, making it the most expensive option here for no meaningful benefit. Pipedream gives you full Node.js control and can enrich the Slack message with CRM data in the same step, but requires a developer to set it up. Zapier is still the right call if the person setting this up is a support ops manager, not an engineer — the filter UI and test-mode feedback loop are genuinely faster for non-coders.

Three things you'll hit after going live. First, Help Scout's tag field returns a comma-separated string, not an array — if you ever try to parse individual tags in a Formatter step, you'll need to use the 'Split Text' option explicitly or the whole string gets treated as one value. Second, if a Help Scout conversation is created via API by an integration (like a chatbot or contact form tool), the webhook sometimes fires before the customer record is fully written, resulting in blank name and email fields in Slack. A 30-second Delay step before the Slack action fixes this in most cases. Third, Zapier auto-pauses Zaps after 10 consecutive errors — a temporary Help Scout API outage can silently kill your alert system for hours if you don't have error email notifications enabled. Turn those on before you go to sleep.

Ideas for what to build next

  • Route alerts by tier into separate Slack channelsAdd a Zapier Router step after the filter to split 'enterprise' tickets into #enterprise-urgent and 'vip' tickets into #vip-support, so each tier gets dedicated attention without cross-channel noise.
  • Auto-assign VIP tickets to a dedicated agent in Help ScoutAdd a second action step that uses the Help Scout 'Update Conversation' action to assign the ticket to your senior support agent immediately — pairing the Slack alert with automatic ownership so nothing slips through.
  • Build a daily VIP ticket digest instead of per-ticket alertsIf alert volume grows above 15-20 VIP tickets per day, replace this Zap with a scheduled Make scenario that batches the day's VIP tickets into a single Slack digest at 9am — quieter channel, same visibility.

Related guides

Was this guide helpful?
Slack + Help Scout overviewZapier profile →