SuperHote (v1) Make integrationAutomate SuperHote (v1) with Make.
Can Make push your rental events into SuperHote without a line of code? The SuperHote (v1) Make integration offers 4 action modules and no trigger. This page is for hosts and property managers: it shows how to link the account, build a first scenario and read each module with care.
Verified Trustpilot reviews · AI, automation & growth agency
What does the SuperHote (v1) Make integration let you automate?
The SuperHote (v1) Make integration links your SuperHote account to Make so that a scenario, the automation you build in Make, can call one of 4 SuperHote modules. A module is one brick of that scenario. All four are actions, so something else has to start the run: a trigger from another app, or the schedule Make puts on the first module.
A booking made elsewhere reaches SuperHote. Picture a form or a sales tool that records a new stay. Its trigger opens the scenario, and After Booking passes the stay on to SuperHote. When the stay changes later, After Booking Modified is the module whose name matches that moment.
Paperwork and money follow the same path. The names After Contract Sign and After Payment point to a signed rental agreement and a settled payment. A signature tool or a billing tool can open the flow, and the matching SuperHote module closes it.
What Make does not tell you. The official documentation says openly that it lacks public information on SuperHote (v1): it lists no fields, no connection prerequisite and no official description for the modules. The purpose written above comes from each module name only, so open the module in the editor and check what it asks before you rely on it. There is also no Make an API Call module for this app.
New to the editor? The Make training walks through the basics, and n8n vs Make helps if you are still choosing a tool. When a run fails, keep Make troubleshooting close.
How do you connect SuperHote (v1) to Make?
- 01
Open a SuperHote module
In your scenario, add any of the 4 SuperHote (v1) modules, then click Create a connection. A connection is your SuperHote account linked to Make once, then reused by every SuperHote module you add later.
- 02
Name the connection
Giving the connection a name is optional, yet it pays off when you manage more than one property account. A clear label lets you pick the right account in each module without guessing which login sits behind it.
- 03
Authorize Make and save
Depending on what SuperHote shows, either approve Make on the SuperHote page that opens or paste the key that SuperHote gives you. Then click Save, and the module can use your account.
Your first scenario with SuperHote (v1)
GoalWhen another app records a new stay, Make sends it to SuperHote with After Booking.
- 01
Create the scenario
From the Scenarios page, create a new scenario and click the + to add the first module. Since SuperHote has no trigger, this first module belongs to the app where your stays begin.
- 02
Add the SuperHote module
Click the + on the right of that first module, search for SuperHote (v1) and pick After Booking. Select the connection you created, or click Create a connection if you skipped that part.
- 03
Map the booking data
Fill the fields the module shows by mapping data from the first module. The documentation lists none, so read each field label carefully and map only what clearly matches your booking.
- 04
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, a bundle being one item passed along, here one stay.
- 05
Schedule and switch on
On the first module, set the schedule, every 15 minutes by default, then switch the scenario on. From then on, every new stay flows into SuperHote without you copying it by hand.
What each SuperHote (v1) module is for
SuperHote (v1) gives you 4 modules. For each one: what it does for you, when to reach for it, and what to watch out for.
After Booking
ActionIn the docs onlyUse this action when a stay is born outside SuperHote and you are tired of typing it twice. Its name ties it to the moment a booking exists; that reading is a deduction, since Make gives no description.
After Booking Modified
ActionIn the docs onlyPick this one when a stay already exists and something about it moved: new dates, a different guest count, another unit. Its name places it after a change, not after the first booking, which keeps it apart from After Booking.
After Contract Sign
ActionIn the docs onlyHere the moment that matters is a signed rental agreement, and the module lets that event continue into SuperHote instead of staying in your signature tool. Only its name says so, since Make offers no official description.
After Payment
ActionIn the docs onlyMoney received is the event behind this module, going by its name. Place it at the end of a flow that starts in your billing or payment app, so SuperHote learns that a stay has been paid for.
Need help automating SuperHote (v1) with Make?
A person reads every message.
