Resources · Make integration

BookingKoala Make integrationAutomate BookingKoala with Make.

What happens in your BookingKoala account after a booking lands? The BookingKoala Make integration gives you 19 triggers and 2 actions to pass that news to your other tools. This guide shows how to link the account with an API key and build a first working scenario.

Try the BookingKoala integration on MakeSee the 21 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the BookingKoala Make integration do?

The BookingKoala Make integration links your BookingKoala account to Make, a visual tool where you build a scenario: an automation made of modules, each one a brick that watches, creates or calls something. BookingKoala brings 21 modules: 19 triggers that notice what changes in your account and 2 actions that write to it.

Keep the team in the loop on every new job. Watch New Booking hands each fresh booking to the next module, so a cleaning company can post it in a team chat or add a row to a planning sheet without anyone copying details by hand.

Chase money problems early. Watch Declined Booking Charge and Watch Invoice Charge tell you when a payment fails or goes through, which lets the office manager follow up the right customer instead of scanning the dashboard.

Feed prospects straight into BookingKoala. Create Lead turns a request collected elsewhere, a web form or an ad lead, into a lead in BookingKoala, ready for the sales follow-up.

Make does not cover everything BookingKoala can do: when a listed module is missing, Make an API Call reaches other endpoints with the same connection. New to the tool? The Make review gives the big picture, and n8n vs Make helps if you are weighing the two platforms. For a hands-on start, see the Make training.

Connect

How do you connect BookingKoala to Make?

  1. 01

    Generate your API key in BookingKoala

    In BookingKoala, open Settings > General > Apps and Integrations and scroll to the Make section. Click Click Here, switch the red Disabled button on, confirm with Yes, then press Generate API Key and copy the key.

  2. 02

    Add a BookingKoala module in Make

    Inside your Make scenario, add any BookingKoala module and click Create a connection. A connection is your BookingKoala account linked to Make once, then reused by every BookingKoala module. The Connection name field is optional.

  3. 03

    Paste the key and save

    Paste the API key you copied into the credentials field, or follow the on-screen instructions, and save. Make can now read your BookingKoala data, and the module shows the connection you just created.

First scenario

Your first scenario: BookingKoala Make integration

GoalWhen a prospect fills in a form in another app, Make creates a lead in BookingKoala.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big +. The first module you add is the one that starts everything, here the app where your prospects leave their request.

  2. 02

    Set up the starting module

    Search your form or lead source by name, pick its trigger, click Create a connection and fill its fields. Each request it picks up becomes a bundle: one item passed to the next module.

  3. 03

    Add Create Lead

    Click the + on the right of that module, search BookingKoala and pick Create Lead. Link your account, then map the answers from the form bundle into the fields Make lists.

  4. 04

    Test with Run once

    Send a test entry through your form, then click Run once. Make runs the scenario one time and shows the bundles each module received, so you can open BookingKoala and check the new lead.

  5. 05

    Schedule and switch on

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

Triggers

BookingKoala triggers in Make

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

BookingKoala1Watch Booking Card Hold

Watch Booking Card Hold

triggerIn the docs only

Spot bookings where BookingKoala holds an amount on the customer's card, and send each one on to the rest of your scenario as a bundle you can map.

How it fires
scheduled, Make checks the app on the scenario's schedule and picks up the card holds added since its last look.
When to use it
your office wants a heads-up whenever a hold is placed before a job, to confirm the booking with the customer.
BookingKoala2Watch Cancelled Booking

Watch Cancelled Booking

triggerIn the docs only

Freeing a slot starts with knowing it is free: this trigger passes every booking cancelled in BookingKoala to the next module of your scenario.

How it fires
scheduled, Make looks at the app on the scenario's schedule, so a cancellation shows up at the next check.
When to use it
you want the provider warned in a chat app, or the slot flagged in a planning sheet, as soon as Make sees the cancellation.
BookingKoala3Watch Charged Booking

Watch Charged Booking

triggerIn the docs only

Get a clean signal each time a booking is actually charged, which is handy for bookkeeping that should only move once money is in.

How it fires
scheduled; Make checks the app on the scenario's schedule and returns the newly charged bookings found since the previous run.
When to use it
you log paid jobs in a spreadsheet or accounting tool and prefer not to copy each charge by hand.
Watch out
every booking returned is a bundle, and each module that processes it uses one operation.
BookingKoala4Watch Completed Booking

Watch Completed Booking

triggerIn the docs only

Close the loop after the work is done: bookings marked as completed come out of this trigger ready for a follow-up step.

How it fires
scheduled, Make checks BookingKoala on the scenario's schedule instead of waiting for a push from the app.
When to use it
a finished job should trigger a thank-you email or a review request to the customer, without anyone remembering to send it.
BookingKoala5Watch Declined Booking Charge

