Resources · Make integration

Beds24 Make integrationAutomate Beds24 with Make.

What if every booking in Beds24 could start its own follow-up without you copying anything? The Beds24 Make integration gives you 1 module, a scheduled trigger that watches bookings. This page shows how to connect your account, build a first scenario and pass each booking on to your other tools.

Try the Beds24 integration on MakeSee the 1 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Beds24 Make integration do for you?

The Beds24 Make integration links your Beds24 account to Make so that bookings can start a scenario, which is the automation you build in Make as a chain of modules. A module is one brick of that chain. On the Beds24 side there is exactly one: Watch Bookings, which picks up bookings and hands each one to the rest of your flow.

Because Beds24 only brings a trigger, the value comes from what you plug in after it. Here are three setups you could build, as examples. A team log: Watch Bookings passes every booking to a spreadsheet app, so the front desk and the owner read the same list. A cleaning handoff: the same trigger feeds a messaging app, and whoever prepares the rooms sees each stay appear. A guest file: bookings flow into a CRM so repeat guests are easy to spot.

Each booking travels as a bundle, meaning one item passed from a module to the next. What Make cannot do here is write back to Beds24: the documentation lists no action, no search and no Make an API Call module for this app, so changing a booking still happens inside Beds24.

The trigger is scheduled. Make checks Beds24 on the scenario's schedule, every 15 minutes by default, rather than being called the second a booking lands. If you are new to the editor, the Make training walks through modules and mapping, and Make pricing explains how runs are counted. The same app often has an n8n node too; n8n vs Make lays out how the two tools differ.

Connect

How do you connect Beds24 to Make?

  1. 01

    Add the Beds24 module

    In your scenario, click the +, search for Beds24 and pick Watch Bookings. The module asks for a connection, which is your Beds24 account linked to Make once and reused afterwards. Click Create a connection.

  2. 02

    Name the connection

    Giving the connection a name is optional, but it helps later. If you manage more than one Beds24 account, a clear name tells you which one a scenario reads, instead of guessing from a default label.

  3. 03

    Authorize and save

    Make then asks you to authorize it on the Beds24 page, or to paste the key Beds24 gives you, depending on what the window shows. Complete that step and click Save. The connection now appears in the module.

First scenario

Build your first scenario with Beds24

GoalWhen a booking shows up in Beds24, Make passes it to the next app of your choice.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + in the middle of the canvas. That empty circle becomes your first module, the one that starts everything.

  2. 02

    Place the Beds24 trigger

    Search for Beds24, choose Watch Bookings and select the connection you just made. Fill the fields the module shows; Make lists what it can read from your account once the connection exists.

  3. 03

    Add the next app

    Click the + on the right of the Beds24 module and pick where bookings should go: a sheet, a chat, a CRM. Map the booking data from Watch Bookings into the fields of that module.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles each module received, so you can open a booking and check that the right data reached the second app.

  5. 05

    Schedule and switch on

    Open the clock on the first module to set the schedule, every 15 minutes by default, then switch the scenario on. From there, Make checks Beds24 at that pace without you clicking anything.

Triggers

The Beds24 trigger

1 module starts a scenario when something happens in Beds24. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Beds24 as soon as it happens.

Beds241Watch Bookings

Watch Bookings

Scheduled trigger

In Make“Watches for bookings.”

You get each Beds24 booking delivered to your scenario as its own bundle, ready to be copied, announced or filed by the modules you add after it. It is the only Beds24 module in Make, so every Beds24 scenario opens here.

How it fires
scheduled: Make checks the app on the scenario's schedule, every 15 minutes by default, or as often as your plan allows.
When to use it
whenever a booking should trigger work elsewhere, like warning the housekeeping team or adding a line to a shared sheet.
Watch out
bookings are picked up at the next scheduled check, not instantly, so leave room for that delay in anything guests will see.
Need help

Need help automating Beds24 with Make?

A person reads every message.

FAQ

Beds24 and Make: frequently asked questions

01Is the Beds24 Make integration free?
Yes, Beds24 is a standard app in Make, so it works on the Free plan. That plan has limits worth knowing: 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) bring the interval down 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.
02What do you need to connect Beds24 to Make?
A Beds24 account and a Make account. The Make documentation for Beds24 lists no prerequisite and no dedicated connection steps, so the generic flow applies. Add Watch Bookings, click Create a connection, optionally name it, then either authorize Make on the Beds24 page or paste the key Beds24 provides, depending on what the window asks. Click Save and the connection is stored for any later Beds24 module in any scenario.
03Does the Beds24 trigger in Make work in real time?
No. Watch Bookings is a scheduled trigger, marked with a clock badge in the editor. Make checks Beds24 on the scenario's schedule, which is every 15 minutes by default for a new scenario. On the Free plan the shortest interval is 15 minutes; paid plans go down to 1 minute. A booking made just after a check therefore waits for the next one before your scenario sees it, which matters for anything time sensitive.
04What if the Beds24 module you need is missing in Make?
It depends on what you need. The Beds24 app in Make only watches bookings: there is no action, no search and no Make an API Call module to fill the gap. If you need to change a booking, update a guest or cancel a stay, that part stays manual inside Beds24, while Make carries the news to your other tools. The team can look at your case and suggest the simplest setup through the help form on this page.
05Should you use Make or n8n for Beds24?
It depends on the tool you already use. The same app often has an n8n node, so check both catalogs for what Beds24 offers in each before choosing. On the Make side, the facts are simple: one scheduled trigger, Watch Bookings, available on the Free plan, with a visual editor where you test through Run once. Pick the platform where the rest of your automations already live, since each booking will mostly feed other apps.
Same platform

Other docs you might need on this stack.

Browse all integrations