Resources · Make integration

Help Scout Make integrationAutomate Help Scout with Make.

What if your support inbox fed the rest of your tools on its own? The Help Scout Make integration gives you 41 modules, including 3 instant triggers. This guide is for support leads who know Help Scout well and are new to Make: connect, build, test.

Try the Help Scout integration on MakeSee the 41 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Help Scout Make integration do for your support team?

The Help Scout Make integration links your Help Scout account to Make, a no-code tool where you chain apps into a scenario (the automation you build). Help Scout can start a scenario the moment a conversation moves, a customer appears or a rating comes in, and Make can also write back into Help Scout.

A cleaner customer base. Someone signs up in your product or pays an invoice in another tool, and Create a Customer adds them to Help Scout before they ever write in. Your agents open the first ticket with a name and a history already there.

Ratings that reach the right people. Watch Satisfaction Rating fires as soon as a customer rates a reply. Pair it with Get a Conversation to pull the full exchange, then send it to a spreadsheet or a team channel so good and bad feedback stops hiding inside the helpdesk.

Conversations logged from outside. A form on your site, a phone system or a chatbot can open a ticket through Create a Conversation, so every request lands in the same mailbox.

The Help Scout documentation for Make carries one warning of its own: it is AI-generated and may contain mistakes, so check important details against Help Scout itself. If a scenario stalls, the Make troubleshooting guide covers the usual suspects. Help Scout also has an n8n node, described on the Help Scout n8n integration page, and the n8n vs Make comparison helps you pick a tool.

Connect

How do you connect Help Scout to Make?

  1. 01

    Add a Help Scout module

    In your scenario, add any Help Scout module and click Create a connection. A connection is your Help Scout account linked to Make once, then reused by every Help Scout module you add later.

  2. 02

    Name the connection

    The Connection name field is optional, but a clear name such as the team or mailbox owner saves confusion when several people share the same Make workspace.

  3. 03

    Authorize your account

    Follow the on-screen instructions to sign in to Help Scout, which uses OAuth 2. For advanced setups, create an app under Your Profile then My apps, and paste its Client ID and Client secret into Make.

First scenario

Your first scenario: add new customers to Help Scout automatically

GoalWhen a new client shows up in another tool, Make creates the matching customer in Help Scout.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big +. Pick the app where new clients first appear, such as your signup form or your billing tool, and choose its trigger.

  2. 02

    Add Create a Customer

    Click the + on the right of that first module, search for Help Scout and pick Create a Customer. Click Create a connection and sign in to your Help Scout account.

  3. 03

    Map the client details

    Fill the fields of Create a Customer by clicking into them and picking values from the first module, like the name and email it received. Each new client is a bundle, one item passed from module to module.

  4. 04

    Test with Run once

    Click Run once, then trigger a test signup in the first app. Open the bubbles above each module to read the bundles they received, and check the new customer in Help Scout.

  5. 05

    Schedule and switch it on

    If the first module is a scheduled trigger, set its clock on Scheduling (every 15 minutes by default). Then switch the scenario on. Each module run counts as one operation on your Make plan.

Triggers

What can start a Help Scout scenario?

3 modules start a scenario when something happens in Help Scout. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Help Scout as soon as it happens.

Help Scout1Watch Conversations

Watch Conversations

Instant trigger

In Make“Triggers when one or more of the following events occur (Conversation Agent Reply Created, Conversation Assigned, Conversation Created, Conversation Customer Reply Created, Conversation Deleted, Conversation Merged, Conversation Moved, Conversation Note Created, Status Changed in Conversation, Tags Created, Edited, Removed, or Merged in Conversation).”

Watch Conversations starts your scenario when something happens to a ticket: it is created, assigned, moved, merged or deleted, an agent or customer replies, a note is added, the status changes or tags are edited. One trigger covers this whole range of ticket events.

How it fires
instant, Help Scout calls Make through a webhook as soon as it happens.
When to use it
when a closed ticket should update your CRM, or a new assignment should ping the right person.
Watch out
if your scenario then edits that same conversation, tick only the events you need and add a filter, so your own edit does not start it again.
Help Scout2Watch Customers

Watch Customers

