Resources · Make integration

SuperSaaS Make integrationAutomate SuperSaaS with Make.

Every booking in SuperSaaS can start an automation on its own. The SuperSaaS Make integration gives you 8 instant triggers, from new appointments to shop purchases. This guide is for people who run a schedule, not code: connect your account, then build a first scenario.

Try the SuperSaaS integration on MakeSee the 8 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the SuperSaaS Make integration do for you?

The SuperSaaS Make integration lets SuperSaaS tell Make the moment something happens on your booking site: an appointment is booked or changed, a client signs up, a form is sent, a credit is bought. Make then runs a scenario, which is the automation you build as a chain of modules, and passes that event to your other apps.

A calendar that updates the rest of your tools. A physiotherapy practice can put New appointment at the start of a scenario and push every booking into its shared spreadsheet or team chat, while Changed appointment catches every later edit to a booking.

A client list that stays in sync. A tutoring center can use New user to copy each new sign-up into its CRM, and Changed user to follow later edits to a profile.

Emails sent from your own tools. Email generated and Reminder / Follow up hand SuperSaaS messages to Make, so a salon can send them through its own mail account. Read the warnings in the notes below first: SuperSaaS stops sending those messages itself while the webhook exists.

What Make does not offer here: every SuperSaaS module is a trigger. There is no action to create a booking and no search, and no Make an API Call module either. If you are still choosing a platform, the Make review and the n8n vs Make comparison lay out the options, and the Acuity Scheduling Make integration covers another booking tool.

Connect

How do you connect SuperSaaS to Make?

  1. 01

    Create an API key in SuperSaaS

    Log in to SuperSaaS and open the Account Info page. Create an API key there and keep it at hand. Make needs this key, together with an active SuperSaaS account, to read your events.

  2. 02

    Add a SuperSaaS module and its webhook

    In your Make scenario, add any SuperSaaS module. They all carry the instant tag, so click Create a webhook first, then Create a connection. A connection is your SuperSaaS account linked to Make once and reused by every module.

  3. 03

    Paste your credentials and save

    Give the connection a clear label in Connection name if you like, then enter the credentials you copied from SuperSaaS, or follow the instructions on screen. Save, and the webhook is ready to receive events.

First scenario

Your first scenario with SuperSaaS and Make

GoalWhen a client books a new appointment in SuperSaaS, Make sends the booking details to another app your team already uses.

  1. 01

    Start a blank scenario

    Open the Scenarios page in Make, create a new scenario and click the big + to place the first module.

  2. 02

    Pick the New appointment trigger

    Search for SuperSaaS and choose New appointment. Click Create a webhook, then Create a connection, and link the account with your API key.

  3. 03

    Add the app that receives the booking

    Click the + on the right of the trigger and pick the app that should get the booking, such as a spreadsheet or a chat tool. Map the appointment data from SuperSaaS into its fields.

  4. 04

    Test with Run once

    Click Run once, then book a test appointment on your SuperSaaS schedule. Open the bubble above each module to read the bundle it received, meaning the single booking that went through.

  5. 05

    Switch the scenario on

    Once the test looks right, turn the scenario on. From then on, each new booking reaches Make through the webhook and runs the chain without you opening the editor.

Triggers

The 8 SuperSaaS triggers and when to pick each one

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

SuperSaaS1Changed appointment

Changed appointment

Instant trigger

In Make“Triggers each time an appointment changes on your schedule. A new appointment also counts as a change.”

This trigger gives you one feed of every edit to your schedule. A moved slot, an updated booking and even a brand new appointment all reach Make as a change.

How it fires
instant, SuperSaaS calls Make through a webhook as soon as the edit happens.
When to use it
keep an outside calendar or a planning sheet aligned with SuperSaaS, whatever the client did to their booking.
Watch out
new bookings arrive here too, so if you also run New appointment, add a filter to avoid handling the same booking twice.
SuperSaaS2Changed user

Changed user

Instant trigger

In Make“Triggers for each change to a user in your SuperSaaS account. A new user also counts as a change.”

With this trigger, your client records elsewhere follow what happens to users in SuperSaaS. Any edit to a user, and each new user, is passed to your scenario.

How it fires
instant, SuperSaaS alerts Make through a webhook right when the user changes.
When to use it
a client updates a phone number or an address and your CRM should show the new value without anyone retyping it.
Watch out
sign-ups count as changes as well, so pairing it with New user can create duplicates unless you filter one path.
SuperSaaS3Credit purchase

Credit purchase

Instant trigger

In Make“Triggers when a user buys something in your shop”

Credit purchase turns each sale in your SuperSaaS shop into a fresh run of your scenario, so money coming in can be logged or acted on right away.

How it fires
instant, SuperSaaS sends the purchase to Make over a webhook as soon as the client pays.
When to use it
a yoga studio selling class packs adds each purchase to its bookkeeping sheet and sends a thank-you message from its own tool.
Watch out
it only covers purchases made in the SuperSaaS shop, not payments you take anywhere else.
SuperSaaS4Email generated

Email generated

