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

How to Send Help Scout Ticket Updates to Slack with Zapier

Automatically posts a Slack message whenever a Help Scout ticket is closed, reopened, or reassigned — keeping your support team informed without checking Help Scout manually.

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

Best for

Support teams of 3–20 people who want a shared Slack channel to track ticket status changes without toggling between tools.

Not ideal for

Teams processing hundreds of ticket changes per hour — at that volume, polling delays and Zapier task costs add up fast; use Make or a native Help Scout webhook instead.

Sync type

scheduled

Use case type

notification

Real-World Example

💡

A 10-person SaaS customer success team routes all support into Help Scout but lives in Slack. Before this Zap, a ticket could sit closed or reassigned for 2–3 hours before anyone on the team noticed. After setup, a message fires to #support-updates within 15 minutes of any status change, showing the ticket subject, assignee, new status, and a direct link back to Help Scout.

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 Manager-level access to authorize the Zapier OAuth connection
Zapier account — free tier works for testing, but a paid plan is needed for polling intervals under 15 minutes
Slack workspace where you have permission to add apps and post to the target channel
At least one recent Help Scout conversation with a status change so Zapier can pull test data during setup
Target Slack channel already created before setup — Zapier cannot create channels for you

Field Mapping

Map these fields between your apps.

FieldAPI Name
Required
Conversation Subject
Status
Web URL
7 optional fields▸ show
Assigned To First Name
Assigned To Last Name
Customer Email
Customer Name
Mailbox Name
Tags
Number

Step-by-Step Setup

1

zapier.com > Dashboard > Create Zap

Create a new Zap in Zapier

Log in at zapier.com and click the orange 'Create Zap' button in the left sidebar. You'll land on the Zap editor, which shows a two-panel layout: the left panel lists your steps, and the right panel is where you configure each one. The editor starts with a single trigger step labeled 'Trigger' and prompts you to search for an app. You're building from Help Scout outward to Slack, so start by setting up the trigger.

  1. 1Click the orange 'Create Zap' button in the left sidebar
  2. 2Click the 'Trigger' step in the left panel to open the app search
  3. 3Type 'Help Scout' in the search bar
  4. 4Select 'Help Scout' from the results list
What you should see: You should see the Help Scout trigger configuration panel open on the right side, showing a 'Trigger Event' dropdown.
Common mistake — Make sure you select the standard 'Help Scout' app, not 'Help Scout (Legacy)'. The legacy version uses an older API and is missing several conversation trigger events.
2

Zap Editor > Trigger > Trigger Event

Choose your trigger event

Click the 'Trigger Event' dropdown. Help Scout's Zapier integration offers several conversation events. For status changes, the most useful trigger is 'Conversation Status Changed' — this fires when a ticket moves to closed, active, pending, or spam. If you also want to catch reassignments, you'll need a separate Zap using 'Conversation Assigned'. Pick one trigger per Zap; don't try to combine them here.

  1. 1Click the 'Trigger Event' dropdown
  2. 2Select 'Conversation Status Changed' from the list
  3. 3Click 'Continue' to move to the account connection step
What you should see: The panel should now show 'Conversation Status Changed' selected and a 'Continue' button at the bottom.
Common mistake — There is no single trigger that covers every status change type AND reassignment in one Zap. If you need both, build two separate Zaps — one for status changes, one for assignments.
Zapier
+
click +
search apps
Slack
SL
Slack
Choose your trigger event
Slack
SL
module added
3

Zap Editor > Trigger > Choose Account

Connect your Help Scout account

Zapier will prompt you to sign into Help Scout. Click 'Sign in to Help Scout' and a pop-up OAuth window will appear. Log in with your Help Scout credentials and authorize Zapier's access. Once authorized, the pop-up closes and you'll see your Help Scout account appear in a dropdown labeled 'Choose account'. Select it and click 'Continue'.

  1. 1Click 'Sign in to Help Scout'
  2. 2Complete the OAuth login in the pop-up window
  3. 3Select your Help Scout account from the 'Choose account' dropdown
  4. 4Click 'Continue'
What you should see: You should see a green checkmark next to your Help Scout account name and the 'Continue' button becomes active.
Common mistake — You must authorize with an account that has at least Manager-level access in Help Scout. Viewer-only accounts cannot authorize the Zapier integration and will fail silently at the OAuth step.
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 > Configure