Instant trigger

In Make“Triggers when a customer is created.”

Watch Customers wakes your scenario every time a new customer record is created in Help Scout. Each new customer arrives as one bundle you can pass along to your other tools, with no export and no copy-paste.

How it fires
instant. Help Scout notifies Make through a webhook right when the customer is created, so nothing waits for a schedule.
When to use it
to copy fresh contacts into your newsletter list or CRM without exporting anything.
Watch out
it reacts to creation only, so edits on an existing customer never reach this trigger.
Help Scout3Watch Satisfaction Rating

Watch Satisfaction Rating

Instant trigger

In Make“Triggers when a satisfaction rating is received.”

Watch Satisfaction Rating runs your scenario each time a customer rates the support they got. It turns a number buried in Help Scout reports into something your team can act on while the conversation is still fresh.

How it fires
instant, Help Scout pushes the rating to Make by webhook the moment it is received.
When to use it
to log every rating in a spreadsheet, or alert a manager when a customer is unhappy.
Watch out
each rating uses operations for every module that follows, so filter early if you only care about some of them.
Modules

What can Make do in Help Scout?

Help Scout gives you 38 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Help Scout1

Create a Chat Handle

Action

In Make“Creates a new chat handle for an existing customer.”

Attaches a chat handle to a customer who already exists in Help Scout, so agents can see where to reach that person in chat without digging through old messages.

When to use it
a customer starts using your chat tool and you want their Help Scout profile to show it.
Watch out
the customer must exist first, so place this after Create a Customer or a search.
Help Scout2

Create a Conversation

Action

In Make“Creates a conversation in a mailbox with at least one thread.”

Opens a new ticket in the Help Scout mailbox you pick, with at least one thread inside it. Requests coming from forms, phone logs or other tools end up in the same queue as email.

When to use it
a contact form on your website should become a real ticket instead of an email forwarded by hand.
Watch out
an empty conversation is not possible, always map the message text into the first thread.
Help Scout3

Create a Customer

Action

In Make“Creates a new customer.”

Adds a brand-new person to your Help Scout customer list. Your agents then see a known name and profile the first time that person writes in, instead of an anonymous address.

When to use it
right after a signup, a purchase or a signed contract in another tool.
Watch out
run List Customers first if the person might already exist, or you may end up with duplicates.
Help Scout4

Create an Email

Action

In Make“Creates a new email for an existing customer”

Adds another email address to a customer profile that is already in Help Scout. Messages from a work address and a personal one can then be tied to the same person.

When to use it
your CRM stores a second address for a client and you want support to recognize both.
Watch out
the module expects an existing customer, so feed it a customer ID from an earlier module.
Help Scout5

Create a Phone

Action

In Make“Creates a new phone number for an existing customer.”

Saves a phone number on an existing Help Scout customer. Agents who handle callbacks get the number right on the profile instead of hunting for it in another app.

When to use it
your booking or billing tool collects phone numbers that support should see too.
Watch out
it adds a number rather than replacing one; use Update a Phone to correct an old entry.
Help Scout6

Create a Social Profile

Action

In Make“Creates a new social profile for an existing customer.”

Links a social media profile to a customer who is already in Help Scout. It gives agents extra context on who they are talking to, especially for public complaints.

When to use it
your social listening tool spots a client and you want the profile stored alongside their tickets.
Watch out
like the other contact details, it only works on a customer that exists already.
Help Scout7

Create a Thread

Action

In Make“Creates a new thread of chat, customer, note, phone, and reply.”

Adds a new message to a conversation that is already open: a chat, a customer message, an internal note, a phone log or a reply. The ticket history stays complete even when things happen outside Help Scout.

When to use it
an order update from your shop should appear as a note on the related ticket.
Watch out
pick the thread type carefully, since a note and a reply do not play the same role in the ticket.
Help Scout8

Create a Website

Action

In Make“Creates a new website for an existing customer.”

Stores a website address on a Help Scout customer profile. For B2B support, knowing the company site at a glance saves the agent a search before answering.

When to use it
a lead form captures the company URL and you want it visible next to future tickets.
Watch out
the customer has to exist beforehand, so chain it after a create or a search step.
Help Scout9

