Resources · Make integration

Bookafy Make integrationAutomate Bookafy with Make.

Bookings and customer records can move on their own once Bookafy talks to Make. The Bookafy Make integration gives you 13 modules: 3 triggers, 8 actions and 2 searches. This guide is for anyone running a calendar of client meetings, and it walks you from the API key to a working scenario.

Try the Bookafy integration on MakeSee the 13 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Bookafy Make integration do for you?

The Bookafy Make integration links your Bookafy account to Make, a visual tool where you build a scenario (the automation itself, a chain of steps) without writing code. Each step is a module: it watches Bookafy, books or changes an appointment, or looks up a customer. You pick the modules, Make runs them in order.

Every new client lands in your other tools. Start with Watch Customers, then send each person to your CRM, your mailing list or a shared sheet. Nobody retypes a name or an email address again.

Requests become booked slots. A lead fills in a form somewhere else; Create a Customer adds the person to Bookafy and Create an Appointment reserves the meeting. When plans change, Update an Appointment or Cancel an Appointment keeps the calendar honest.

Your team roster stays visible. Watch Users picks up the people on your Bookafy account, handy when a new colleague should also get access to other tools.

Know the limits before you start: the documentation lists 13 modules and nothing about quotas, and all 3 triggers work on a schedule, so Make checks Bookafy at intervals rather than being pinged by it. For anything the list misses, Make an API Call reaches the rest of the Bookafy API with the same connection. The same app often has an n8n node too; the n8n vs Make comparison helps you choose, the Make pricing page explains plans, and the Make training takes you further.

Connect

How do you connect Bookafy to Make?

  1. 01

    Copy your API key in Bookafy

    Log in to Bookafy, click the cog icon at the top right, then Settings. Open Integrations, then API, and copy the API Key value. Keep it somewhere safe, it opens your account to Make.

  2. 02

    Create the connection in Make

    Add any Bookafy module to your scenario and click Create a connection. A connection is your Bookafy account linked to Make once, then reused by every Bookafy module. You can give it a label in Connection name.

  3. 03

    Paste the key and save

    Paste the key into the API Key field and click Save. If Bookafy asks you to sign in and confirm access, do it. The module now shows your connection, and Make can read your Bookafy data.

First scenario

Build your first scenario with Bookafy

GoalWhen a request comes in from another app, Make adds the person as a Bookafy customer and books the appointment.

  1. 01

    Create a new scenario

    On the Scenarios page, create a new scenario and click the +. Pick the app where requests arrive, such as your form tool, and choose its module that watches new entries.

  2. 02

    Add Create a Customer

    Click the + on the right of that first module, search for Bookafy and choose Create a Customer. Link your account with Create a connection, then map the name and contact details from the form.

  3. 03

    Add Create an Appointment

    Add one more module, Create an Appointment, and map what it needs from the two modules before it. Each item passing between modules is a bundle: here, one request and one customer.

  4. 04

    Test with Run once

    Send a test entry through your form, then click Run once. Make runs the scenario a single time and shows the bundles each module received, so you can check the new customer and the booking in Bookafy.

  5. 05

    Schedule it and switch it on

    Open the clock on the first module: a new scenario runs every 15 minutes by default, and 15 minutes is the shortest gap on the Free plan. Choose your schedule, then switch the scenario on.

Triggers

Bookafy triggers: what starts your scenario

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

Bookafy1Watch Appointments

Watch Appointments

triggerIn the docs only

Watch Appointments brings your Bookafy appointments into Make, one bundle per appointment, so every booking can start its own chain of steps. It is the natural first module for anything built around the calendar.

How it fires
it is a scheduled trigger, so Make checks Bookafy on the scenario's schedule instead of hearing from Bookafy directly.
When to use it
you want each booking copied to a shared team calendar or a follow-up list without touching it by hand.
Watch out
every appointment it brings in runs the next modules and uses operations, the unit Make counts on your plan, so pick a schedule that matches how fast you really need to react.
Bookafy2Watch Customers

Watch Customers

triggerIn the docs only

With Watch Customers, the people stored in Bookafy flow into your scenario and can be copied anywhere else you keep contacts. Each customer arrives as a separate bundle, ready to be mapped into the next module.

How it fires
Make checks the app on the scenario's schedule; nothing is pushed from Bookafy the moment a customer appears.
When to use it
a clinic or a coaching practice wants every client who books online to show up in its CRM or newsletter tool too.
Watch out
this trigger looks at customers, not bookings; pick Watch Appointments when the meeting itself is what matters.
Bookafy3Watch Users

Watch Users

triggerIn the docs only

This one keeps an eye on the users of your Bookafy account, the staff members who take bookings, and passes each of them to the next module. It is the only module in the Users group, which makes it easy to spot.

How it fires
on a schedule, the clock badge on the module; Make asks Bookafy at each run of the scenario.
When to use it
a new colleague joins the booking team and should also get a seat in your chat tool or your internal directory.
Watch out
users are the people on your team, not your clients; client records come from Watch Customers.
Modules

Bookafy modules: what you can do from a scenario

Bookafy gives you 10 modules in 3 groups. For each one: what it does for you, when to reach for it, and what to watch out for.

Appointments

4 modules
Bookafy1

Create an Appointment

ActionIn the docs only

Books a new appointment in Bookafy straight from your scenario, so a slot gets reserved without anyone opening the calendar. You map the details from the modules placed before it.

