Resources · Make integration

SuperHote Make integrationAutomate SuperHote with Make.

What happens in your rental business the moment a guest books? The SuperHote Make integration gives you 4 instant triggers: new booking, changed booking, signed contract, processed payment. This guide shows how to connect your account and build your first scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the SuperHote Make integration do for you?

The SuperHote Make integration lets SuperHote start a Make scenario, the automation you build in Make, whenever a reservation event happens. SuperHote sends the reservation details, and the rest of your scenario decides where they go. It only listens: there is no module that writes back into SuperHote.

Hand a new stay to your team. Start with Watch After Booking: each new reservation arrives in Make with its details, ready to be passed to the tool where your cleaning or check-in team works.

Chase paperwork only when it is done. Watch After Contract Sign fires once the guest has signed, so the follow-up message or the file for your records goes out at the right moment, never before.

Keep your books in step with guests. Watch After Payment reacts to a processed payment, and Watch After Booking Modified catches a changed stay, so the copy of each reservation you keep elsewhere does not drift.

What Make does not cover here: the integration has no action, no search and no Make an API Call module, so it cannot create or edit a reservation in SuperHote. Make also warns that its SuperHote documentation is limited because public information about the app is scarce. If you are new to the tool, the Make review gives the big picture, and the n8n vs Make comparison helps if you are still choosing a platform.

Connect

How do you connect SuperHote to Make?

  1. 01

    Add a SuperHote module

    In your scenario, click the +, type SuperHote and pick one of the four Watch modules. Then click Create a connection. A connection is your SuperHote account linked to Make once, then reused by every SuperHote module.

  2. 02

    Name the connection

    Giving it a name is optional, but it pays off if you manage several SuperHote accounts, for example one per property owner. A clear label saves you from picking the wrong account in a later scenario.

  3. 03

    Authorize Make, then save

    Follow what SuperHote asks for: either approve Make on the SuperHote page that opens, or paste the key SuperHote gives you. Click Save, and the connection appears in the module, ready to use.

First scenario

Your first scenario: send every new SuperHote booking to your team

GoalWhen a guest books in SuperHote, Make passes the reservation details to the app your team already uses.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the large + to add the first module of the chain.

  2. 02

    Pick Watch After Booking

    Search for SuperHote, choose Watch After Booking and select your connection. The lightning badge means SuperHote calls Make itself; there is no polling to set.

  3. 03

    Add the destination

    Click the + on the right of the trigger and add the module of the app that should receive the stay. Map the reservation details from the SuperHote bubble into its fields.

  4. 04

    Test with Run once

    Click Run once, then create a test booking in SuperHote. Each module shows the bundle it received, one bundle per reservation, so you can check every value before going live.

  5. 05

    Switch it on

    Turn the scenario on. From then on, each new booking starts it. Every module run counts as one operation, the unit Make deducts from your plan.

Triggers

The SuperHote triggers in Make

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

SuperHote1Watch After Booking

Watch After Booking

Instant trigger

In Make“Module triggered as soon as a reservation is created, and the reservation details will be sent.”

Watch After Booking starts your scenario the moment a guest creates a reservation, and hands Make the details of that stay as a bundle, one item that flows to the next module.

How it fires
instant, SuperHote calls Make through a webhook as soon as the booking exists, so there is no interval to wait for.
When to use it
any job that should begin with a new stay, such as briefing the housekeeping team or logging the guest in a shared sheet.
Watch out
it only sees new bookings; pair it with Watch After Booking Modified if later changes matter.
SuperHote2Watch After Booking Modified

Watch After Booking Modified

Instant trigger

In Make“Module triggered as soon as a reservation is modified in the SuperHote app, and the reservation details related to this modification will be sent.”

With Watch After Booking Modified, a copy of a stay kept in another tool stays accurate, because every edit made to a reservation in SuperHote sends Make the details tied to that change.

How it fires
instant, SuperHote alerts Make by webhook right after the edit.
When to use it
a guest shifts dates and the planning your cleaners follow, or the record in your spreadsheet, has to follow without anyone retyping it.
Watch out
make the next module update the existing record rather than add a new one, or each change will create a duplicate line.
SuperHote3Watch After Contract Sign

Watch After Contract Sign

Instant trigger

In Make“Module triggered once a contract is signed in SuperHote, and the reservation details related to this contract will be sent.”

You get a clean signal that the paperwork is done: Watch After Contract Sign fires once a guest signs a contract in SuperHote and passes along the reservation linked to it.

How it fires
instant, the signature itself triggers a webhook call from SuperHote to Make.
When to use it
releasing the next step of a stay only after signature, like sending arrival instructions or filing the booking with your records.
Watch out
Make describes what it sends as reservation details, with no mention of the signed file, so plan to fetch the document in SuperHote if you need it.
SuperHote4Watch After Payment

Watch After Payment

Instant trigger

In Make“Module that is triggered once a payment is processed in SuperHote, and the reservation details related to the payment will be sent”

Your accounting side learns about money as it lands: Watch After Payment reacts once SuperHote has processed a payment and delivers the reservation details that go with it.

How it fires
instant, SuperHote notifies Make by webhook as soon as the payment goes through.
When to use it
confirming a stay to the guest, flagging a paid booking to your team, or adding a line to the ledger you keep outside SuperHote.
Watch out
if SuperHote processes several payments for one reservation, each one starts its own run and consumes operations.
Need help

Need help automating SuperHote with Make?

A person reads every message.

FAQ

SuperHote and Make: frequent questions

01Is the SuperHote Make integration free?
Yes, SuperHote is a standard app in Make, available from the Free plan. That plan allows 2 active scenarios, runs of 5 minutes at most, files up to 5 MB and 512 MB of data transfer. Its 15 minute minimum interval applies to scheduled scenarios; SuperHote triggers are instant, so SuperHote calls Make directly. Paid plans (Core, Pro, Teams, Enterprise) lift the scenario cap and count usage in credits per month. Your SuperHote subscription is a separate matter that Make does not cover.
02What do you need to connect SuperHote to Make?
A SuperHote account and a Make account. Make's documentation lists no specific prerequisite for this app and no dedicated connection steps, so the generic flow applies: add a SuperHote module, click Create a connection, optionally name it, authorize Make on the SuperHote page or paste the key SuperHote provides, then click Save. The connection is then shared by all four SuperHote modules, so you only set it up once per account.
03Do SuperHote triggers in Make react in real time?
Yes. All four SuperHote modules are instant triggers, marked with a lightning badge in the editor. SuperHote calls Make through a webhook as soon as a booking is created or changed, a contract is signed or a payment is processed. You do not wait for the default 15 minute schedule, which only applies to scheduled triggers. Once your Run once test looks right, just remember to switch the scenario on.
04What if the SuperHote module you need is missing in Make?
It depends on what you need. The integration only offers four triggers and has no Make an API Call module, so Make cannot create, edit or search reservations in SuperHote. Make also notes that its documentation for this app is limited. For anything beyond the four events, check whether SuperHote offers another way to share its data, or ask the team for help designing a workaround with other apps in your scenario.
05Should you use Make or n8n for SuperHote?
It depends on your criteria. In Make, the four SuperHote triggers are ready to use without code, and the editor shows each bundle when you test with Run once, which suits someone starting out. The same app often has an n8n node too, so check what n8n offers for SuperHote before you decide. Compare the events covered, how each tool counts usage, and which one your team already knows; neither choice is right for every rental business.