Instant trigger

In Make“Triggers each time an email is generated. Can be used to send notifications from your own email account. Note that the SuperSaaS mail server will stop sending mail when this webhook exists.”

Email generated hands you every message SuperSaaS prepares, so you can send it from your own email account or another channel and keep your branding.

How it fires
instant, Make gets the email through a webhook the moment SuperSaaS generates it.
When to use it
you want confirmations to leave from your company address and land in your sent folder.
Watch out
once this webhook exists, the SuperSaaS mail server stops sending mail. If your scenario is off or fails, clients receive nothing, so test it before you rely on it.
SuperSaaS5New appointment

New appointment

Instant trigger

In Make“Triggers for each new appointment on your schedule.”

This is the cleanest starting point: New appointment fires once per fresh booking on your schedule, and edits to existing bookings stay out of the way.

How it fires
instant, SuperSaaS notifies Make through a webhook as soon as the booking is made.
When to use it
post each booking in your team chat, add a row to a shared sheet or open a task for whoever runs the session.
Watch out
a reschedule does not come through this trigger, so pick Changed appointment when edits matter to you.
SuperSaaS6New form

New form

Instant trigger

In Make“Triggers each time a user submits a new stand-alone form. Does not trigger for forms that are filled out as part of an appointment or user sign up.”

New form sends Make the answers each time someone fills in one of your stand-alone SuperSaaS forms, so a request or questionnaire can go straight to the right person.

How it fires
instant, a webhook carries the submission to Make as soon as the user sends it.
When to use it
an intake questionnaire should create a record in your client file or alert a colleague.
Watch out
forms filled in during a booking or at user sign-up do not fire it. Catch those answers with New appointment or New user.
SuperSaaS7New user

New user

Instant trigger

In Make“Triggers each time a new user registers on your SuperSaaS account.”

New user gives you a clean signal for growth: one run of your scenario per person who registers on your SuperSaaS account, and nothing for later edits.

How it fires
instant, SuperSaaS calls Make through a webhook as soon as the registration goes through.
When to use it
add each new client to your newsletter tool or CRM and send a welcome message of your own.
Watch out
profile edits after sign-up are not sent here; Changed user covers those.
SuperSaaS8Reminder / Follow up

Reminder / Follow up

Instant trigger

In Make“Triggers on a reminder or a follow up. Note that SuperSaaS will stop sending the reminder or follow up while this web hook exists.”

Reminder / Follow up lets you decide how reminders and follow-ups reach clients, by text, chat or your own mail, instead of the default SuperSaaS message.

How it fires
instant, SuperSaaS pushes each reminder or follow up to Make through a webhook when it is due.
When to use it
clients read a text message more reliably than an email, or a follow up should ask for a review.
Watch out
while this webhook exists, SuperSaaS no longer sends the reminder or follow up itself. Your scenario must handle every one.
Need help

Need help automating SuperSaaS with Make?

A person reads every message.

FAQ

SuperSaaS and Make: common questions

01Is the SuperSaaS Make integration free?
Yes, SuperSaaS is a standard app, so its modules are available from the Free plan of Make. That plan has limits: 2 active scenarios, runs of 5 minutes at most, files up to 5 MB and 512 MB of data transfer. Each module run on one bundle counts as one operation on your plan. Paid plans (Core, Pro, Teams, Enterprise) lift the active scenario limit and allow runs of up to 40 minutes. Your SuperSaaS subscription is a separate matter that this page does not cover.
02What do you need to connect SuperSaaS to Make?
You need an active SuperSaaS account and an API key. Create the key on the Account Info page inside SuperSaaS and copy it. In Make, add a SuperSaaS module; because every module is instant, click Create a webhook first, then Create a connection. Name the connection if you want, paste the credentials and save. The same connection then serves all 8 triggers, so you only do this once per SuperSaaS account.
03Do SuperSaaS triggers in Make fire in real time?
Yes. All 8 SuperSaaS triggers are instant: SuperSaaS calls Make through a webhook as soon as the event happens, so a booking or a purchase starts your scenario right away instead of waiting for a check. You will see the lightning badge on these modules in the editor. Scheduled triggers, which Make polls every 15 minutes by default on a new scenario, do not apply to this app. Keep in mind that the scenario must be switched on to catch events.
04What if a SuperSaaS module you need is missing in Make?
It depends on what you need. The app only has triggers, so Make cannot create or search bookings in SuperSaaS through it, and there is no Make an API Call module to fill the gap. Use the triggers to push data out, then act in another app that has the actions you need. If the gap blocks your project, the Hack'celeration team can look at your case and suggest another route.
05Should you use Make or n8n for SuperSaaS?
It depends on your team and your setup. On Make, SuperSaaS brings 8 instant triggers and no action or search, which suits flows that start from a booking, a sign-up or a purchase. Many apps also have an n8n node, so check what n8n offers for SuperSaaS before you decide. Pick the tool your team already knows and can maintain, and compare the modules each one gives you for the exact events you need.
Same platform

Other docs you might need on this stack.

Browse all integrations