Resources · n8n integration

Help Scout n8n integrationAutomate Help Scout with n8n.

Every reply that lands in Help Scout can start a workflow. The Help Scout n8n integration ships a node with 13 operations spread over 4 resources, conversations, customers, mailboxes and threads, plus a trigger that listens to 12 events. For support teams still copying tickets by hand.

Try the Help Scout integration on n8nSee the 13 operations

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the Help Scout n8n integration actually give you?

Two nodes, both shipped inside n8n. The Help Scout node calls the Mailbox API on your behalf: 13 operations spread over 4 resources, so a workflow can open a conversation, add a thread to it, read or update a customer record, and list mailboxes. The Help Scout Trigger does the opposite job. It starts a workflow the moment Help Scout fires one of its 12 events.

Start with the noisiest part of a support inbox: reporting. A workflow that begins on convo.created and writes one row per ticket into Google Sheets gives the team a live backlog without anyone touching a spreadsheet. Same trigger, different ending: push the subject and the mailbox into Slack so the channel sees new tickets before anyone opens Help Scout.

Second pattern: escalation on feedback. The satisfaction.ratings event fires when a rating comes back, and a rating is the one signal nobody wants to read a day late. Route it to a channel, or chain it into conversation.get to pull the full conversation before the alert goes out, so the person reading it has the subject and the status in front of them.

Third pattern runs the other way, from another system into Help Scout. A form submission, a billing failure, a row flagged in a sheet: the workflow calls conversation.create with a mailbox, a subject, a status and a type, then thread.create to add the message body. The ticket exists in the right mailbox with the right content, and the agent who picks it up sees a normal conversation. Pair it with Gmail when the source is a mailbox n8n already watches.

Some of what you want will sit outside the 13 operations in the catalogue. That case has a standard answer in n8n: the HTTP Request node calls any endpoint of the Help Scout API and reuses the same credential through predefined authentication, so you stay on one connection instead of managing a second one.

Two things to plan for. Reads that return lists, conversations, customers, mailboxes and threads, are paginated: Return All walks every page of the API, while leaving it off caps the run at Limit. And the 12 events are not evenly spread. Group them and the shape is clear: 10 belong to the convo family, 1 to customer, 1 to satisfaction. Three families, 12 events, so almost every trigger you build starts on a conversation. If you want the wider comparison before committing, the n8n review covers it, and the n8n training walks through building these workflows.

Connect

How do you connect Help Scout to n8n?

  1. 01

    Create a Help Scout app

    The credential supports one authentication method: OAuth2, the flow where Help Scout hands n8n a token instead of you pasting a password anywhere. You need a Help Scout account first, then an app created on the Help Scout side following their OAuth documentation. That app is what identifies n8n when the token is issued, and it is the only piece of setup that happens outside n8n.

  2. 02

    Save the credential once in n8n

    In n8n, open the Credentials menu and create a Help Scout credential, meaning the stored connection n8n reuses instead of asking you to authenticate in every node. Complete the OAuth2 flow there. One credential covers both the Help Scout node and the Help Scout Trigger, so a workflow that listens and a workflow that writes run off the same connection.

  3. 03

    Pick a resource and run one operation

    Drop the Help Scout node on the canvas, select the credential from the dropdown, then pick a resource and an operation. mailbox.getAll is the cheapest first test: it returns your mailboxes and proves the token works. Keep the mailbox identifier it gives you, since conversation.create asks for Mailbox Name or ID and the node can also offer it in a list.

Triggers

What starts a Help Scout workflow?

Help Scout Trigger is the node that starts a workflow when something happens in Help Scout. It listens to 12 events, listed below by family. Pick one or several, activate the workflow: n8n registers the webhook on your Help Scout account.

What you see in n8n

Every event, by family

One row per object, one chip per action. The event to tick in the node is object.action; hover a chip to read exactly when it fires.

convo.*10
  • convo.
    • assigned
    • created
    • deleted
    • merged
    • moved
    • status
    • tags
  • convo.agent.reply.
    • created
  • convo.customer.reply.
    • created
  • convo.note.
    • created
customer.*1
  • customer.
    • created
satisfaction.*1
  • satisfaction.
    • ratings

Configuration notes

01Set up the Help Scout TriggerThe trigger is a webhook listener, meaning Help Scout calls an n8n URL the moment something happens rather than n8n asking every few minutes. n8n registers that URL with Help Scout when you activate the workflow, and each event arrives within seconds. No polling, no interval to tune.

