How fast does the Slack notification appear after a ticket is created in Help Scout?

Typically 1–2 minutes. Zapier's Help Scout trigger uses a webhook, not polling, so it fires as soon as Help Scout sends the event. The 1–2 minute gap is Zapier processing time, not a delay on Help Scout's side.

Can I send notifications to multiple Slack channels from one Zap?

Yes. Add additional Slack 'Send Channel Message' action steps to the same Zap — one per channel. Each step can have different message formatting. Keep in mind each action step counts as one Zapier task per ticket.

Will this Zap fire when a customer replies to an existing ticket, or only on new tickets?

Only on new tickets, as long as you used the 'New Conversation' trigger. Replies update an existing conversation and do not create a new one, so they won't trigger this Zap. If you need reply notifications, that requires a separate Zap with the 'New or Updated Conversation' trigger filtered to reply events.

What happens if Help Scout is down and the webhook doesn't fire?

Zapier does not retry missed webhook events — if Help Scout fails to send the event, the notification is lost. For critical teams, consider setting up Help Scout's built-in email notifications as a backup so nothing gets missed during outages.

Beginner~8 min setupCommunication & SupportVerified April 2026

How to Send Help Scout Tickets to Slack with Zapier

When a new conversation is created in Help Scout, Zapier instantly posts a formatted message to a Slack channel with the ticket subject, customer name, and a direct link.

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

Zapier

Also on:Make N8n Power-automate Pipedream

Best for

Support teams of 3–20 people who need real-time ticket visibility in Slack without building custom tooling

Not ideal for

Teams receiving 500+ tickets per day — at that volume, Zapier task costs add up fast and a native Help Scout Slack integration or Make handles it cheaper

Sync type

real-time

Use case type

notification

Real-World Example

💡

A 12-person e-commerce company routes all Help Scout conversations into #support-alerts in Slack so the on-call rep sees new tickets within 90 seconds of arrival. Before this Zap, the team relied on email notifications that buried urgent tickets in crowded inboxes — urgent issues sat unacknowledged for 20–40 minutes. After setup, median first-response time dropped from 38 minutes to under 8 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.

$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

Before You Start

Make sure you have everything ready.

Help Scout account with at least one active mailbox and conversations to test with

Help Scout user role of Manager or Administrator — Viewer accounts cannot authorize third-party OAuth connections

Slack workspace where you have permission to add apps and post to the target channel

Zapier account on any plan — this Zap uses 1 task per ticket, so the free tier (100 tasks/month) works for very low volume

The target Slack channel must already exist before you configure the Zap — Zapier cannot create channels

Field Mapping

Map these fields between your apps.

Field	API Name	Description
Required
Conversation Subject		The subject line of the Help Scout ticket — the primary identifier in the Slack notification that tells the team what the issue is about
Customer Name		Full name of the customer who opened the ticket — helps the team personalize their response immediately
Customer Email		The customer's email address — lets team members reply directly from Slack if needed
App URL		Direct link to the conversation in the Help Scout web interface — use this field, not 'URL', which outputs the API endpoint instead

4 optional fields▸ show

Conversation ID		Unique numeric ID for the ticket — useful for referencing in Slack threads or cross-checking with other tools
Mailbox Name		Which Help Scout mailbox received the ticket (e.g., Support, Billing) — helpful if you're routing all mailboxes into one Slack channel and need context
Status		The conversation status at creation — almost always 'active', but worth including to confirm the ticket is open and actionable
Created At		Timestamp of when the ticket was created — useful for SLA tracking visibility directly in Slack

Step-by-Step Setup

zapier.com > Dashboard > Create Zap

Create a new Zap

Log into Zapier at zapier.com and click the orange 'Create Zap' button in the top-left sidebar. You'll land on the Zap editor, which shows a two-panel layout: the step list on the left and the configuration panel on the right. The first block is labeled 'Trigger' and is already selected. This is where you define what event starts the automation.

1Go to zapier.com and sign in
2Click the orange 'Create Zap' button in the left sidebar
3Confirm the Zap editor opens with an empty Trigger block selected

✓ What you should see: You should see the Zap editor with a single gray 'Trigger' block and the app search panel open on the right side.

Zap Editor > Trigger > Choose App