Create/Update an Address

Action

In Make“Creates or updates an address for an existing customer.”

Writes a postal address on an existing customer, creating it if there is none and updating it if there is. One module covers both cases, which keeps your scenario short.

When to use it
a shipping address changes in your store and support needs the latest one for returns.
Watch out
the previous address is overwritten, so keep a copy elsewhere if you need its history.
Help Scout10

Delete a Chat Handle

Action

In Make“Deletes a chat handle of a customer.”

Removes a chat handle from a customer profile in Help Scout. It keeps profiles accurate when a person stops using a channel or asks you to forget it.

When to use it
a customer closes their chat account and the old handle only causes confusion.
Watch out
deletion cannot be undone from Make, so test with Run once on a sample customer first.
Help Scout11

Delete a Conversation

Action

In Make“Deletes a conversation.”

Erases a whole conversation from Help Scout, threads included. It is the heavy tool of the list and deserves a clear rule behind it.

When to use it
spam tickets or test conversations flagged by another step should disappear instead of cluttering reports.
Watch out
there is no undo, and Watch Conversations can fire on the deletion, so add a filter before this module.
Help Scout12

Delete an Address

Action

In Make“Deletes an address of a customer.”

Clears the postal address saved on a Help Scout customer. Useful when a record should no longer carry location data at all.

When to use it
a customer asks for their personal data to be removed and you handle that request in a scenario.
Watch out
the address is gone for good once the module runs, so double-check the customer ID you map.
Help Scout13

Delete an Email

Action

In Make“Deletes an email of a customer.”

Takes one email address off a customer profile, leaving the rest of the record in place. Old or bounced addresses stop showing up for your agents.

When to use it
your email tool reports an address as dead and you want Help Scout to match.
Watch out
use List Emails first to find the right one when a customer has several addresses.
Help Scout14

Delete a Phone

Action

In Make“Deletes a phone number of a customer.”

Removes a phone number from a customer in Help Scout. It prevents agents from calling a number that no longer belongs to that person.

When to use it
your phone system flags a number as invalid and support records should follow.
Watch out
nothing brings the number back after the run, so keep this step behind a clear condition.
Help Scout15

Delete a Website

Action

In Make“Deletes a website of a customer.”

Drops a website entry from a customer profile. Profiles stay short and relevant when a client changes domain or shuts a project down.

When to use it
a company rebrands and the old site link now points nowhere useful.
Watch out
removal is final; if you only need a new URL, Update a Website is the gentler choice.
Help Scout16

Delete Social Profile

Action

In Make“Deletes a social profile of a customer.”

Unlinks a social profile from a Help Scout customer. Agents no longer see an account that is outdated or that the customer asked you to drop.

When to use it
a privacy request comes in and your scenario cleans every contact detail in one pass.
Watch out
the link cannot be recovered from Make once deleted, so run a test on a dummy profile.
Help Scout17

Get a Conversation

Action

In Make“Gets information about a conversation by ID.”

Fetches the full details of one conversation when you already know its ID. Handy right after a trigger, when you need more than what the trigger handed over.

When to use it
a rating arrives and you want the subject and assignee of the ticket before posting it to your team.
Watch out
without a valid ID the module fails, so map it from a previous module rather than typing it.
Help Scout18

Get a Customer

Action

In Make“Gets information about a customer by ID.”

Reads one customer profile by its ID and passes all of it along to the next modules. Think of it as opening the profile page, but inside your scenario.

When to use it
a conversation trigger gives you a customer ID and your CRM needs the name and details too.
Watch out
it retrieves by ID only; to find someone by email, reach for List Customers.
Help Scout19

Get a Mailbox

Action

In Make“Gets information about a mailbox by ID.”

Returns the details of one Help Scout mailbox from its ID. Teams running several inboxes use it to know which one a ticket belongs to before routing it.

When to use it
your scenario sends sales and support tickets to different channels and needs the mailbox name.
Watch out
run List Mailboxes once to see which IDs exist in your account.
Help Scout20

Get an Address

Action

In Make“Gets the address of a customer with a given ID.”

Reads the postal address stored on a given customer. Nothing is changed, the address is simply handed to the next module in your scenario.