The trigger is a webhook listener, meaning Help Scout calls an n8n URL the moment something happens rather than n8n asking every few minutes. n8n registers that URL with Help Scout when you activate the workflow, and each event arrives within seconds. No polling, no interval to tune.

Key parameters

  • Events: the list of event types this trigger listens to. Twelve are available, and you tick the ones you want. Leaving too many ticked means one workflow handling unrelated payloads, so a branch per concern usually stays easier to read.
When to use it
any time the starting point is something a human did inside Help Scout. An agent replied, a customer rated the exchange, a ticket changed hands. Trigger node version 1.
02Conversation lifecycle eventsSeven of the ten convo events track what happens to a ticket itself rather than what is written in it. convo.created fires on a new conversation, convo.assigned when it lands on someone, convo.status on a status change, convo.moved when it changes mailbox, convo.tags on tagging, convo.merged when two tickets become one, and convo.deleted on removal.

Seven of the ten convo events track what happens to a ticket itself rather than what is written in it. convo.created fires on a new conversation, convo.assigned when it lands on someone, convo.status on a status change, convo.moved when it changes mailbox, convo.tags on tagging, convo.merged when two tickets become one, and convo.deleted on removal.

Use cases
assignment and status are the two that carry most of the reporting value. Start on convo.assigned to log who took what, or on convo.status to measure how long tickets sit before they close. Tick convo.moved alongside if your team routes between several mailboxes and you want to see where the traffic actually goes. None of these seven events carries the message text itself, only the change to the ticket record, so pair one with conversation.get when the note or reply also matters.
03Reply and note eventsThe remaining three convo events fire on content added to a conversation. convo.customer.reply.created fires when the customer writes back, convo.agent.reply.created when an agent answers, and convo.note.created when someone adds an internal note. Splitting them matters: a customer reply and an agent reply mean opposite things for a follow-up rule.

The remaining three convo events fire on content added to a conversation. convo.customer.reply.created fires when the customer writes back, convo.agent.reply.created when an agent answers, and convo.note.created when someone adds an internal note. Splitting them matters: a customer reply and an agent reply mean opposite things for a follow-up rule.

Use cases
a reply from a customer on a ticket already marked closed is the classic reopen case, and catching it lets the workflow notify the owner before the message goes unread. On the internal side, convo.note.created feeds a channel where a mention in a note pulls a colleague in without anyone leaving Help Scout. None of the three tells you the ticket status on its own, so a workflow that also needs the status chains conversation.get right after the trigger.
04Customer and satisfaction eventsThe last two events sit in their own families. customer.created belongs to the customer family and fires when a new customer record appears. satisfaction.ratings is the whole satisfaction family on its own and fires when a rating comes in. Add the ten conversation events and you get the full count: 10 plus 1 plus 1, 12 events across 3 families.

The last two events sit in their own families. customer.created belongs to the customer family and fires when a new customer record appears. satisfaction.ratings is the whole satisfaction family on its own and fires when a rating comes in. Add the ten conversation events and you get the full count: 10 plus 1 plus 1, 12 events across 3 families.

Use cases
customer.created is the hook for onboarding, since the record exists before anyone has enriched it. Chain customer.update behind it to fill in what another system already knows. satisfaction.ratings feeds the weekly quality review, and routing it to a channel puts feedback in front of the team the day it arrives. Neither event shares fields with the ten conversation events, so a workflow branching on the family needs its own mapping from the payload.
Actions

The 13 operations, one by one

The Help Scout node exposes 13 operations across 4 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.

Resources × operations matrix
ResourceCreateGetGet ManyUpdateDeleteProperties
Conversation✓✓✓✓
Customer✓✓✓✓✓
Mailbox✓✓
Thread✓✓

Conversation

4 operations
01

Create a conversation

conversation.create

What you see in n8n

Notes & use cases

Opens a new conversation in a mailbox and returns the conversation created, which is how an event happening elsewhere becomes a ticket an agent can work on.

Key parameters

  • Mailbox Name or ID: the mailbox the conversation is created in. Pick it from the list, or pass an ID with an expression such as {{ $json.field }}.
  • Status: active, closed or pending.
  • Subject: the conversation subject, the line agents scan in the queue.
  • Type: chat, email or phone.
  • Resolve Data: off, the response only carries the ID of the resource; on, n8n resolves the data automatically.
Use cases
a failed payment turns into an email ticket in pending status inside the billing mailbox, subject built from the invoice reference.
02

Delete a conversation

conversation.delete

What you see in n8n

Notes & use cases