Watch Declined Booking Charge

triggerIn the docs only

Catch failed payments before they turn into awkward calls: this trigger surfaces booking charges that BookingKoala could not collect.

How it fires
scheduled; Make checks the app on the scenario's schedule, so the declined charge reaches you at the next check, not the second it fails.
When to use it
the person who handles billing needs a task or a message to contact the customer and update the card.
BookingKoala6Watch Deleted Booking

Watch Deleted Booking

triggerIn the docs only

Keep your other tools honest when a booking disappears from BookingKoala: this trigger reports each deleted booking to your scenario.

How it fires
scheduled, with Make reading the app on the scenario's schedule and returning deletions found since the last check.
When to use it
a shared calendar or a planning sheet still shows the job and should be cleaned up.
Watch out
test with Run once and read what the bundle actually holds before mapping it to a delete step elsewhere.
BookingKoala7Watch Deleted Provider

Watch Deleted Provider

triggerIn the docs only

When a provider is removed from your BookingKoala team, this trigger lets the rest of your stack know so access and lists stay in sync.

How it fires
scheduled; Make checks the app on the scenario's schedule and picks up providers deleted since its previous run.
When to use it
an HR sheet, a team chat channel or a payroll list should drop the person once they leave BookingKoala.
BookingKoala8Watch Invoice Charge

Watch Invoice Charge

triggerIn the docs only

Know when an invoice gets paid by card, not just issued, and pass that payment on as a bundle to the next module.

How it fires
scheduled, meaning Make checks the app on the scenario's schedule rather than hearing from BookingKoala directly.
When to use it
you reconcile invoice payments in an accounting tool and want each charge recorded there once it happens.
Watch out
Watch New Invoice and Watch Updated Invoice cover other moments of the invoice, so pick the one that matches your step.
BookingKoala9Watch New Booking

Watch New Booking

triggerIn the docs only

A natural first trigger: every booking created in BookingKoala flows into Make, ready to be mapped into another tool.

How it fires
scheduled; Make checks the app on the scenario's schedule, every 15 minutes by default on a new scenario.
When to use it
a new job should land in the provider's calendar, a team chat or a job sheet without retyping it.
Watch out
on the Free plan, 15 minutes is the shortest gap between two scheduled runs.
BookingKoala10Watch New Customer

Watch New Customer

triggerIn the docs only

Grow your contact list without exports: each customer added to BookingKoala comes out of this trigger with the details you can map.

How it fires
scheduled, Make checks the app on the scenario's schedule and returns customers created since the last check.
When to use it
your newsletter tool or CRM should know about a customer from the first booking onward.
Watch out
a customer edited later will not come back here; that is the job of Watch Updated Customer.
BookingKoala11Watch New Invoice

Watch New Invoice

triggerIn the docs only

Mirror your billing elsewhere: each invoice created in BookingKoala is handed to the next module, so you can file or send it from another tool.

How it fires
scheduled; Make checks the app on the scenario's schedule instead of receiving a webhook from BookingKoala.
When to use it
the accountant works in a separate tool and needs each new invoice there, or a finance channel should see it appear.
BookingKoala12Watch New Provider

Watch New Provider

triggerIn the docs only

Onboarding goes faster when nobody has to remember it: this trigger fires for every provider added to your BookingKoala account.

How it fires
scheduled, Make checks the app on the scenario's schedule and picks up the providers created since it last looked.
When to use it
a new cleaner or technician should get a welcome message, a row in the team sheet or an invite to the team chat.
BookingKoala13Watch New Quote

Watch New Quote

triggerIn the docs only

Quotes are warm leads, and this trigger brings each new one from BookingKoala into Make while the prospect is still interested.

How it fires
scheduled; Make checks the app on the scenario's schedule, so the quote shows up at the next check.
When to use it
sales wants a reminder task in a CRM, or a message in the team chat, for every quote that still needs a follow-up.
Watch out
run the scenario once with Run once to see which details the quote bundle carries before mapping.
BookingKoala14Watch New Rating

Watch New Rating

triggerIn the docs only

Hear what customers say right after the job: each rating left in BookingKoala becomes a bundle you can route to the right person.

How it fires
scheduled, Make checks the app on the scenario's schedule and returns the ratings added since the last run.
When to use it
a manager wants low scores in a team chat to call the customer back, or good ones logged for the provider.
Watch out
every rating becomes its own bundle, so each module after this one runs once per rating and counts operations.
BookingKoala15Watch Provider Payout

Watch Provider Payout

triggerIn the docs only

Track money going out to your team: this trigger reports provider payouts recorded in BookingKoala to the next module.

How it fires
scheduled; Make checks the app on the scenario's schedule and picks up the payouts made since its previous check.
When to use it
your bookkeeping sheet or accounting tool should log each payout, or the provider should get a short confirmation message.
BookingKoala16Watch Updated Booking