Set Help Scout as the trigger app

In the right panel, type 'Help Scout' into the app search box. Select 'Help Scout' from the results — it shows a blue life-preserver icon. Zapier will then ask you to choose a trigger event. You want the event that fires when a brand-new conversation arrives, not when an existing one is updated.

1Type 'Help Scout' in the 'Search for an app' field
2Click the Help Scout result with the blue life-preserver icon
3Click the 'Trigger Event' dropdown
4Select 'New Conversation'

✓ What you should see: The trigger block should now show 'Help Scout — New Conversation' and prompt you to connect an account.

⚠

Common mistake — Help Scout also has a 'New or Updated Conversation' trigger. Do NOT pick that one — it fires on every reply, tag change, and assignment, which will flood your Slack channel within hours.

Zapier

click +

search apps

Slack

Set Help Scout as the trigge…

Slack

module added

Zap Editor > Trigger > Help Scout > Sign In

Connect your Help Scout account

Click 'Sign in to Help Scout'. A popup opens asking for your Help Scout credentials. Zapier uses OAuth, so you'll be redirected to Help Scout's own login page — you're not entering your password into Zapier directly. After logging in, Help Scout asks you to grant Zapier read access to your mailboxes and conversations. Approve it.

1Click 'Sign in to Help Scout'
2Log into Help Scout in the popup window
3Click 'Allow' on the Help Scout permissions screen
4Return to Zapier and confirm the account appears in the dropdown

✓ What you should see: You should see your Help Scout account email listed under 'Connected Account' with a green checkmark.

⚠

Common mistake — If you manage multiple Help Scout accounts (e.g., a sandbox and production), double-check the account email shown. Connecting the wrong account is the most common setup mistake here.

Zapier settings

Connection

Choose a connection…Add

click Add

Slack

Authorize Zapier

popup window

✓

Connected

green checkmark

Zap Editor > Trigger > Help Scout > Configure

Select the mailbox to monitor

After connecting your account, Zapier shows a 'Mailbox' dropdown. Help Scout can have multiple mailboxes (e.g., support@, sales@, billing@). Pick the specific mailbox you want to monitor, or leave it blank to watch all mailboxes. For most teams, selecting the primary support mailbox keeps Slack noise low.

1Click the 'Mailbox' dropdown
2Select the target mailbox from the list (e.g., 'Support')
3Leave 'Status' and 'Tag' filters blank unless you want to narrow the trigger further
4Click 'Continue'

✓ What you should see: The configuration panel shows your selected mailbox name and a 'Continue' button that is now active.

Zap Editor > Trigger > Test Trigger

Test the trigger

Click 'Test trigger'. Zapier pulls the 3 most recent conversations from your selected Help Scout mailbox as sample data. You'll see a list of real conversation records — click any one to expand it and review the fields Zapier found. Confirm you can see fields like Subject, Customer Name, Customer Email, and Conversation ID. These are what you'll map into the Slack message in the next steps.

1Click 'Test trigger'
2Wait 5–10 seconds for Zapier to fetch sample data
3Click on one of the returned conversation records to expand it
4Verify that 'Subject', 'Customer Name', 'Customer Email', and 'Conversation ID' fields are present

✓ What you should see: You should see at least one conversation record with populated fields. The subject line and customer email should match a real recent ticket in your Help Scout mailbox.

⚠

Common mistake — If your mailbox has zero conversations, Zapier returns no sample data and you can't proceed to map fields. Create one test conversation in Help Scout first, then re-run the test.

Zapier

▶ Turn on & test

executed

✓

Slack

✓

Help Scout

🔔 notification

received

Zap Editor > + Add Action > Slack > Send Channel Message

Add Slack as the action app

Click the '+' button below the trigger block to add an action step. Search for 'Slack' and select it. Then choose 'Send Channel Message' as the action event — this posts a message to a public or private channel. Do not choose 'Send Direct Message' unless you want to ping a specific person instead of a channel.

1Click the gray '+' button below the Help Scout trigger block
2Type 'Slack' in the app search field
3Select 'Slack' from the results
4Click the 'Action Event' dropdown and select 'Send Channel Message'
5Click 'Continue'

✓ What you should see: The action block now shows 'Slack — Send Channel Message' and prompts you to connect a Slack workspace.

