

How to Send Help Scout Ticket Assignments to Slack with Zapier
When a Help Scout conversation is assigned to a team member, Zapier posts a Slack message directly to that person so they see the ticket immediately.
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 5–30 agents who live in Slack and need instant visibility into new ticket assignments without checking Help Scout manually.
Not ideal for
Teams with 500+ daily assignments — at that volume the per-task cost adds up fast and Make handles the same logic for free.
Sync type
real-timeUse case type
notificationReal-World Example
A 12-person support team at a B2B SaaS company routes tickets by product area. Before automation, agents refreshed Help Scout every 20–30 minutes to check for new assignments and tickets sat unacknowledged for up to an hour during busy periods. After setting up this Zap, each agent gets a direct Slack message within 5 minutes of assignment, including the customer name, subject line, and a direct link to the conversation.
What Will This Cost?
Drag the slider to your expected monthly volume.
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.
Field Mapping
Map these fields between your apps.
| Field | API Name | |
|---|---|---|
| Required | ||
| Assignee Email | ||
| Conversation Subject | ||
| Conversation URL | ||
7 optional fields▸ show
| Assignee Name | |
| Customer Name | |
| Customer Email | |
| Mailbox Name | |
| Conversation Number | |
| Status | |
| Created At |
Step-by-Step Setup
zapier.com > Dashboard > Create Zap
Create a new Zap and name it
Log in to zapier.com and click the orange 'Create Zap' button in the left sidebar. Give the Zap a name at the top — something like 'Help Scout Assignment → Slack DM' so it's easy to find later. You'll land on the trigger setup screen, which shows a search bar for apps. Naming it now saves confusion when you have multiple Help Scout Zaps running.
- 1Click 'Create Zap' in the left sidebar
- 2Click the untitled Zap name at the top and type a descriptive name
- 3Click the 'Trigger' step box to begin app selection
Zap Editor > Trigger > App & Event
Select Help Scout as the trigger app
In the trigger search bar, type 'Help Scout' and select it from the dropdown. You'll see a list of available triggers on the right panel. Select 'Conversation Assigned' as the trigger event — this fires whenever a conversation is assigned or reassigned to any agent. Do not choose 'New Conversation' — that triggers on creation, not assignment.
- 1Type 'Help Scout' in the 'Search for apps' field
- 2Click 'Help Scout' in the results list
- 3Click the 'Trigger Event' dropdown
- 4Select 'Conversation Assigned'
- 5Click 'Continue'
Zap Editor > Trigger > Account
Connect your Help Scout account
Click 'Sign in to Help Scout' and a popup window will appear asking you to authorize Zapier. Log in with your Help Scout credentials if prompted, then click 'Allow'. You need to be a Help Scout Admin to grant this OAuth access — Manager-level accounts may not have permission to connect third-party apps. Once authorized, select the connected account from the dropdown and click Continue.
- 1Click 'Sign in to Help Scout'
- 2Log in to Help Scout in the popup window
- 3Click 'Allow' to grant Zapier access
- 4Select your authorized account from the dropdown
- 5Click 'Continue'
Zap Editor > Trigger > Configure
Configure the trigger mailbox
Zapier will show a 'Mailbox' field where you can optionally filter by a specific Help Scout mailbox. If your team uses multiple mailboxes (e.g., support@, billing@), select the relevant one here. Leave it blank to fire on assignments across all mailboxes. Click 'Continue' when done, then click 'Test trigger' to pull a real sample assignment.
- 1Click the 'Mailbox' dropdown
- 2Select a specific mailbox or leave blank for all mailboxes
- 3Click 'Continue'
- 4Click 'Test trigger' to load sample data
Zap Editor > Action > App & Event
Add a Slack action step
Click the '+' button below the trigger step to add an action. Search for 'Slack' and select it. For the action event, choose 'Send Direct Message' to notify the specific assignee, or 'Send Channel Message' if you want all assignments posted to a shared support channel. Direct message is usually better for accountability — the assigned agent gets a personal ping, not just a channel post they might miss.
- 1Click the '+' button below the trigger step
- 2Type 'Slack' in the search bar
- 3Click 'Slack' in the results
- 4Click the 'Action Event' dropdown
- 5Select 'Send Direct Message' or 'Send Channel Message'
- 6Click 'Continue'
Zap Editor > Action > Account
Connect your Slack workspace
Click 'Sign in to Slack' and authorize Zapier in the popup. You'll need to be a Slack workspace member with permission to send messages — standard member access is enough here, you don't need admin rights. Select the workspace from the dropdown, click Allow, and confirm the connected account appears in the Zapier panel.
- 1Click 'Sign in to Slack'
- 2Select your workspace in the Slack authorization popup
- 3Click 'Allow'
- 4Select the authorized Slack account in the dropdown
- 5Click 'Continue'
Zap Editor > Action > Configure
Map the recipient and message fields
In the 'To Username' field, map the Help Scout trigger field 'Assignee Email' — Slack will look up the user by email and send the DM to that person. In the 'Message Text' field, build your notification using the dynamic fields from the trigger. Include the ticket subject, customer name, and the conversation URL so the agent has everything they need without opening Help Scout. Keep the message under 280 characters so it renders cleanly in Slack's notification preview.
- 1Click the 'To Username' field and select 'Assignee Email' from the Help Scout trigger data
- 2Click the 'Message Text' field
- 3Type your message and insert dynamic fields: Subject, Customer Name, Conversation URL
- 4Optionally set 'Send as a Bot' to Yes and give the bot a name like 'Help Scout'
- 5Click 'Continue'
📬 New entry: {{1.name}}
Email: {{1.email}}
Details: {{1.description}}Zap Editor > + (between steps) > Filter by Zapier
Add a Filter step to avoid re-assignment noise (optional but recommended)
Click '+' between the trigger and action steps to insert a Filter. Set the filter to 'Only continue if Assignee Email is not empty.' This prevents the Zap from firing when a ticket is unassigned (which Help Scout also logs as an assignment event with a blank assignee). Without this filter, you'll get Slack errors every time someone removes an assignee from a ticket.
- 1Click the '+' icon between the trigger and action steps
- 2Select 'Filter by Zapier'
- 3Set Field to 'Assignee Email'
- 4Set Condition to 'Exists' or '(Text) is not exactly' with a blank value
- 5Click 'Continue'
Zap Editor > Action > Test
Test the full Zap
Click 'Test action' on the Slack step. Zapier will send a real Slack DM to the assignee email from your sample data — make sure that email belongs to a real Slack user in your workspace before testing, or the message will fail. Check Slack to confirm the message arrived with the correct subject, customer name, and link. If the test succeeds, you'll see a green 'Test was successful' banner in Zapier.
- 1Click 'Test action'
- 2Open Slack and check the DMs for the test user
- 3Confirm the message text, link, and sender name look correct
- 4Return to Zapier and verify the green success banner
Zap Editor > Publish Zap > Toggle On
Turn the Zap on
Click 'Publish Zap' in the top right corner. Toggle the Zap to 'On' if it isn't already. Zapier will now poll Help Scout every 1–15 minutes (every 1–2 minutes on paid plans, up to 15 minutes on free) for new assignment events. The Zap will run automatically from this point — no further action needed.
- 1Click 'Publish Zap' in the top right
- 2Confirm the toggle is set to 'On' (shown in blue)
- 3Note the polling interval shown on the Zap dashboard
This Code by Zapier step runs between the Help Scout trigger and the Slack action. It formats a clean, consistent message string and flags tickets that are older than 2 hours at the time of assignment — so agents know immediately if they've inherited a stale ticket. Paste this into a 'Code by Zapier' step (Run JavaScript) and map the output 'message' field into your Slack message text field instead of building it manually in the Slack step.
JavaScript — Code Stepconst subject = inputData.subject || 'No subject';▸ Show code
const subject = inputData.subject || 'No subject'; const customerName = inputData.customer_name || 'Unknown customer'; const customerEmail = inputData.customer_email || '';
... expand to see full code
const subject = inputData.subject || 'No subject';
const customerName = inputData.customer_name || 'Unknown customer';
const customerEmail = inputData.customer_email || '';
const conversationUrl = inputData.conversation_url || '';
const assigneeName = inputData.assignee_name || 'You';
const createdAt = inputData.created_at ? new Date(inputData.created_at) : null;
let ageWarning = '';
if (createdAt) {
const ageMs = Date.now() - createdAt.getTime();
const ageHours = ageMs / (1000 * 60 * 60);
if (ageHours > 2) {
const ageDisplay = ageHours >= 24
? `${Math.floor(ageHours / 24)}d ${Math.floor(ageHours % 24)}h`
: `${Math.floor(ageHours)}h ${Math.floor((ageHours % 1) * 60)}m`;
ageWarning = ` ⚠️ This ticket is ${ageDisplay} old.`;
}
}
const customerLine = customerEmail
? `${customerName} (${customerEmail})`
: customerName;
const message = `📬 New ticket assigned to you, ${assigneeName}: *${subject}* — from ${customerLine}.${ageWarning}\nOpen it here: ${conversationUrl}`;
output = [{ message }];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
Use Zapier for this if your support team is small (under 50 agents), non-technical, and needs this running in under 30 minutes without writing any code. The Zap builder's guided steps make the Help Scout trigger and Slack action obvious to anyone who can use a web form. You also get built-in error history and reconnect flows that save time when credentials expire. The one scenario where you'd skip Zapier: if your team needs real-time delivery under 60 seconds, Help Scout's native webhooks push events instantly, and pairing them with Make or n8n gives you that speed without the polling delay.
The cost math is straightforward. Each ticket assignment = 1 Zapier task (2 tasks if you add the Filter step, since filters consume a task when they stop a run). A team closing 200 tickets per month with a 70% assignment rate burns through roughly 140–280 tasks per month. The Zapier free plan covers 100 tasks — you'll exceed that within the first week. Starter at $19.99/month gives you 2,000 tasks, which covers most teams comfortably. Make's free tier handles 1,000 operations per month, meaning the same 280-task workflow runs free on Make — saving you $240/year for an identical outcome.
Make fires this same workflow with real-time webhooks instead of polling, meaning assignments hit Slack in under 10 seconds instead of up to 15 minutes. n8n self-hosted runs this for free at any volume with full webhook support, and you can add conditional logic (like routing enterprise tickets differently) without paying per task. Power Automate has a Help Scout connector, but it's a premium connector requiring a $15/user/month Power Automate per-user plan — expensive for a simple notification. Pipedream's free tier supports HTTP triggers and the Slack SDK natively, which gives you more message formatting control than Zapier's Slack action allows. That said, Zapier wins here on pure setup speed and maintainability for non-technical team leads who need to own this Zap long-term without help from engineering.
Three things you'll hit after setup. First, Slack email mismatches break DMs silently — Zapier logs a failure but doesn't retry or alert the intended recipient, so tickets go unnoticed. Audit your email list before day one. Second, Help Scout counts unassignment events as assignment events with a blank assignee field. Without the filter step, you'll burn tasks on every ticket removal and see Slack errors in your history daily. Third, if your Help Scout mailbox is shared with another integration (like a CRM or reporting tool) that's also polling the API, you may hit Help Scout's rate limits (600 requests per minute per account). This surfaces as intermittent 'Held' runs in Zapier history — the fix is to stagger polling intervals across your connected tools.
Ideas for what to build next
- →Post assignments to a shared #support-queue channel — Add a second Slack action step that posts to a team channel in addition to the DM. This gives team leads visibility into assignment volume in real time without needing to check Help Scout's inbox.
- →Escalate tickets that go unacknowledged for 30 minutes — Build a second Zap that monitors Help Scout for tickets that are assigned but still open after 30 minutes, then pings the team lead in Slack. This catches situations where an agent missed or dismissed the original DM.
- →Add a Slack reminder for tickets nearing SLA breach — Combine this workflow with Help Scout's tag or status fields to trigger a follow-up Slack message when a ticket is approaching your SLA window — for example, any ticket still open 4 hours after assignment.
Related guides
How to Share Notion Meeting Notes to Slack with Pipedream
~15 min setup
How to Share Notion Meeting Notes to Slack with Power Automate
~15 min setup
How to Share Notion Meeting Notes to Slack with n8n
~20 min setup
How to Send Notion Meeting Notes to Slack with Zapier
~8 min setup
How to Share Notion Meeting Notes to Slack with Make
~12 min setup
How to Create Notion Tasks from Slack with Pipedream
~15 min setup