Resources · Make integration

SupportBee Make integrationAutomate SupportBee with Make.

What if every new ticket, reply or comment in SupportBee could start work in your other tools? The SupportBee Make integration gives you 12 modules, 4 of them instant triggers. This page shows you how to link your account and build a first working scenario.

Try the SupportBee integration on MakeSee the 12 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the SupportBee Make integration do for your help desk?

The SupportBee Make integration links your help desk to Make, a visual tool where you build a scenario: an automation made of modules, each one a brick that watches, reads or changes something. SupportBee brings 12 of these bricks, so tickets can move between your support inbox and the rest of your stack without copy and paste.

Tickets that open themselves. A request lands in a form, a spreadsheet or a chat tool, and Create a Ticket files it in SupportBee so nobody retypes it. The Airtable Make integration is a common starting point for that kind of intake.

Replies your team hears about. Watch New Customer Reply fires the moment a customer answers, so you can alert the right person in the tool they already watch, instead of waiting for someone to refresh the inbox.

A cleaner queue. Search Tickets finds the ones you care about, and Trash a Ticket or Un-Trash a Ticket move them in or out of the trash. Test the search with Run once first, so you see exactly which tickets would move.

The Make documentation for SupportBee lists no specific limits, and it warns that its page is AI-generated and may contain mistakes, so double-check anything important with SupportBee itself. When a module you need is not in the list, Make an API Call covers the rest of the SupportBee API. If you are still choosing a platform, read the n8n vs Make comparison, and check Make pricing before you scale up.

Connect

How do you connect SupportBee to Make?

  1. 01

    Copy your API token

    In SupportBee, click your profile picture in the upper left corner of the dashboard, choose API Token in the menu, and copy the token shown on screen. You need an active SupportBee account for this.

  2. 02

    Add a SupportBee module

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

  3. 03

    Paste and save

    Give the connection a name in Connection name if you like (it is optional), paste the API token you copied, and follow the on-screen instructions to finish.

First scenario

Build your first scenario with SupportBee

GoalWhen a request arrives in another app, Make opens a matching ticket in SupportBee.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. Pick the app where requests reach you today, such as your form tool or spreadsheet.

  2. 02

    Set up that first module

    Choose its trigger, link your account with Create a connection, and fill its fields. Once connected, Make lists the forms, sheets or objects it can read, so you pick instead of typing.

  3. 03

    Add Create a Ticket

    Click the + on the right of the first module, search for SupportBee and pick Create a Ticket. Connect your account with the API token, as shown above.

  4. 04

    Map the request into the ticket

    Fill the ticket fields by mapping data from the first module: click a field and choose the value that arrived in the request. Each item passing through is a bundle, like one form entry.

  5. 05

    Test with Run once

    Click Run once, send a test request, and read the bundles each module received. If a ticket shows up in SupportBee, the mapping works.

  6. 06

    Schedule and switch on

    Set the schedule on the first module (every 15 minutes by default for a new scenario) and switch the scenario on. From then on, each request becomes a ticket without anyone touching it.

Triggers

What can start a SupportBee scenario?

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

SupportBee1Watch New Agent Reply

Watch New Agent Reply

Instant trigger

In Make“Watches for a new agent reply.”

Every answer your agents send becomes a starting point for a scenario, so the work that follows a reply can happen on its own. Log the answer somewhere your managers review it, or tell a sales colleague that the account got a response.

How it fires
instant: SupportBee calls Make through a webhook as soon as an agent replies.
When to use it
pick it when the event that matters is your team speaking, not the customer, for instance to keep a shared log of answers on key accounts.
Watch out
when you add it, click Create a webhook before Create a connection, or the trigger stays silent.
SupportBee2Watch New Comment

Watch New Comment

Instant trigger

In Make“Watches for a new comment.”

Internal discussion on a ticket reaches the people who need it, even if they never open SupportBee. Each new comment starts the scenario, so you can forward the note to a chat channel or a project tool your developers use.

How it fires
instant: SupportBee calls Make through a webhook as soon as someone adds a comment.
When to use it
a support agent asks engineering a question on a ticket, and you want that question to land where engineering already works.
Watch out
it reacts to comments only; replies from agents or customers have their own triggers on this page.
SupportBee3Watch New Customer Reply

Watch New Customer Reply

Instant trigger

In Make“Watches for a new customer reply.”

You learn the moment a customer writes back, which keeps a waiting conversation from going cold. The scenario can ping the agent in charge, flag the account in your CRM, or record the reply for later analysis.

How it fires
instant: SupportBee calls Make through a webhook as soon as the customer replies.
When to use it
your team juggles many open tickets and a returning customer should jump to the top of someone's attention.
Watch out
pair it with Get a Ticket when later modules need the ticket this reply belongs to, and test with Run once to see what the bundle holds.
SupportBee4Watch New Ticket

Watch New Ticket

Instant trigger

In Make“Watches for a new ticket.”

Fresh requests are picked up as they appear, so a new ticket can be copied, announced or routed without waiting for someone to scan the inbox. It is the natural first module for most SupportBee scenarios.

How it fires
instant: SupportBee calls Make through a webhook as soon as a ticket is created.
When to use it
you want a new ticket to open a matching row in a spreadsheet, or a message in the channel your support team reads.
Watch out
a ticket your own scenario files with Create a Ticket is still a new ticket, so expect it to fire this trigger too and avoid a flow that feeds itself.
Modules

