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

How to Send Help Scout Tickets to Slack with Make

When a new conversation is created in Help Scout, Make fires a webhook and posts a formatted message to a Slack channel with the ticket subject, customer email, 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 real-time ticket visibility in Slack without polling Help Scout manually every few minutes.

Not ideal for

Teams routing tickets to different Slack channels based on tag or mailbox — use Make's Router module or switch to n8n for cleaner conditional branching.

Sync type

real-time

Use case type

notification

Real-World Example

💡

A 12-person SaaS support team uses this to post every new Help Scout conversation into #support-queue the moment a customer emails in. Before this, the on-call engineer refreshed Help Scout manually and urgent tickets sat unacknowledged for 20–40 minutes. Now the Slack message includes the subject, customer email, and a one-click link to the conversation — response time dropped from 38 minutes average to 11.

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

Skip the setup

Import this workflow directly into Make

Copy the pre-built Make blueprint and paste it straight into Make. 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 Admin access — required to authorize the OAuth connection and register webhooks under Manage > Company > Webhooks
Make account — free tier works for under 500 tickets/month; Core plan ($9/month) for higher volume
Slack workspace with permission to install apps — if your workspace restricts app installs, you need a Slack Admin to approve Make before OAuth completes
Slack channel already created — the target channel (e.g., #support-queue) must exist before you configure the Slack module, or Make throws a channel-not-found error
Help Scout mailbox access — the account you connect must have read access to the mailbox you want to monitor; restricted agents only see their assigned conversations

Field Mapping

Map these fields between your apps.

FieldAPI Name
Required
Conversation Subjectsubject
Customer Emailcustomer.email
Ticket URL_links.web.href
6 optional fields▸ show
Conversation IDid
Mailbox NamemailboxId
Conversation Statusstatus
Created At TimestampcreatedAt
Customer Full Namecustomer.firstName
Assigned Agentassignee.email

Step-by-Step Setup

1

make.com > Scenarios > Create a new scenario

Create a new scenario in Make

Log into Make at make.com and click the blue 'Create a new scenario' button in the top-right corner of the Scenarios dashboard. You'll land on the visual canvas — a dark grid where modules appear as circles. Don't add anything yet. First, name the scenario by clicking the default name ('New scenario') at the top-left and typing something like 'Help Scout → Slack Ticket Alerts'. Naming it now saves confusion later when you have multiple scenarios.

  1. 1Log in at make.com
  2. 2Click 'Create a new scenario' (top-right, blue button)
  3. 3Click the default scenario name at the top-left
  4. 4Type a clear name like 'Help Scout → Slack Ticket Alerts'
  5. 5Press Enter to save the name
What you should see: You see an empty dark canvas with a single grey circle in the center and your new scenario name in the top-left.
Common mistake — Make autosaves scenario names but not module configs — if you close the tab mid-setup before saving, your module configuration is lost. Save manually with Cmd/Ctrl+S after each major step.
2

Canvas > + > Help Scout > Watch Conversations (Instant)

Add the Help Scout webhook trigger

Click the grey circle in the center of the canvas to open the module picker. Search for 'Help Scout' and select it from the results. Make will show you a list of Help Scout triggers — choose 'Watch Conversations (Instant)'. This is the webhook-based trigger, not the polling one. You'll know it's the right one because it has a lightning bolt icon next to the name. Instant triggers fire the moment Help Scout sends data; polling triggers check on a schedule and will introduce delay.

  1. 1Click the grey circle on the canvas
  2. 2Type 'Help Scout' in the search box
  3. 3Select 'Help Scout' from the app list
  4. 4Choose 'Watch Conversations (Instant)' — look for the lightning bolt icon
  5. 5Click 'Add' to open the connection dialog
What you should see: A Help Scout module appears on the canvas and a connection dialog opens asking you to connect your Help Scout account.
Common mistake — There are two Help Scout trigger options: 'Watch Conversations (Instant)' uses webhooks and fires in seconds. 'Watch Conversations' without the Instant label polls on a schedule. Pick the wrong one and your team waits up to 15 minutes per notification.
Make
+
click +
search apps
Slack
SL
Slack
Add the Help Scout webhook t…
Slack
SL
module added
3

Help Scout Module > Connection > Add > OAuth Authorization

Connect your Help Scout account

In the connection dialog, click 'Add' to create a new Help Scout connection. Make will redirect you to Help Scout's OAuth authorization page. Log in with your Help Scout credentials if prompted, then click 'Allow' to grant Make access. After authorization, you'll be returned to the Make canvas and the connection will appear with your Help Scout account name. Make stores this connection for reuse across other scenarios.

  1. 1Click 'Add' in the connection dropdown
  2. 2In the new dialog, click 'Save' — Make redirects to Help Scout OAuth
  3. 3Log into Help Scout if not already logged in
  4. 4Click 'Allow' on the Help Scout permissions screen
  5. 5Confirm you're returned to Make with your account name showing in the connection field
What you should see: The connection field shows your Help Scout account name (e.g., 'Acme Corp Help Scout') and a green checkmark. The module configuration panel is now fully visible.
Common mistake — You must be a Help Scout Admin to authorize the OAuth connection. Manager-level accounts will hit a permissions error during the 'Allow' step and the connection will fail silently — it just returns you to Make without connecting.
Make settings
Connection
Choose a connection…Add
click Add
Slack
Log in to authorize
Authorize Make
popup window
Connected
green checkmark
4

Help Scout Module > Event > Conversation Created

Configure the Help Scout trigger filter

With the connection set, configure the trigger settings. Set 'Event' to 'Conversation Created'. In the 'Mailbox' dropdown, you can either leave it set to 'All Mailboxes' or pick a specific one if you only want alerts for a particular inbox. Leave 'Status' as 'Any' for now — you can tighten this later. Click 'OK' to close the module. Make now needs to register a webhook URL with Help Scout, which happens in the next step.

  1. 1Set 'Event' to 'Conversation Created'
  2. 2Set 'Mailbox' to 'All Mailboxes' or choose a specific mailbox from the dropdown
  3. 3Leave 'Status' as 'Any'
  4. 4Click 'OK' to save the module configuration
What you should see: The Help Scout module on the canvas now shows 'Watch Conversations (Instant)' with a small clock icon, and no red error badge appears on it.
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

Help Scout > Manage > Company > Webhooks > New Webhook

Register the Make webhook in Help Scout

Make generates a unique webhook URL for this scenario, but Help Scout needs to know about it. Click 'Run once' at the bottom of the Make canvas — this puts the scenario in listening mode and shows you the webhook URL. Copy that URL. Now open Help Scout in a new browser tab, go to Manage > Company > Webhooks, click 'New Webhook', paste the URL, check the 'Conversation Created' event box, and save. Help Scout will immediately send a test ping to verify the URL is live.

  1. 1Click 'Run once' at the bottom of the Make canvas
  2. 2Copy the webhook URL shown in the Help Scout trigger module
  3. 3Open Help Scout in a new tab
  4. 4Navigate to Manage > Company > Webhooks
  5. 5Click 'New Webhook', paste the URL, check 'Conversation Created', click 'Save'
What you should see: Help Scout shows a green status dot next to the new webhook. Back in Make, the Help Scout trigger module should show a small data bubble if Help Scout sent a verification ping.
Common mistake — Help Scout webhooks require a publicly accessible URL. If you're testing locally with a tunnel like ngrok, the URL changes every session — you'll need to re-register the webhook each time. In production on Make's hosted infrastructure, this is not an issue.
6

Help Scout > New Conversation > Send > Make Canvas > Help Scout Module > Inspect Bundle

Send a test ticket to capture sample data

With Make still in 'Run once' mode and listening, go to Help Scout and manually create a test conversation in your chosen mailbox. Use a realistic subject like 'Login not working — urgent' and a real-looking customer email. Within 5–10 seconds, Make should capture the incoming data and show a green checkmark on the Help Scout trigger module. Click the module to inspect the captured bundle — you'll see fields like subject, customer email, conversation ID, status, and the direct URL to the ticket.

  1. 1Go to Help Scout and click 'New Conversation'
  2. 2Fill in a test subject and customer email
  3. 3Click 'Send' or 'Start Conversation'
  4. 4Switch back to Make — watch for a green checkmark on the trigger module
  5. 5Click the trigger module to open the bundle inspector and verify the data
What you should see: The trigger module shows '1 bundle' with a green checkmark. Clicking it reveals fields including subject, customer.email, id, and _links.web.href (the ticket URL).
Common mistake — If the bundle inspector shows the conversation ID but customer.email is empty, the test ticket was created without a customer email. Help Scout allows internal notes without a customer — always use an actual customer email in your test or the Slack message will have a blank email field.
Make
▶ Run once
executed
Slack
Help Scout
Help Scout
🔔 notification
received
7

Canvas > + > Slack > Create a Message

Add the Slack module

Click the small '+' icon to the right of the Help Scout module on the canvas to add the next module. Search for 'Slack' and select it. From the action list, choose 'Create a Message'. This is the action that posts to a Slack channel. Connect your Slack workspace by clicking 'Add' in the connection field — Make will redirect to Slack's OAuth page where you authorize access. Select the correct workspace if you belong to more than one.

  1. 1Click the '+' icon to the right of the Help Scout module
  2. 2Type 'Slack' in the search box and select it
  3. 3Choose 'Create a Message' from the action list
  4. 4Click 'Add' in the connection field
  5. 5Authorize Make on Slack's OAuth page and select your workspace
What you should see: The Slack module appears connected to the Help Scout module on the canvas, and the Slack connection field shows your workspace name (e.g., 'Acme Corp').
Common mistake — The Slack OAuth scopes Make requests include chat:write and channels:read. If your Slack workspace has restricted app installations (common in enterprise plans), you'll need a Slack Admin to approve the Make app before the connection completes.
8

Slack Module > Channel > Text > Map Variables

Map Help Scout fields to the Slack message

In the Slack module configuration, set the 'Channel' field to the Slack channel where alerts should appear — type the channel name or ID (e.g., #support-queue). In the 'Text' field, build your message using Make's variable picker. Click inside the Text field, then click the map icon (the small toggle) to switch to mapping mode. Use the variables from the Help Scout bundle to construct the message. A good starting message: ':ticket: New ticket from {{customer.email}} — *{{subject}}* — <{{_links.web.href}}|View in Help Scout>'. Keep it short — agents read this at a glance.

  1. 1Set 'Channel' to your target channel (e.g., #support-queue)
  2. 2Click inside the 'Text' field
  3. 3Toggle mapping mode on (small toggle icon to the right of the field)
  4. 4Type your message and use the variable picker to insert Help Scout fields
  5. 5Insert: subject, customer.email, and _links.web.href as a hyperlink
What you should see: The Text field shows a mix of static text and orange variable pills (e.g., an orange pill for 'subject', another for 'customer.email'). The message preview shows realistic values from your test bundle.
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}}
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

Canvas > Connection Line > Add Router > Filter > Slack Module (per path)

Add conditional routing for urgent tickets (optional but recommended)

If you want urgent tickets to post to a separate #support-urgent channel, add a Router module between Help Scout and Slack. Click the wrench icon on the connection line between the two modules and select 'Add a router'. This creates two paths. On Path 1, add a filter: set it to check if 'subject' contains 'urgent' (case-insensitive). On Path 2, set a fallback with no filter so all other tickets go to #support-queue. Duplicate the Slack module onto each path and set the channel differently per path.

  1. 1Right-click the arrow between Help Scout and Slack modules
  2. 2Select 'Add a router'
  3. 3Click the filter icon on Path 1 and set: subject > Contains (case insensitive) > 'urgent'
  4. 4On Path 1, add a Slack module pointed at #support-urgent
  5. 5On Path 2 (no filter), keep the Slack module pointed at #support-queue
What you should see: The canvas shows the Help Scout module connecting to a router circle, which fans out into two paths — each ending in a Slack module with different channel settings.
Common mistake — Router paths are evaluated top-to-bottom. If you accidentally set a filter on the fallback path, some tickets will match no path and be silently dropped. Always leave one path with no filter as the catch-all.
10

Canvas > Run once > Inspect each module > Slack Channel

Test the full scenario end-to-end

Click 'Run once' on the Make canvas again. Create another test conversation in Help Scout with a realistic subject. Watch the Make canvas — each module should light up green as data flows through. Click each module after the run to inspect what data passed through it. Check your Slack channel to confirm the message arrived with the correct subject, email, and a working link to the Help Scout ticket. If the link is clickable and opens the right conversation, the setup is complete.

  1. 1Click 'Run once' at the bottom of the Make canvas
  2. 2Create a new test conversation in Help Scout
  3. 3Watch the Make canvas for green checkmarks on each module
  4. 4Click each module to confirm data mapped correctly
  5. 5Open Slack and verify the message appeared in the correct channel with a working link
What you should see: All modules show green checkmarks. The Slack message in #support-queue reads something like ':ticket: New ticket from [email protected] — *Login not working — urgent* — View in Help Scout' with a working link.
11

Canvas > Scenario toggle (bottom-left) > On

Activate the scenario

Once the end-to-end test passes, click the toggle at the bottom-left of the canvas to switch the scenario from 'Off' to 'On'. The toggle turns blue. From this point, every new Help Scout conversation will trigger the scenario automatically without you clicking 'Run once'. Set the scheduling to 'Immediately' — this is the default for instant/webhook scenarios and means Make processes each incoming webhook as it arrives, not in batches.

  1. 1Click the grey toggle at the bottom-left of the canvas
  2. 2Confirm it turns blue (active)
  3. 3Verify the scenario status shows 'Active' in the Scenarios list
  4. 4Check that scheduling is set to 'Immediately' in scenario settings
What you should see: The scenario toggle is blue and the Scenarios dashboard shows this scenario with a green 'Active' status badge. The 'Last run' column will update the next time a Help Scout ticket arrives.
Common mistake — Make free plans cap at 1,000 operations per month. Each scenario run uses 2 operations (one per module). At 500 tickets/month, you hit the free limit exactly — 501 tickets and notifications stop silently. Set up a Make email alert under Account > Notifications to warn you before you hit the cap.

Paste this formula into the Make Slack module's 'Text' field using the formula editor (click the 'f(x)' icon in the field). It formats the createdAt timestamp into a readable time, adds a priority label based on subject keywords, and gracefully handles missing customer names — all in one expression without adding extra modules.

JavaScript — Custom Functionif(
▸ Show code
if(
  contains(lower(subject); "urgent") or contains(lower(subject); "down") or contains(lower(subject); "broken");
  ":rotating_light: *URGENT* — ";

... expand to see full code

if(
  contains(lower(subject); "urgent") or contains(lower(subject); "down") or contains(lower(subject); "broken");
  ":rotating_light: *URGENT* — ";
  ":ticket: New ticket — "
)
& if(
  customer.firstName != null;
  customer.firstName & " (" & customer.email & ")";
  ifempty(customer.email; "Unknown customer")
)
& " submitted: *" & subject & "*"
& "\nReceived: " & formatDate(createdAt; "MMM D, YYYY [at] h:mm A"; "America/New_York")
& "\n<" & _links.web.href & "|Open ticket #" & id & " in Help Scout>"

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 Make for this workflow

Use Make for this if your team wants a visual map of exactly what happens to each ticket notification — the canvas shows the Help Scout trigger, any routing logic, and the Slack output in one view, which makes debugging fast. Make also handles the webhook registration more cleanly than Zapier for Help Scout: you get an instant trigger with no polling delay, and the built-in Router module handles priority routing (urgent vs. normal channels) without needing a separate Zap. The one scenario where you'd skip Make: if your team already runs everything in n8n self-hosted and owns the infrastructure — the operational overhead of one more SaaS tool isn't worth it.

Cost

The math on cost is straightforward. Each scenario run uses 2 Make operations — one for the Help Scout trigger, one for the Slack message. Make's free tier gives you 1,000 operations per month, which covers exactly 500 tickets. At 501 tickets, the scenario stops and nobody in Slack gets notified until next month. The Core plan at $9/month gives you 10,000 operations — that's 5,000 tickets/month — which covers most small support teams comfortably. Zapier's equivalent (Multi-Step Zaps) requires the Starter plan at $19.99/month minimum. Make is cheaper by $10.99/month for the same workflow at this volume.

Tradeoffs

Zapier has one real edge here: setup speed. If you've never used either tool, Zapier's step-by-step guided setup gets you from zero to live notification in about 6 minutes versus Make's 12–15 minute canvas-based approach. n8n is better if you need complex conditional logic — its Code node lets you write actual JavaScript to classify tickets by subject keywords, something that requires chaining multiple Make modules. Power Automate is the right call if your team is already in Microsoft 365 and wants ticket alerts in Teams instead of Slack — its Help Scout connector is weaker but the Teams integration is first-class. Pipedream wins on custom API calls: if you need to fetch additional Help Scout data (like full conversation history) before posting to Slack, Pipedream's async/await code steps handle that without extra modules. Make is still the right pick here because the scenario is straightforward — one trigger, one action, optional routing — and Make's visual canvas makes it easier to hand off to a non-developer on your team.

Three things you'll run into after go-live. First: Help Scout's webhook payload doesn't include the full customer profile — you get customer.email and customer.firstName but not the customer's company name. If you want company in the Slack message, you need a second Make module calling Help Scout's customer API using the customer ID, which doubles your operation count per run. Second: Slack's message formatting doesn't support HTML — the _links.web.href field needs to be formatted as Slack's mrkdwn link syntax (<URL|label text>), not a standard HTML anchor tag. Paste a raw URL and it appears as an unformatted string. Third: Make's free plan pauses inactive scenarios after 30 days with no data. If your team has a slow month — say, a holiday week with no tickets — the scenario goes dormant and new tickets in January arrive silently. Set a calendar reminder to check the scenario status or upgrade to a paid plan to disable the inactivity pause.

Ideas for what to build next

  • Add a Slack thread reply when a ticket is resolvedBuild a second Make scenario triggered by Help Scout's 'Conversation Status Changed' event. When status moves to 'closed', post a threaded reply on the original Slack notification using the conversation ID to match the message. Your team gets a complete open-to-close timeline inside Slack.
  • Route tickets by mailbox to separate Slack channelsAdd a Router module after the Help Scout trigger with filters on the mailboxId field. Route billing tickets to #billing-support and technical tickets to #tech-support. This keeps each team's channel clean without creating multiple scenarios.
  • Send a daily digest instead of per-ticket alertsBuild a parallel Make scenario on a scheduled trigger (every day at 9am) that pulls open Help Scout conversations via the 'Search Conversations' module and posts a numbered list to Slack. Useful for managers who want a summary without live interruptions.

Related guides

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