Configure the trigger filters

After connecting, Zapier shows a 'Configure' panel for the trigger. You can optionally filter by Mailbox — if you have multiple mailboxes in Help Scout and only want updates from one (e.g., 'Support' but not 'Billing'), select it here from the Mailbox dropdown. If you want all mailboxes, leave it blank. You can also filter by Status if you only want to catch closed tickets, for example. Once configured, click 'Continue'.

  1. 1Optional: Select a specific mailbox from the 'Mailbox' dropdown
  2. 2Optional: Select a specific status from the 'Status' dropdown (e.g., 'closed')
  3. 3Click 'Continue' to proceed to test the trigger
What you should see: The panel advances to the 'Test trigger' step, showing a 'Find Data' button.
Common mistake — Filters are the most common place setups break. Double-check the field name and value exactly match what your app sends — a single capital letter difference will block everything.
Slack
SL
trigger
filter
Condition
matches criteria?
yes — passes through
no — skipped
Help Scout
HE
notified
5

Zap Editor > Trigger > Test Trigger

Test the Help Scout trigger

Click 'Test trigger' so Zapier polls Help Scout for a recent conversation that matches your configuration. Zapier will return up to 3 recent conversations where the status changed. You'll see a list of records — click into one to see all the available data fields, including subject, status, assignee name, customer email, and a URL. These are the fields you'll map into your Slack message in the next steps. Verify the data looks correct before continuing.

  1. 1Click 'Test trigger'
  2. 2Wait 5–10 seconds for Zapier to pull records from Help Scout
  3. 3Click on a returned record to expand its fields
  4. 4Confirm you can see fields like 'Subject', 'Status', 'Assigned To', and 'Web URL'
What you should see: You should see at least one Help Scout conversation record with populated fields including subject, status, and a direct URL to the conversation.
Common mistake — If Zapier returns no records, it means no conversations have had a status change recently in the selected mailbox. Manually close or reopen a test ticket in Help Scout first, then re-run the test.
Zapier
▶ Turn on & test
executed
Slack
Help Scout
Help Scout
🔔 notification
received
6

Zap Editor > Action > Choose App

Add Slack as the action app

Click the '+' button below the trigger step to add an action. Search for 'Slack' in the app search and select it. Then choose an action event from the dropdown. 'Send Channel Message' is the right choice here — it posts to a public or private channel. If you need to notify a specific person directly, use 'Send Direct Message' instead. For team-wide ticket visibility, 'Send Channel Message' is the standard approach.

  1. 1Click the '+' button below the trigger step
  2. 2Type 'Slack' in the app search bar
  3. 3Select 'Slack' from the results
  4. 4Choose 'Send Channel Message' as the action event
  5. 5Click 'Continue'
What you should see: The Slack action configuration panel opens, showing a 'Choose account' prompt.
7

Zap Editor > Action > Choose Account

Connect your Slack workspace

Click 'Sign in to Slack' and authorize Zapier in the OAuth pop-up. You'll need to select the correct Slack workspace if you're a member of multiple. Zapier requests permission to post messages on your behalf. Once you authorize and close the pop-up, your workspace name appears in the 'Choose account' dropdown. Select it and click 'Continue'.

  1. 1Click 'Sign in to Slack'
  2. 2Select the correct workspace in the Slack OAuth screen
  3. 3Click 'Allow' to grant Zapier posting permissions
  4. 4Select your workspace from the 'Choose account' dropdown
  5. 5Click 'Continue'
What you should see: Your Slack workspace name appears with a green checkmark and the panel advances to the 'Configure' step.
Common mistake — Zapier posts messages as its own bot user, not as your personal Slack account. The message will show 'Zapier' as the sender. If your workspace has a custom bot name set up, it won't apply here — you'd need a Slack app with a custom bot token instead.
8

Zap Editor > Action > Configure

Configure the Slack message