What SupportBee modules does Make offer?

SupportBee gives you 8 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

SupportBee1

Create a Ticket

Action

In Make“Creates a ticket.”

Requests that start outside SupportBee end up in your queue as proper tickets, with the details mapped in from wherever they came from. No more copying emails or form answers by hand.

When to use it
a web form, a spreadsheet row or a chat message should turn into something your support team tracks.
Watch out
every run creates a new ticket, so test with Run once before switching the scenario on.
SupportBee2

Delete a Trashed Ticket

Action

In Make“Deletes a trashed ticket.”

This clears a ticket for good once it already sits in the SupportBee trash, which keeps the trash from piling up with requests nobody needs.

When to use it
after Trash a Ticket, when you are sure the ticket, such as obvious spam, has no reason to come back.
Watch out
a deletion cannot be undone, unlike trashing, which Un-Trash a Ticket can reverse.
SupportBee3

Get a Ticket

Action

In Make“Gets a ticket.”

Pulls up one ticket so the next modules can work with its details, for example the ticket a reply or comment belongs to. Think of it as opening a single ticket from inside your scenario.

When to use it
a trigger or a search points to a ticket, and a later step needs more of it than you already have.
Watch out
it reads one ticket at a time; to look through many, start with Search Tickets or Fetch Tickets.
SupportBee4

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Reaches any part of the SupportBee API that the listed modules leave out, using the connection you already set up. It is your escape hatch when a task has no dedicated module.

When to use it
you need a SupportBee feature missing from the modules on this page and you are comfortable reading the SupportBee API reference.
Watch out
you write the request yourself, so check the SupportBee API documentation for the right address and format.
SupportBee5

Trash a Ticket

Action

In Make“Trashes a ticket.”

Moves a ticket out of the active queue and into the SupportBee trash, so your agents stop seeing it while it stays recoverable.

When to use it
a search turns up tickets your team agrees are noise, like automated notifications that slipped into the support address.
Watch out
if a search feeds this module, run it once and read the bundles first, because every ticket it returns goes to the trash.
SupportBee6

Un-Trash a Ticket

Action

In Make“Un-trashes a ticket.”

Brings a trashed ticket back into your queue, which undoes a cleanup that went too far without asking anyone to dig through the trash by hand.

When to use it
a customer writes about a request that was trashed, or a cleanup scenario caught tickets it should have left alone.
Watch out
it only helps while the ticket is still in the trash; after Delete a Trashed Ticket, there is nothing to restore.
SupportBee7

Fetch Tickets

Search

In Make“Fetches tickets.”

Returns a batch of tickets in one step, each one a separate bundle, so the rest of the scenario can handle them one by one. Handy for exports and reports.

When to use it
you want to copy your tickets into a spreadsheet or a reporting tool instead of looking for one specific request.
Watch out
each ticket returned counts toward your operations in the modules that follow, so a large batch uses more of your plan.
SupportBee8

Search Tickets

Search

In Make“Searches from all tickets.”

Looks through all your SupportBee tickets and hands back the ones that match, which is how a scenario finds an existing ticket before acting on it.

When to use it
before creating a ticket, check whether the same customer already has one open so you do not create duplicates.
Watch out
a search can return zero, one or several bundles, so plan what happens next in each case.
Need help

Need help automating SupportBee with Make?

A person reads every message.

FAQ

SupportBee and Make: common questions

01Is the SupportBee Make integration free?
Yes, SupportBee is a standard app in Make, so it works on the Free plan. That plan allows 2 active scenarios, runs scheduled scenarios every 15 minutes at the shortest, stops a run after 5 minutes, and caps files at 5 MB and data transfer at 512 MB. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute, remove the cap on active scenarios and allow 40 minutes per run. Usage is counted in credits, one per operation, meaning one module run on one bundle. For the SupportBee subscription itself, check the SupportBee pricing page.
02What do you need to connect SupportBee to Make?
You need an active SupportBee account and its API token. In SupportBee, click your profile picture in the upper left corner of the dashboard, then API Token, and copy the value shown. In Make, add a SupportBee module, click Create a connection, optionally name it, and paste the token. For an instant trigger, click Create a webhook first, then Create a connection. The connection is saved once and reused by every SupportBee module in your scenarios.
03Do SupportBee triggers in Make fire in real time?
Yes. All 4 SupportBee triggers are instant: Watch New Ticket, Watch New Agent Reply, Watch New Customer Reply and Watch New Comment. SupportBee calls Make through a webhook as soon as the event happens, so the scenario does not wait for a polling interval. The lightning badge on the module shows this in the editor. The only extra step is clicking Create a webhook when you add the trigger, before creating the connection.
04What if a SupportBee module is missing in Make?
Use Make an API Call. It calls any endpoint of the SupportBee API with the connection you already have, so a feature without a dedicated module is still reachable. You write the request yourself, following the SupportBee API reference. Also keep in mind that the Make documentation page for SupportBee says it is AI-generated and may contain mistakes, so confirm important details with SupportBee directly before you build on them.
05Should you use Make or n8n for SupportBee?
It depends on what you already run. On Make, SupportBee comes with 12 modules: 4 instant triggers, 6 actions and 2 searches, plus a visual editor where each step is a module you can test with Run once. Apps often have an n8n node as well, so if your team already works in n8n, check whether SupportBee is covered there before switching. The comparison page on this site lays out the criteria side by side.
Same platform

Other docs you might need on this stack.

Browse all integrations