Resources · Make integration

supi support Make integrationAutomate supi support with Make.

Keep your supi support contacts and canned replies in step with the rest of your tools. The supi support Make integration gives you 14 modules: 11 actions and 3 searches. This page shows what each one does, how to link your account and how to build a first scenario.

Try the supi support integration on MakeSee the 14 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the supi support Make integration do for you?

The supi support Make integration lets a Make scenario, the automation you build in Make, create, edit, delete and list your supi support contacts, contact groups and canned replies, and send messages. Each step of that scenario is a module, one brick that does a single job, and you assemble them without writing code.

A new customer lands in supi support without retyping. When a form tool or a shop records a buyer, a scenario can run Add a Contact, then Send a Message so the conversation starts on your side. The first module comes from that other app, since supi support has no trigger of its own.

Your saved answers stay tidy. Support leads who keep a library of standard answers can use Get the Canned Replies List to review what exists, then Edit a Canned Reply or Delete a Canned Reply to fix the wording in one pass instead of clicking through each entry.

Contact groups follow your segments. Add a Contact Group, Edit a Contact Group and Get the Contact Group List let a sales or success team mirror the segments they already keep in a CRM or a spreadsheet.

Know the limits before you start. Make publishes only a short documentation page for this app, because supi support shares little public information, so the page does not describe fields or quotas. When a listed module is not enough, Make an API Call reaches the rest of the supi support API with the same connection. If you are weighing tools, the n8n vs Make comparison sets out the criteria, and the Make training walks through the editor step by step.

Connect

How do you connect supi support to Make?

  1. 01

    Add a supi support module

    Open your scenario, click the + and search for supi support. Pick any of its modules, then click Create a connection. A connection is your supi support account linked to Make once and reused by every supi support module afterwards.

  2. 02

    Name the connection

    Giving the connection a name is optional, yet it helps as soon as you manage more than one account. Something like the workspace or the team it belongs to makes the right one easy to spot later in the dropdown.

  3. 03

    Authorize and save

    Authorize Make on the supi support page that opens, or paste the key supi support gives you, depending on what the connection window asks for. Then click Save, and the module is ready to use.

First scenario

Your first scenario with supi support

GoalWhen a new lead is recorded in another app, Make adds that person to supi support and sends them a message.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. Here it belongs to the app where your leads appear, such as a form or a CRM, since supi support has no trigger.

  2. 02

    Add Add a Contact

    Click the + to the right of that first module, search for supi support and choose Add a Contact. Click Create a connection if you have not linked your account yet.

  3. 03

    Map the lead's details

    Fill the fields Make shows for the contact by mapping data from the first module, the name or email it received. Each lead travels as one bundle, one item passed from a module to the next.

  4. 04

    Add Send a Message

    Click the + again, pick Send a Message from supi support and fill its fields, reusing what Add a Contact returned so the message goes out on the record you just created.

  5. 05

    Test with Run once

    Click Run once to execute the scenario one time. Open the bubble above each module to read the bundles it received, then check in supi support that the contact and message are there.

  6. 06

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, and switch the scenario on. Each module run on one bundle counts as one operation on your Make plan.

Modules

What each supi support module does

supi support gives you 14 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

supi support1

Add a Canned Reply

Action

In Make“Adds a canned reply.”

Saves a new ready-made answer in supi support, so your agents can reuse it instead of typing the same explanation again.

When to use it
a new policy or product note has been approved in a shared doc and should become a standard reply straight away.
Watch out
run Get the Canned Replies List first if the answer might already exist, or you will end up with duplicates.
supi support2

Add a Contact

Action

In Make“Adds a contact.”

Creates a person in supi support from data another module passed along, which saves you from copying names by hand when a lead or customer appears elsewhere.

When to use it
right after a form submission, a purchase or a new CRM record, as the first supi support step.
Watch out
this module always creates; search with Get the Contact List first when the person may already be there.
supi support3

Add a Contact Group

Action

In Make“Adds a contact group.”

Opens a new group in supi support, giving you a container for contacts that share a segment, a client account or a campaign.

When to use it
a new segment or client account is created in your CRM and needs its own group on the support side.
Watch out
the group starts empty, so plan the next step that fills it; the documentation does not say how contacts are attached.
supi support4

Delete a Canned Reply

Action

In Make“Deletes a canned reply.”

Removes a saved answer from supi support so agents stop sending wording that no longer matches your offer or your rules.

When to use it
a product is retired or a policy changes, and the matching reply has to disappear with it.
Watch out
a deletion cannot be undone from Make; test with Run once on a single reply before letting the scenario run on its own.
supi support5

Delete a Contact

Action

In Make“Deletes a contact.”

Erases one contact from supi support, which keeps your address book in line with the records you have closed in other tools.

When to use it
a customer asks to be forgotten or a record is removed from your CRM, and supi support should follow.
Watch out
Make cannot bring the contact back; add a filter so only the intended person reaches this module.
supi support6

Delete a Contact Group

Action