Select the target channel from the 'Channel' dropdown — type the channel name to search if you have many. In the 'Message Text' field, build your message using a mix of static text and dynamic fields from Help Scout. Click inside the Message Text box and then click the purple data picker icon (looks like a lightning bolt) to insert Help Scout fields. A well-structured message includes the ticket subject, new status, assignee, and a clickable link. Slack supports basic markdown here: use asterisks for bold and angle brackets for links.

  1. 1Select your target channel from the 'Channel' dropdown (e.g., #support-updates)
  2. 2Click into the 'Message Text' field
  3. 3Type your message template and insert Help Scout fields using the data picker
  4. 4Example message: '*Ticket Update:* <{{Web URL}}|{{Subject}}> — Status changed to *{{Status}}*. Assigned to: {{Assigned To First Name}} {{Assigned To Last Name}}'
What you should see: The Message Text field shows a mix of static text and orange pill-shaped dynamic field tokens pulled from Help Scout.
Common mistake — The 'Assigned To' field will be blank if a ticket is unassigned. Add a fallback by typing 'Unassigned' after the field token — Zapier won't do this automatically.
Message template
📬 New entry: {{1.name}}
Email: {{1.email}}
Details: {{1.description}}
9

Zap Editor > Action > Configure > Advanced Options

Set optional message formatting

Scroll down in the Slack action configuration to find additional options. Set 'Send as Bot' to Yes — this is the default and required for channel posting. You can customize the 'Bot Name' field (e.g., 'Help Scout Bot') and add an emoji as the 'Bot Icon' (e.g., :mailbox:) to make the messages visually distinct in your Slack feed. Leave 'Link Names' set to Yes so @mentions in ticket subjects render correctly.

  1. 1Set 'Send as Bot' to 'Yes'
  2. 2Enter a bot name in the 'Bot Name' field (e.g., 'Help Scout Bot')
  3. 3Enter an emoji code in the 'Bot Icon' field (e.g., ':mailbox:')
  4. 4Set 'Link Names' to 'Yes'
  5. 5Click 'Continue'
What you should see: The configuration panel shows your bot name and icon set, and a 'Test action' button appears at the bottom.
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.
Message template
📬 New entry: {{1.name}}
Email: {{1.email}}
Details: {{1.description}}
10

Zap Editor > Action > Test Action

Test the Slack action

Click 'Test action' to send a real test message to your selected Slack channel using the sample Help Scout data pulled in Step 5. Open your Slack workspace and navigate to the channel — you should see the message appear within seconds. Review it carefully: check that the ticket subject renders correctly, the status field shows the right value, the assignee name is readable (not an ID), and the link is clickable. If anything looks wrong, go back and edit the Message Text field before publishing.

  1. 1Click 'Test action'
  2. 2Open your Slack workspace and navigate to the target channel
  3. 3Confirm the message appears with correct subject, status, assignee, and link
  4. 4Return to Zapier and click 'Continue' if the message looks correct
What you should see: A test Slack message appears in your channel showing real Help Scout ticket data — subject, status, assignee name, and a working link to the conversation.
Common mistake — The test message fires into your real Slack channel — not a sandbox. Give your team a heads-up before running the test, or temporarily point the Zap at a private test channel.
11

Zap Editor > Publish

Name and publish the Zap

Click 'Publish' in the top right corner of the Zap editor. Before it goes live, give the Zap a clear name — something like 'Help Scout Status Change → #support-updates Slack'. This matters when you have multiple Zaps and need to find this one quickly. Once published, the Zap status shows 'On' in your dashboard. Zapier will now poll Help Scout every 1–15 minutes (depending on your plan) and fire the Slack message when it detects a status change.

  1. 1Click the Zap name field at the top of the editor and enter a descriptive name
  2. 2Click the 'Publish' button in the top right corner
  3. 3Confirm the Zap status switches to 'On' in your Zapier dashboard
What you should see: The Zap shows a green 'On' toggle in your Zapier dashboard and the name you set appears in the Zaps list.
Common mistake — Free and Starter Zapier plans poll every 15 minutes. Professional plans poll every 1–2 minutes. If your team needs faster updates, you'll need at least a Professional plan — there's no way to force real-time polling on Help Scout's Zapier trigger.

This Code by Zapier step runs between the trigger and the Slack action. It formats a richer message with emoji status indicators and handles the blank-assignee edge case cleanly. Paste it into a 'Code by Zapier' step (action event: 'Run JavaScript'), then map the output fields into your Slack message instead of the raw Help Scout fields.

JavaScript — Code Step// Input data mapped from Help Scout trigger
▸ Show code
// Input data mapped from Help Scout trigger
const subject = inputData.subject || 'No subject';
const status = inputData.status || 'unknown';

... expand to see full code

// Input data mapped from Help Scout trigger
const subject = inputData.subject || 'No subject';
const status = inputData.status || 'unknown';
const assignee = (inputData.assigneeFirst && inputData.assigneeLast)
  ? `${inputData.assigneeFirst} ${inputData.assigneeLast}`
  : 'Unassigned';
const customerName = inputData.customerName || 'Unknown customer';
const webUrl = inputData.webUrl || '';
const ticketNumber = inputData.number || '';

// Map status to emoji
const statusEmoji = {
  closed: ':white_check_mark:',
  active: ':large_blue_circle:',
  pending: ':hourglass_flowing_sand:',
  spam: ':no_entry_sign:'
};

const emoji = statusEmoji[status.toLowerCase()] || ':grey_question:';
const statusLabel = status.charAt(0).toUpperCase() + status.slice(1);

// Build formatted Slack message
const message = webUrl
  ? `${emoji} *<${webUrl}|#${ticketNumber}: ${subject}>* changed to *${statusLabel}*\n> Assigned to: ${assignee} | Customer: ${customerName}`
  : `${emoji} *#${ticketNumber}: ${subject}* changed to *${statusLabel}*\n> Assigned to: ${assignee} | Customer: ${customerName}`;

output = [{ message, assignee, statusLabel, emoji }];

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 is non-technical and you need this running today. The guided Zap builder handles the Help Scout OAuth, the Slack connection, and the field mapping in about 12 minutes total — no JSON, no API docs, no code. It's also the right call if you're already paying for Zapier for other workflows and have task capacity to spare. The one scenario where you'd skip Zapier: if your team closes 200+ tickets per day. At that volume, each status change costs a task, and you'll hit the Professional plan's task cap faster than expected.

Cost

The math is straightforward. Each ticket status change = 1 Zapier task. A team closing 50 tickets per day generates roughly 1,500 tasks per month from this Zap alone (accounting for some reopens and reassignments). Zapier's free plan caps at 100 tasks — you'll exceed it in two days. Starter ($19.99/month) gives you 750 tasks. Professional ($49/month) gives you 2,000. Make's equivalent setup costs $9/month for 10,000 operations. If this is your only Zap, Zapier is $40/month more expensive for the same outcome.

Tradeoffs

Make handles this use case with a Watch Conversations module that's more configurable — you can filter by tag, customer, or custom field at the trigger level without adding extra steps. n8n can use Help Scout's native webhooks (not polling), which means true real-time delivery in under 5 seconds instead of up to 15 minutes. Power Automate doesn't have a first-party Help Scout connector, so you'd be building on HTTP actions with manual auth — not worth it. Pipedream also supports webhook-based triggers from Help Scout and gives you full JavaScript control over message formatting. Zapier is still the right pick when your team won't touch code and the 15-minute polling delay is acceptable.

Three things you'll hit after go-live. First, polling lag catches people off guard — teams expect real-time and get 15 minutes. Set expectations upfront. Second, the assignee field goes blank on unassigned tickets and Zapier doesn't warn you — test this before publishing by running a test with an unassigned ticket in Help Scout. Third, if you have a high-volume mailbox (transactional emails, spam, auto-responders), the Zap fires on those too. A Filter step scoped to specific statuses or tags is not optional — it's necessary to keep your Slack channel from becoming noise.

Ideas for what to build next

  • Route by mailbox to multiple channelsAdd a Zapier 'Paths' step to send billing tickets to #billing-support and general tickets to #support-updates based on the Help Scout mailbox name field. This keeps channel noise low as your team scales.
  • Add a daily digest of open ticketsBuild a second Zap on a Schedule trigger that queries Help Scout for all open tickets older than 24 hours and posts a summary to Slack each morning. This catches tickets that never changed status but still need attention.
  • Log status changes to a Google Sheet for reportingFork the same Help Scout trigger into a parallel action that appends a row to Google Sheets with timestamp, ticket number, status, and assignee. After 30 days you'll have enough data to spot response time patterns and workload imbalances.

Related guides

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