Removes a conversation from Help Scout. There is no confirmation step inside the node, so whatever reaches this operation is gone from the mailbox.

Key parameters

  • Conversation ID: the conversation to remove, typically carried over from an earlier node with {{ $json.field }}.
Use cases
spam cleanup. A workflow that reads a mailbox, scores subjects and deletes only what matches a strict rule keeps the queue readable. Put an IF node in front of it and test the branch on a throwaway conversation before you activate anything.
03

Get a conversation

conversation.get

What you see in n8n

Notes & use cases

Fetches one conversation by its identifier, so a workflow that only knows an ID can work with the full record.

Key parameters

  • Conversation ID: the identifier of the conversation to read, often taken from the trigger payload with {{ $json.field }}.
Use cases
enrichment between a trigger and an alert. A workflow that starts on a rating or a status change holds an identifier and little else, and this operation fills the gap before the message is sent, so the notification carries real context rather than a bare ID.
04

Get many conversations

conversation.getAll

What you see in n8n

Notes & use cases

Lists conversations and is where reporting workflows start, because the filters do the narrowing before any data reaches n8n.

Key parameters

  • Return All: on, n8n walks every page of results; off, it stops at Limit.
  • Modified Since: returns only conversations modified after this date, the usual guard for a scheduled run.
  • Status: active, all, closed, open, pending or spam.
  • Mailbox ID: restricts the list to one mailbox.
  • Embed: set to threads to load sub-entities with the conversation.
Use cases
a nightly export of everything modified since yesterday, filtered on one mailbox.

Customer

5 operations
05

Create a customer

customer.create

What you see in n8n

Notes & use cases

Adds a customer record to Help Scout. No field is required, so the shape of the record is entirely yours to decide.

Key parameters

  • Emails: a collection where each entry adds an email to the record.
  • First Name: when set, it must be between 1 and 40 characters.
  • Job Title: 60 characters maximum.
  • Organization: the company the contact belongs to.
  • Phones, Websites, Social Profiles, Chat Handles, Address: one collection each, added entry by entry.
Use cases
a signup pushes name, email and company into Help Scout, so the first ticket already arrives attached to a known contact.
06

Get a customer

customer.get

What you see in n8n

Notes & use cases

Reads a single customer record and hands it to the rest of the workflow.

Key parameters

  • Customer ID: the identifier of the record to read, usually inherited from a previous node as {{ $json.field }}.
Use cases
deduplication before a write. A workflow that is about to create something reads the existing record first and branches on what it finds, which keeps a customer from ending up twice in the account. It also works as a lookup step when an alert needs the contact details behind an identifier.
07

Get many customers

customer.getAll

What you see in n8n

Notes & use cases

Returns a list of customers, with filters applied by the API rather than by a filter node further down the workflow.

Key parameters

  • Return All: on, every page of customers comes back; off, the run stops at Limit.
  • Query: advanced search, for anything the plain filters do not express.
  • Mailbox ID: keeps only customers from one mailbox.
  • Sort Field and Sort Order: order the result, for example modifiedAt with desc.
Use cases
a monthly sync that pulls customers modified since the last run and updates a CRM in the same workflow.
08

Get customer properties

customer.properties

What you see in n8n

Notes & use cases

Returns the customer property definitions from the account, meaning the custom fields an admin configured in Help Scout rather than the values stored on one contact. It takes no parameters at all, so you drop it in and run it.

Use cases
the discovery step before a sync project. Run it once, read what comes back, and you know which properties exist before mapping anything from another tool. It also works as a safety check in a long-lived workflow, where a property renamed in Help Scout would otherwise break a mapping silently.
09

Update a customer

customer.update

What you see in n8n

Notes & use cases

Edits an existing customer record. Only the fields you fill in the collection are sent, so a workflow can touch one attribute without rewriting the contact.

Key parameters

  • Customer ID: the record to edit, commonly passed as {{ $json.field }} from the node before.
  • Organization, Job Title, Location: the attributes most often refreshed from another system.
  • Notes: free background text on the contact.
  • Photo Url: the URL of the customer photo.
Use cases
a job change detected in the CRM updates the title and organization in Help Scout the same day.

Mailbox

2 operations
10

Get a mailbox

mailbox.get

What you see in n8n

Notes & use cases

Returns the data of one mailbox, which is what you need when a workflow has an identifier and has to describe the mailbox in something a person will read.

Key parameters

  • Mailbox ID: the mailbox to read, entered directly or built with an expression.