In Make“Deletes a contact group.”

Takes a whole contact group out of supi support when the segment or client account behind it has ended.

When to use it
a campaign closes or a client leaves, and the group attached to it only clutters the list.
Watch out
Make's documentation does not say what happens to the contacts inside the group, so try it on a test group before any real one.
supi support7

Edit a Canned Reply

Action

In Make“Edits a canned reply.”

Fixes a saved answer in place. Next time any agent inserts it in supi support, they get the corrected text.

When to use it
a price wording, a link or a procedure changes and the reply must be updated rather than recreated.
Watch out
the module needs to know which reply to change; feed it from Get the Canned Replies List instead of typing the reference.
supi support8

Edit a Contact

Action

In Make“Edits a contact.”

Updates a contact who already exists in supi support, keeping the details your agents see as fresh as the ones in your main tool.

When to use it
a customer changes email or company in your CRM and the support record should match.
Watch out
find the person first with Get the Contact List and map that result, so the change lands on the right record.
supi support9

Edit a Contact Group

Action

In Make“Edits a contact group.”

Changes an existing contact group in supi support, so it keeps matching the segment it stands for.

When to use it
a client account is renamed or a segment is redefined on the sales side.
Watch out
pick the group from Get the Contact Group List; two groups with close names are easy to confuse when you type them by hand.
supi support10

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Sends your own request to the supi support API through the connection you already set up, which covers whatever the listed modules leave out.

When to use it
you need an object or an option that no module above offers, and supi support's API documents it.
Watch out
you write the request yourself, so keep supi support's API reference open; Make's own page for this app is limited.
supi support11

Send a Message

Action

In Make“Sends a message.”

Posts a message through supi support from inside a scenario, so a customer hears from you when the scenario picks up news from another tool.

When to use it
after Add a Contact, to greet a new customer, or when an order or ticket changes status elsewhere.
Watch out
a scenario that runs on many bundles sends one message per bundle; test with Run once on a single record first.
supi support12

Get the Canned Replies List

Search

In Make“Gets the canned replies list.”

Pulls the saved answers stored in supi support into your scenario, which lets you review, export or audit them without opening each one.

When to use it
before editing or deleting a reply, or to copy your reply library into a spreadsheet for a review.
Watch out
as a search module it returns zero, one or many bundles, and every following module runs once per bundle.
supi support13

Get the Contact Group List

Search

In Make“Gets the contact group list.”

Returns the contact groups that exist in supi support, the quickest way to check a group is there before you create or change one.

When to use it
ahead of Add a Contact Group, to avoid a duplicate, or to sync group names with your CRM.
Watch out
the result can be empty; add a filter after it so the next module only runs when a group was found.
supi support14

Get the Contact List

Search

In Make“Get the contact list.”

Reads the contacts held in supi support and hands them to the next modules, so you can match, clean or copy your support address book.

When to use it
to check whether a person exists before Add a Contact, or to export contacts for a mailing.
Watch out
a long list means many bundles, and each one run through later modules counts as an operation on your plan.
Need help

Need help automating supi support with Make?

A person reads every message.

FAQ

Questions about the supi support Make integration

01Is the supi support Make integration free?
Yes, supi support is a standard app in Make, available from the Free plan. The Free plan still has limits: 2 active scenarios, 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 (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations, one per module run on one bundle. Any price of supi support itself is outside this page.
02What do you need to connect supi support to Make?
A supi support account you can authorize, and nothing else that Make documents. Make's page for this app lists no prerequisites and no official connection steps, so the generic path applies: add any supi support module, click Create a connection, optionally name it, then authorize Make on the supi support page or paste the key the app gives you, and click Save. The same connection then serves all 14 modules. If the window asks for a key you cannot find, look in the settings of your supi support account.
03Does the supi support Make integration have a trigger?
No, supi support has no trigger module in Make, so a scenario cannot start from an event inside supi support. You start it another way. The first module can belong to another app, such as a form, a shop or a CRM, whose new record then flows into Add a Contact or Send a Message. You can also open the scenario with a supi support search such as Get the Contact List and let the schedule on that first module run it, every 15 minutes by default, down to 1 minute on paid plans.
04What if a supi support module is missing in Make?
Use Make an API Call. It sends any request the supi support API accepts, with the connection you already created, so you are not limited to the 11 actions and 3 searches listed here. Keep in mind that Make's own documentation for supi support is limited, because little public information exists about the app, so you will rely on the API reference supi support provides. If an endpoint is not public at all, ask supi support before building the scenario around it.
05Should you use Make or n8n for supi support?
It depends on what your team already runs and what you need from supi support. On the Make side the facts are clear: 14 modules covering contacts, contact groups, canned replies and messages, no trigger, and Make an API Call for the rest. Whether n8n has a supi support node is something to check in n8n itself before deciding. Compare the two on the modules available for this app, how you prefer to build, and the tools your scenarios already connect to, rather than on a general ranking.
Same platform

Other docs you might need on this stack.

Browse all integrations