When to use it
a return request comes in and your shipping tool needs the address on file.
Watch out
it only reads; to change the address, use Create/Update an Address.
Help Scout21

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Sends your own request to the Help Scout API, using the connection you already set up. It covers anything the listed modules do not, as long as the API supports it.

When to use it
you need a Help Scout feature that has no ready-made module in Make.
Watch out
you write the request yourself, so keep the Help Scout API reference open while you build it.
Help Scout22

Update a Chat Handle

Action

In Make“Updates a chat handle of a customer.”

Edits a chat handle already saved on a customer. The profile keeps pointing to the right chat account after a customer changes their username.

When to use it
your chat platform reports a new handle for a known client.
Watch out
you need the ID of the handle itself, which List Chat Handles gives you.
Help Scout23

Update a Conversation

Action

In Make“Updates conversation data.”

Changes the data of an existing conversation, for example to move it along once something happens elsewhere. Agents see the ticket in the right state without touching it.

When to use it
a refund is confirmed in your payment tool and the related ticket should reflect it.
Watch out
if Watch Conversations listens to status or tag changes, this update can start that scenario again.
Help Scout24

Update a Customer

Action

In Make“Updates customer data.”

Rewrites the main data of a customer profile in Help Scout. It keeps support in sync with the tool your team treats as the source of truth.

When to use it
a client updates their company name in your CRM and agents should see it too.
Watch out
for custom properties, Update Customer Properties is the module built for that job.
Help Scout25

Update an Email

Action

In Make“Updates an email of a customer.”

Corrects an email address already stored on a customer. It saves agents from answering a ticket and seeing the reply bounce.

When to use it
a customer fixes a typo in their address inside your app and you want Help Scout aligned.
Watch out
List Emails gives you the ID of the address to change when there are several.
Help Scout26

Update a Phone

Action

In Make“Updates a phone number of a customer.”

Replaces a phone number saved on a Help Scout customer with a new value. The old number stops circulating among agents.

When to use it
your booking system records a new mobile number for a regular client.
Watch out
the module edits one existing number, so it needs that number's ID from an earlier step.
Help Scout27

Update a Social Profile

Action

In Make“Updates a social profile of a customer.”

Edits a social profile already linked to a customer. Profiles stay accurate when someone changes their handle on a network.

When to use it
your community tool detects a renamed account for one of your clients.
Watch out
it only changes an existing link; adding a new network calls for Create a Social Profile.
Help Scout28

Update a Thread

Action

In Make“Updates an existing thread.”

Modifies a thread that already sits inside a conversation. Useful to correct or complete a note that an earlier scenario wrote automatically.

When to use it
an automated note about an order needs the final tracking status once it is known.
Watch out
you need both the conversation and the thread, so pull them with List Threads first.
Help Scout29

Update a Website

Action

In Make“Updates a website of a customer.”

Changes a website address stored on a customer profile, keeping the entry but with the new value. Cleaner than deleting and recreating it.

When to use it
a client moves to a new domain and your CRM already has the update.
Watch out
it works on one existing website entry, identified by its own ID.
Help Scout30

Update Customer Properties

Action

In Make“Updates customer properties.”

Fills the custom properties you defined on Help Scout customers, such as plan, account manager or region. Agents get business context right beside the ticket.

When to use it
a customer upgrades their plan in your billing tool and support should know before the next message.
Watch out
check in Help Scout that the properties you target are set up before you run it.
Help Scout31

List Chat Handles

Search

In Make“Gets a list of chat handles for a given customer.”

Returns every chat handle saved on one customer. Each handle comes out as its own bundle, so the next module runs once per handle.

When to use it
before updating or deleting a handle, to find the right one.
Watch out
a customer with no handle returns zero bundles, and the modules after it simply do not run.
Help Scout32

List Conversations

Search

In Make“Lists and filters all conversations.”

Searches your conversations with the filters you set and returns the matches, one bundle each. It is how a scenario answers questions like which tickets are still open.

When to use it
to build a report of pending tickets or to find the ticket tied to an order.
Watch out
every result triggers the next modules, so a loose filter can burn through operations.
Help Scout33