Use cases
alerting across several inboxes. A convo.moved event tells you a ticket changed mailbox, and this operation turns the identifier in the payload into something readable before the notification goes out to the team.
11

Get many mailboxes

mailbox.getAll

What you see in n8n

Notes & use cases

Lists the mailboxes on the account. It is the simplest operation in the node, which makes it the natural first run after saving a credential.

Key parameters

  • Return All: on, every mailbox comes back; off, the node stops at Limit.
Use cases
collecting the identifiers a build needs. Most other operations ask for a mailbox, and this is where those values come from. The n8n template library has a ready-made workflow for exactly this, Get all mailboxes from Help Scout, published as workflow 567.

Thread

2 operations
12

Create a thread

thread.create

What you see in n8n

Notes & use cases

Adds a message to an existing conversation. This is the operation that writes actual content, where conversation.create only opens the container.

Key parameters

  • Conversation ID: the conversation the thread is added to.
  • Type: chat, customer, note, phone or reply. The choice decides whether the message reads as an internal note or as a reply.
  • Text: the chat text.
  • Attachments: a collection where each entry carries FileName, Mime Type and Data, a Base64 encoded stream.
Use cases
an inventory check posts its result as a note on the open ticket, so the agent sees it without switching tools.
13

Get many threads

thread.getAll

What you see in n8n

Notes & use cases

Returns the threads of one conversation, which is how a workflow reads the exchange itself rather than the ticket header.

Key parameters

  • Conversation ID: the conversation whose threads you want.
  • Return All: on for the entire exchange, off to stop at Limit.
Use cases
feeding an AI step. One n8n template does this already, Park Help Scout retro-tagged tickets for review with OpenAI and TeamRetro, workflow 18453, where Help Scout data goes through a Code node and a Basic LLM Chain with a Structured Output Parser.
Need help

Need help automating Help Scout with n8n?

A person reads every message.

FAQ

Questions people ask about the Help Scout n8n integration

01Is the Help Scout n8n integration free to use?
Yes on the n8n side. The Help Scout node and the Help Scout Trigger ship with n8n, so there is nothing to install and nothing extra to pay for the connector itself. That holds on n8n Cloud, the hosted offer run by n8n, and on a self-hosted instance under the Community Edition and its Sustainable Use licence. A workflow built in one runs the same way in the other, which matters if you prototype on Cloud and later move to your own server. What a Help Scout account costs is a separate question and sits with Help Scout, not with n8n.
02What credentials do you need to connect Help Scout to n8n?
One credential, using OAuth2. That is the only authentication method supported here, so there is no API key path. You need a Help Scout account, then a Help Scout app created on their side following the Help Scout OAuth documentation, and then the OAuth2 flow completed once in the n8n Credentials menu. The credential is stored there and reused everywhere: the Help Scout node offers it in a dropdown, the Help Scout Trigger uses the same one, and an HTTP Request node can reuse it through predefined authentication. Set it up once and no workflow asks you to authenticate again.
03What are the limits of the Help Scout node in n8n?
Two things to know. First, the node exposes 13 operations across 4 resources, conversations, customers, mailboxes and threads. Anything outside that catalogue goes through the HTTP Request node, which calls any endpoint of the Help Scout API and reuses the same credential through predefined authentication, so you do not manage a second connection. Second, list operations are paginated. Return All walks every page of the API, and with it off the run stops at Limit. On a large mailbox that difference decides whether an export is complete or a sample, so set it deliberately rather than leaving the default in place.
04Does the Help Scout Trigger react in real time?
Yes. The Help Scout Trigger works by webhook, meaning Help Scout calls an n8n URL as soon as something happens instead of n8n checking on a schedule. n8n registers that URL with Help Scout when you activate the workflow, and each event reaches the workflow within seconds. There is no polling interval to configure and nothing to tune for latency. You pick which of the 12 events to listen to in the Events parameter, and the trigger stays idle until one of them fires. Grouped by family that is 10 conversation events, 1 customer event and 1 satisfaction event.
05n8n or Make for automating Help Scout?
It depends on three things. Hosting: n8n self-hosts with Docker or npm, or runs on n8n Cloud, while Make is hosted only, so if your support data has to stay on infrastructure you control the choice is made for you. Cost model: Make bills per operation, which is worth modelling against your ticket volume before you commit, since a busy mailbox generates a lot of events. Visual logic: both build workflows on a canvas, and the honest answer is that the one your team will actually maintain wins. A detailed comparison lives on the site rather than in this answer.
Same platform

Other docs you might need on this stack.

Browse all integrations