Zap Editor > Action > Slack > Sign In

Connect your Slack workspace

Click 'Sign in to Slack'. A popup opens Slack's OAuth screen. Select the workspace you want to post to and click 'Allow'. Zapier requests permission to post messages as a bot user — the bot is named 'Zapier' by default and appears as the message sender in Slack. You cannot rename it from within Zapier.

1Click 'Sign in to Slack'
2Select your workspace from the dropdown in the popup
3Click 'Allow' to grant Zapier bot posting permissions
4Return to Zapier and confirm the workspace name appears under 'Connected Account'

✓ What you should see: Your Slack workspace name appears in the 'Connected Account' field with a green checkmark.

⚠

Common mistake — Zapier's Slack bot can only post to channels it has been invited to. If you target a private channel, you must manually invite the Zapier app to that channel in Slack before the Zap will work.

Zap Editor > Action > Slack > Configure

Configure the Slack message

This step is where you build the actual message your team will see. Set the 'Channel' field to the target channel (e.g., #support-alerts). In the 'Message Text' field, compose the notification using dynamic fields from the Help Scout trigger. A clear format includes the subject, customer name, email, and a direct link to the conversation. Slack supports basic formatting: use *bold* for emphasis and line breaks to separate fields.

1Click the 'Channel' dropdown and select your target Slack channel (e.g., #support-alerts)
2Click into the 'Message Text' field
3Type ':ticket: New Help Scout ticket:' then press Enter
4Click the '+' insert button and select 'Subject' from the Help Scout fields
5Add lines for Customer Name, Customer Email, and the conversation URL using the same insert method
6Set 'Bot Name' to something like 'Help Scout Bot' for clarity (optional)
7Click 'Continue'

✓ What you should see: The Message Text field shows a mix of static text and blue dynamic field chips, like ':ticket: New ticket: [Subject] from [Customer Name] ([Customer Email]) — [URL]'.

⚠

Common mistake — Help Scout's conversation URL field outputs the API URL (api.helpscout.net/...), not the web app URL (secure.helpscout.net/...). Map the 'App URL' field specifically, not 'URL', so the link opens in the browser interface.

Message template

📬 New entry: {{1.name}}
Email: {{1.email}}
Details: {{1.description}}

Zap Editor > Action > Slack > Test Action

Test the Slack action

Click 'Test action'. Zapier sends a real message to your selected Slack channel using the sample data from step 5. Open Slack and navigate to your target channel. Confirm the message appeared, check that all the dynamic fields populated correctly (no blank or undefined values), and verify the link to the Help Scout conversation works.

1Click 'Test action'
2Switch to Slack and open the target channel
3Find the test message posted by the Zapier bot
4Click the Help Scout conversation link and confirm it opens the correct ticket

✓ What you should see: A Slack message appears in your channel with the subject, customer name, email, and a working link — all populated with real data from your Help Scout sample conversation.

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 descriptive name — something like 'Help Scout → Slack: New Ticket Alert'. A clear name matters when you eventually have 20+ Zaps and need to debug one at 11pm. After publishing, the Zap status switches to 'On' and Zapier begins listening for new Help Scout conversations via webhook.

1Click the Zap name field at the top of the editor and type a descriptive name
2Click the 'Publish' button in the top-right corner
3Confirm the toggle switches to 'On' (shown in green)

✓ What you should see: The Zap editor shows a green 'On' status badge and the Zap appears in your Zapier dashboard under 'My Zaps'.

Zapier Dashboard > My Zaps > [Zap Name] > Zap History

Verify with a live ticket

Create a real test conversation in Help Scout by sending an email to your monitored mailbox from an external address. Wait up to 2 minutes. Check your Slack channel for the notification. If it doesn't appear within 3 minutes, go to your Zapier dashboard, click the Zap, and check the 'Zap History' tab for any failed runs or error messages.

1Send a test email to your Help Scout mailbox from an external email address
2Wait 1–2 minutes
3Check the target Slack channel for the notification
4If nothing appears, go to Zapier > My Zaps > click your Zap > click 'Zap History'
5Review any error entries and compare them against the troubleshooting section below

✓ What you should see: A Slack message appears within 2 minutes of the email landing in Help Scout, with the correct subject line, sender name, and a working link.

⚠

Common mistake — Zapier's Help Scout webhook can take 1–3 minutes to register a new conversation, not seconds. If you're testing and expecting instant delivery, wait the full 3 minutes before diagnosing a problem.

Going live

Production Checklist

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

Send a real test email to your Help Scout mailbox and confirm the Slack notification fires within 3 minutes

Verify the Slack channel in the Zap matches the intended production channel — not a test channel left over from setup

Confirm the Help Scout OAuth connection uses your production account, not a sandbox or personal account

If the target channel is private, invite the Zapier bot (/invite @Zapier) before going live

Check Zapier task usage against your plan limit — at 300 tickets/month you'll need the Starter plan (750 tasks included) or you'll hit the free tier ceiling

Turn on Zapier email notifications for Zap errors so you know immediately if the integration breaks

Document the Zap name and Zapier account owner internally — avoid single-owner setups where one person's account controls a team-critical automation

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 team is non-technical, needs to go live in under 15 minutes, and isn't handling more than 300–400 tickets per month. The Help Scout 'New Conversation' trigger works via webhook, so delivery is genuinely fast (under 2 minutes in practice). The Zap editor is clear enough that a support manager with no automation experience can configure this without help. If you're running multiple mailboxes, complex routing logic, or high ticket volume, switch to Make — it handles conditional routing across mailboxes more cleanly and costs less at scale.

Cost

On cost: this Zap consumes 1 task per ticket. At 200 tickets/month, you're at 200 tasks — within Zapier's free tier (100 tasks) for low-volume teams, or the Starter plan ($19.99/month for 750 tasks) for most support teams. At 500 tickets/month, you're looking at $19.99/month minimum. Make's free tier covers 1,000 operations/month and handles the same workflow for nothing. At 500 tickets/month, Make costs $0 versus Zapier's $19.99. At 2,000 tickets/month, Make's Core plan at $9/month still beats Zapier's Professional plan at $49/month.

Tradeoffs

Make handles conditional routing better — you can build a single scenario that branches by mailbox, tag, or customer domain using its visual router, rather than duplicating Zaps. n8n lets you self-host the whole thing for zero per-message cost, which matters at high volume, and its Help Scout node gives you direct access to the full conversation payload including thread history. Power Automate has a Help Scout connector, but it's a premium connector requiring a higher-tier license, making it the most expensive option here with no corresponding advantage. Pipedream lets you write JavaScript against Help Scout's API directly, which is useful if you need to pull additional data (like the first message body) before posting to Slack — something Zapier's trigger doesn't expose. Zapier is still the right call for teams that want zero maintenance and are under 400 tickets/month. Above that, the cost math points to Make or n8n.

Three things you'll hit after setup. First, Help Scout's 'URL' field outputs the API endpoint (api.helpscout.net/v2/conversations/...), not the web UI link. Anyone who clicks it from Slack gets a JSON response in their browser. Always use the 'App URL' field instead. Second, if a Help Scout admin rotates API credentials or revokes connected apps across the board (common after a security audit), your Zap silently stops firing — Zapier doesn't alert you until you notice no messages in Slack. Set up Zapier's error notification emails so you catch this. Third, tickets created via the Help Scout API (not email) sometimes arrive without a customer name — the name field is blank in Zapier's payload. If your product creates Help Scout tickets programmatically, test with an API-created ticket, not just an email, to confirm the notification still looks usable.

Ideas for what to build next

→
Route tickets by mailbox to different Slack channels — Add a Zapier Filter or Paths step to check the Mailbox Name field and post to #billing-alerts, #support-alerts, or #sales-alerts depending on where the ticket arrived. This keeps notifications relevant to the right sub-teams.
→
Add urgency detection with a keyword filter — Use Zapier's Filter step to check if the ticket subject contains words like 'urgent', 'broken', or 'down', then post those tickets to a separate high-priority channel or use Slack's @here mention to escalate immediately.
→
Log new tickets to a Google Sheet for SLA reporting — Add a second action step that appends each new Help Scout ticket to a Google Sheet row with the creation timestamp, customer email, and subject. After 30 days you have a real dataset for tracking ticket volume trends and first-response performance.