List Customers

Search

In Make“Lists and filters all customers”

Looks up customers in Help Scout with filters and hands back the matches. The classic use is checking whether someone already exists before you create them.

When to use it
just before Create a Customer, to avoid a second profile for the same email.
Watch out
it can return zero, one or many people; plan what the scenario does in each case.
Help Scout34

List Emails

Search

In Make“Gets a list of customer email addresses.”

Lists all the email addresses stored on one customer. Each address becomes a bundle carrying the ID you need to edit or remove it.

When to use it
a customer has several addresses and you must update only the outdated one.
Watch out
the modules placed after it run once per address, which counts operations.
Help Scout35

List Mailboxes

Search

In Make“Gets a list of the mailboxes.”

Gives you every mailbox in your Help Scout account. You get each mailbox ID, ready to pick in your other modules.

When to use it
while building, to find the ID of the inbox a scenario should post into.
Watch out
a single Run once is often enough to note the IDs, so there is no need to call it on every run.
Help Scout36

List Mailbox Folders

Search

In Make“Gets a list of mailbox folders.”

Returns the folders of a Help Scout mailbox, one bundle each. Your scenario learns how the inbox is organized before acting on tickets.

When to use it
you want a count or a report per folder, or need a folder ID for another step.
Watch out
folders belong to one mailbox, so get the mailbox ID from List Mailboxes first.
Help Scout37

List Tags

Search

In Make“Gets a list of tags.”

Retrieves the tags defined in your Help Scout account. It is the reference list when your scenario needs to match or report on tags consistently.

When to use it
to sync your support tags with a spreadsheet the team uses for reporting.
Watch out
each tag becomes a bundle, so large tag lists multiply the operations of later modules.
Help Scout38

List Threads

Search

In Make“Gets a list of threads.”

Pulls the threads of a conversation: replies, notes, customer messages. Your scenario can read the whole exchange instead of just its summary.

When to use it
to archive a resolved ticket in a document or pass its content to an AI summary step.
Watch out
long tickets return many bundles; add an aggregator if the next module expects one text.
Need help

Need help automating Help Scout with Make?

A person reads every message.

FAQ

Questions about Help Scout and Make

01Is the Help Scout Make integration free to use?
Yes. Help Scout is a standard app in Make, so it is available on the Free plan. That plan lets you keep 2 scenarios active, with at least 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans lower the interval to 1 minute and remove the cap on active scenarios. You still need your own Help Scout subscription, which Make does not cover. Each module run counts as one operation on your Make plan.
02What do you need to connect Help Scout to Make?
You need an active Help Scout account and a Make account, and the link uses OAuth 2, so you mostly sign in and approve access. In a scenario, add a Help Scout module, click Create a connection, optionally name it, then follow the on-screen instructions. Advanced setups can create an app in Help Scout from your profile, then paste its Client ID and Client secret. For instant triggers, click Create a webhook before creating the connection.
03Do Help Scout triggers react in real time in Make?
Yes. All three Help Scout triggers are instant: Watch Conversations, Watch Customers and Watch Satisfaction Rating. Help Scout calls Make through a webhook as soon as the event happens, so your scenario does not wait for the 15 minute default schedule that scheduled triggers use. The lightning badge on the module in the editor shows it. Remember that each event then consumes operations for every module that follows, so filter early when only some events matter.
04What if a Help Scout feature has no module in Make?
In most cases, yes. The Make an API Call module sends any request the Help Scout API accepts, reusing the connection you already have, so you are not limited to the 41 listed modules. You write the request yourself with the API reference at hand. Also keep in mind that the Help Scout documentation for Make warns it is AI-generated and may contain mistakes, so verify important details with Help Scout directly.
05Make or n8n for Help Scout: which one fits?
It depends on the tool your team already runs. Help Scout has an n8n node too, so both paths exist. On Make, you get 41 ready modules, instant triggers for conversations, customers and ratings, and Make an API Call for the rest. The practical question is where your other scenarios live, since keeping support automations next to them makes maintenance simpler. The comparison page linked earlier walks through the criteria side by side.
Same platform

Other docs you might need on this stack.

Browse all integrations