Watch Updated Booking

triggerIn the docs only

Bookings move: a new time, a new address, a new provider. This trigger sends each changed booking on so your other tools follow.

How it fires
scheduled, Make checks the app on the scenario's schedule and returns bookings edited since the last check.
When to use it
a synced calendar or job sheet must reflect the change before the provider heads out.
Watch out
cancellations and completions have their own triggers; use those when the status is what matters.
BookingKoala17Watch Updated Customer

Watch Updated Customer

triggerIn the docs only

Stale contact data costs missed jobs; this trigger passes along every customer whose record changes in BookingKoala.

How it fires
scheduled; Make checks the app on the scenario's schedule and picks up customers edited since its last run.
When to use it
a customer updates a phone number or address and your CRM or mailing list should carry the same details.
Watch out
pair it with Watch New Customer if you also want brand new records.
BookingKoala18Watch Updated Invoice

Watch Updated Invoice

triggerIn the docs only

Invoices rarely stay as first issued, and this trigger hands each edited one to Make so the copy elsewhere stays accurate.

How it fires
scheduled, Make checks the app on the scenario's schedule and returns the invoices changed since the previous check.
When to use it
an amount or a line is corrected in BookingKoala and your accounting tool or finance sheet must match.
BookingKoala19Watch Updated Provider

Watch Updated Provider

triggerIn the docs only

Changes to a provider's profile reach the rest of your stack through this trigger, one bundle per edited provider.

How it fires
scheduled; Make checks the app on the scenario's schedule and picks up providers edited since it last ran.
When to use it
a technician changes contact details or availability and the team directory or payroll sheet should update itself.
Watch out
a removed provider shows up in Watch Deleted Provider, not here.
Modules

BookingKoala actions in Make

BookingKoala gives you 2 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

BookingKoala1

Create Lead

ActionIn the docs only

Create Lead writes a lead into BookingKoala from data another module gives it, so a prospect captured outside the app lands where your sales follow-up happens.

When to use it
a web form, an ad platform or a chat tool collects requests and you want each one in BookingKoala without retyping.
Watch out
the fields appear once the connection exists; run the scenario with Run once and check the lead in BookingKoala.
BookingKoala2

Make an API Call

ActionIn the docs only

Make an API Call is the way out when the 21 listed modules fall short: it calls any endpoint of the BookingKoala API with the connection you already set up.

When to use it
you need to read or change something no other BookingKoala module covers in Make.
Watch out
you describe the request yourself, so keep the BookingKoala API documentation open while you build it.
Need help

Need help automating BookingKoala with Make?

A person reads every message.

FAQ

BookingKoala Make integration: common questions

01Is the BookingKoala Make integration free?
Yes, BookingKoala is a standard app in Make, so it works from the Free plan. The Free plan allows 2 active scenarios, a minimum of 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 lower the interval to 1 minute and remove the limit on active scenarios. You still need your own active BookingKoala account, which is billed by BookingKoala, not by Make.
02What do you need to connect BookingKoala to Make?
You need an active BookingKoala account with access to an API key. In BookingKoala, open Settings, then General, then Apps and Integrations, find the Make section, click Click Here, switch the red Disabled button on, confirm with Yes and press Generate API Key. In Make, add a BookingKoala module, click Create a connection and paste that key. The connection is then reused by every BookingKoala module in your scenarios. Once linked, Make lists the objects it can read in each module.
03Do BookingKoala triggers in Make work in real time?
No. The Make docs list the 19 BookingKoala triggers without a description; judging by their Watch names, they are scheduled triggers: Make checks BookingKoala on the scenario's schedule rather than receiving a webhook, and the module carries the clock badge in the editor. A new scenario checks every 15 minutes by default. On the Free plan, 15 minutes is also the shortest interval, while paid plans go down to 1 minute. Plan your scenarios for a short delay between the event and the reaction. Test each scenario with Run once before switching it on.
04What if a BookingKoala module you need is missing in Make?
Use Make an API Call. BookingKoala has this module in Make, and it can call any endpoint of the BookingKoala API with the same connection as the other modules. That covers what the 19 triggers and Create Lead do not, such as reading or updating a record type with no dedicated module. You write the request yourself, so check the BookingKoala API documentation first. The same connection means no extra setup.
05Should you use Make or n8n for BookingKoala?
It depends on the tool your team already uses. In Make, BookingKoala comes with 21 modules, a connection by API key and a visual editor where you test with Run once. The same app often has an n8n node too, so check whether it covers the bookings, invoices and providers you care about before choosing. Neither tool is ranked here: compare the modules each one offers for your case and pick the one your team will maintain.
Same platform

Other docs you might need on this stack.

Browse all integrations