When to use it
a request arrives through a form or a chat and should end up as a confirmed booking.
Watch out
a Run once test books a real appointment, so clean it up afterwards or test on a spare slot.
Bookafy2

Update an Appointment

ActionIn the docs only

Changes an appointment that already exists in Bookafy, keeping the calendar in line with what was agreed elsewhere. It works on one appointment at a time.

When to use it
a client moves a meeting through your support inbox and the booking has to follow.
Watch out
the module needs to know which appointment to change, so place Search Appointments or a trigger before it to get that appointment.
Bookafy3

Search Appointments

SearchIn the docs only

Looks through your Bookafy appointments and returns the matches, which lets a scenario find a booking before acting on it. A search can return zero, one or several appointments, each as its own bundle.

When to use it
you need the booking of a given client before updating or cancelling it.
Watch out
several results mean the next modules run once per match, which multiplies operations.
Bookafy4

Cancel an Appointment

ActionIn the docs only

Cancels a booking in Bookafy from inside the scenario, freeing the slot without a manual step. It pairs well with a search that finds the right appointment first.

When to use it
an order is refunded or a request is withdrawn in another tool, and the meeting attached to it should disappear.
Watch out
test it on a dummy booking, since Run once cancels real appointments.

Customers

5 modules
Bookafy5

Create a Customer

ActionIn the docs only

Adds a new customer to Bookafy using data from earlier modules, so the person exists before any booking is made. Names and contact details come from wherever the lead first appeared.

When to use it
a prospect signs up on your website or in your CRM and should be ready to book in Bookafy.
Watch out
run List Customers first if the same person may come in twice, or you may end up with duplicates.
Bookafy6

Update a Customer

ActionIn the docs only

Edits a customer already stored in Bookafy, so a change made in another tool reaches your booking records too. It targets one customer per run of the module.

When to use it
a client updates their phone number or email in your CRM and Bookafy should match.
Watch out
the module has to know which customer to edit; Get a Customer or List Customers placed before it supplies that.
Bookafy7

List Customers

SearchIn the docs only

Returns customers from your Bookafy account as a set of bundles, one per person, which is how a scenario checks who is already there. It is one of the 2 searches of the app.

When to use it
before creating a customer, to avoid adding someone twice, or to copy your client base into a sheet.
Watch out
every returned customer runs the following modules once, so a long list costs as many operations.
Bookafy8

Get a Customer

ActionIn the docs only

Fetches the record of one specific customer so later modules can use it, for example to fill an email or a CRM entry. Unlike List Customers, it aims at a single person you already identified.

When to use it
a trigger hands you an appointment and you want the full client record that goes with it.
Watch out
it needs a way to identify that customer, usually mapped from an earlier module.
Bookafy9

Delete a Customer

ActionIn the docs only

Removes a customer from Bookafy inside the scenario, which keeps your client list tidy when a contact should no longer be there. Use it deliberately, because the record goes away.

When to use it
a person asks to have their data erased and your process handles that request in another tool.
Watch out
a deletion does not come back; check that only the right customer reaches this module, and test with a dummy one.

Other

1 module
Bookafy10

Make an API Call

ActionIn the docs only

Reaches any endpoint of the Bookafy API from your scenario, reusing the connection you already created. It fills the gap when none of the ready-made modules does what you need.

When to use it
a Bookafy feature you rely on has no ready-made module in Make.
Watch out
you describe the request yourself, so keep the Bookafy API documentation open, and try it with Run once before switching the scenario on.
Need help

Need help automating Bookafy with Make?

A person reads every message.

FAQ

Bookafy and Make: common questions

01Is the Bookafy Make integration free?
Yes, Bookafy is a standard app in Make, so it works on the Free plan. That plan gives you 2 active scenarios, a shortest gap of 15 minutes between 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) lower the gap 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 each bundle. Bookafy has its own subscription, which this page does not cover.
02What do you need to connect Bookafy to Make?
You need a Bookafy account and its API key. In Bookafy, click the cog icon at the top right, then Settings, Integrations and API, and copy the API Key value. In Make, add a Bookafy module, click Create a connection, give it a name if you like, paste the key into the API Key field and click Save. If Bookafy asks you to confirm access, accept. The connection is then reused by all 13 Bookafy modules in your scenarios.
03Do Bookafy triggers in Make fire instantly?
No. Watch Appointments, Watch Customers and Watch Users are scheduled triggers: Make checks Bookafy on the scenario's schedule, shown by the clock badge on the module. A new scenario runs every 15 minutes by default, and the Free plan cannot go below 15 minutes. Paid plans allow a check every minute. None of the 3 Bookafy triggers is instant, so a booking reaches the scenario at the next scheduled check rather than the moment it is made.
04What if a Bookafy module you need is missing in Make?
Use Make an API Call. It calls any endpoint of the Bookafy API from your scenario with the connection you already set up, so you are not limited to the ready-made modules. You write the request yourself, which takes a look at the Bookafy API documentation. The Make documentation for Bookafy lists no quota or numeric limit, so there is nothing specific to plan around there, but the limits of your Make plan still apply to each run.
05Should you use Make or n8n for Bookafy?
It depends on the tool your team already knows. Bookafy is available as a standard app in Make with 13 modules covering appointments, customers and users, plus Make an API Call for the rest. The same app often has a node in n8n as well. Compare which Bookafy operations each tool offers against the scenario you have in mind, and check where your other apps are already connected. The comparison page on this site lays out the differences between the two platforms in detail.
Same platform

Other docs you might need on this stack.

Browse all integrations