Resources · Make integration

Quill Booking Make integrationAutomate Quill Booking with Make.

Every booking in Quill Booking can start a workflow somewhere else. The Quill Booking Make integration gives you 3 triggers that watch new, cancelled and rescheduled bookings. This guide shows service teams how to link the account and build a first scenario.

Try the Quill Booking integration on MakeSee the 3 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Quill Booking Make integration do?

It lets Make react to what happens in your Quill Booking calendar. You build a scenario, the automation Make runs, and it starts from one of 3 triggers: a booking is created, cancelled or rescheduled. What happens next is up to the modules of your other apps.

A client file that opens itself. Watch created bookings picks up each new appointment, and the next module can log it in the CRM or the spreadsheet your sales team already uses.

A free slot nobody misses. With Watch cancelled bookings, a cancellation can post a message to the team so someone offers the slot to a waiting client.

A schedule that stays in sync. Watch rescheduled Bookings catches a moved appointment and lets you update the record or warn the consultant.

Keep the limits in mind. All three modules are triggers: Quill Booking cannot receive data from Make, and there is no Make an API Call module to go further. Make also states that its own documentation for this app is limited. If you are still choosing a platform, read n8n vs Make, and when a scenario stops, Make troubleshooting covers the usual causes.

Connect

How do you connect Quill Booking to Make?

  1. 01

    Add a Quill Booking module

    In a scenario, click the + and search for Quill Booking. Pick any of its triggers, then click Create a connection. The connection is your Quill Booking account linked to Make once, then reused by every module of the app.

  2. 02

    Name it and authorize

    Give the connection a name if you manage several accounts, so you can tell them apart later. Then follow what Quill Booking asks for: either you approve access on its own page, or you paste the key the app gives you.

  3. 03

    Save and check

    Click Save. Back in the module, the connection now shows in the list, and the other two Quill Booking triggers can pick the same one without asking you to log in again.

First scenario

Your first scenario with Quill Booking

GoalWhen a client books an appointment in Quill Booking, Make passes the booking to the next app of your choice.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to place your first module.

  2. 02

    Pick Watch created bookings

    Search for Quill Booking, choose Watch created bookings and select the connection you made earlier, or click Create a connection if this is your first time.

  3. 03

    Add the next module

    Click the + on the right of the trigger and add a module from another app, such as your CRM. Map the booking data from the trigger into its fields; each booking reaches it as one bundle.

  4. 04

    Test with Run once

    Create a test booking in Quill Booking, then click Run once. Read the bundles each module received to confirm the mapping is right.

  5. 05

    Schedule and switch on

    Click the clock on the trigger to set the schedule, every 15 minutes by default, then switch the scenario on. It now runs by itself.

Triggers

Quill Booking triggers

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

Quill Booking1Watch cancelled bookings

Watch cancelled bookings

triggerIn the docs only

This trigger hands your scenario every cancelled booking, so the gap in the calendar turns into an action instead of a surprise. Each cancellation arrives as its own bundle.

How it fires
it is a scheduled trigger. Make checks Quill Booking on the scenario's schedule, not the moment the cancellation happens.
When to use it
to warn the person who would have run the meeting, or to release a slot you want to offer again.
Watch out
on the Free plan the shortest interval is 15 minutes, so a late cancellation can reach your team a little after the fact.
Quill Booking2Watch created bookings

Watch created bookings

triggerIn the docs only

New appointments become the starting point of your automation: Make collects each fresh booking and passes it down the scenario, ready to feed a CRM, a sheet or a team channel.

How it fires
scheduled. Make asks Quill Booking for new bookings on the scenario's schedule, every 15 minutes by default.
When to use it
as the first module of an intake flow, when every booked call should create a record or a task.
Watch out
each booking the trigger returns is processed by every module after it, and each of those runs is an operation counted on your plan. Filter early if only some bookings matter.
Quill Booking3Watch rescheduled Bookings

Watch rescheduled Bookings

triggerIn the docs only

When an appointment moves to another slot, this trigger brings the change into Make, which keeps the rest of your tools aligned with the new date without anyone copying it by hand.

How it fires
a scheduled trigger again. Make polls Quill Booking on the rhythm you set on the clock of the first module.
When to use it
to update the record your first scenario created, or to tell the consultant the meeting moved.
Watch out
Make has little documentation for this app, so run it once on a real change and read the bundle before you rely on the data it carries.
Need help

Need help automating Quill Booking with Make?

A person reads every message.

FAQ

Quill Booking and Make: frequent questions

01Is the Quill Booking Make integration free?
Yes. Quill Booking is a standard app in Make, so it works from the Free plan. That plan keeps 2 active scenarios, waits at least 15 minutes between two scheduled runs, stops a run after 5 minutes and caps transfer at 512 MB. Paid plans (Core, Pro, Teams and Enterprise) drop the minimum interval to 1 minute and allow unlimited active scenarios. Usage is counted in operations each month, and every Quill Booking bundle handled by a module counts as one. The page does not cover what Quill Booking itself charges.
02What is needed to connect Quill Booking to Make?
A Quill Booking account and a Make account. The documentation lists no other prerequisite. You add a Quill Booking module, click Create a connection, optionally name it, then either authorize Make on the Quill Booking page or paste the key the app provides, and click Save. Make notes that its documentation for this app is limited, so if the authorization screen differs from these generic steps, follow what Quill Booking shows and test the connection with Run once right after.
03Does the Quill Booking trigger fire instantly in Make?
No. All 3 Quill Booking triggers are scheduled: Make checks the app on the scenario's schedule instead of waiting for a signal from Quill Booking. A new scenario checks every 15 minutes by default, which is also the minimum on the Free plan. Paid plans let you go down to 1 minute. Make's documentation of this app is thin, so this type is inferred from the Watch names: the clock badge on the module confirms it. In practice, a booking, a cancellation or a move reaches your other apps at the next check rather than the second it happens.
04What if a Quill Booking module is missing in Make?
It depends on what you need. The app offers 3 triggers and no action, search or Make an API Call module, so Make cannot create or edit a booking in Quill Booking. You can still act on the data the triggers send by adding modules from your other apps. For anything the triggers do not cover, look at whether another tool in your stack holds the same information, or ask the team for help: the audit lasts 60 minutes and maps what is doable.
05Should you use Make or n8n for Quill Booking?
It depends on your criteria. On Make, Quill Booking comes with 3 scheduled triggers, works from the Free plan and has no module to write back to the app, which suits flows that start from a booking and push it elsewhere. Before choosing n8n, check whether it offers a node for Quill Booking and what that node can do, then compare both on the same use case. The two tools are not ranked here; the n8n vs Make comparison linked above lays out the criteria side by side.
Same platform

Other docs you might need on this stack.

Browse all integrations