- Home
- Resources
- Integrations
- BookingKoala
BookingKoala Zapier integrationAutomate BookingKoala with Zapier.
The BookingKoala Zapier integration gives you 19 triggers and 1 action, and every trigger is instant: bookings, invoices, payments, customers, providers and ratings reach Zapier as they happen. Here is what each one does, what it costs and where it trips.
Verified Trustpilot reviews · AI, automation & growth agency
What the BookingKoala Zapier integration actually does
It connects your BookingKoala account, the booking platform built for service businesses like cleaning, dog walking, spas or tutoring, to Zapier. Each event in BookingKoala (a booking, a payment, a new provider, a rating) can then start an automation, and Zapier can add leads back into BookingKoala.
The big news first: all 19 triggers are instant. BookingKoala tells Zapier the moment something happens, so even on the free plan nothing waits for a 15-minute check. It is the main reason to use this integration.
Three results people build with it. Payment problems handled at once: Booking Charge Declined fires as soon as a card is refused, so the next step can alert whoever chases payments. A team roster that stays current: New Provider, Provider Updated and Provider Deleted follow your cleaners or walkers from hiring to departure. Lost bookings turned into leads: Booking Cancelled plus Create Lead keeps the customer in your follow-up list.
What Zapier does not do here matters as much. There is a single action, so a Zap cannot create a booking, issue an invoice or edit a customer in BookingKoala. There is no search step either. Most of the work goes outward: BookingKoala starts the Zap, another app does the action. For the same app on the other platform, see the BookingKoala Make integration.
Zapier words, in plain English
Six words come back throughout this page. Here they are once.
- Zap
- The automation you build in Zapier: one starting event, then one or more steps that run every time that event happens.
- Trigger
- The event that starts the Zap, like a new booking in BookingKoala. Once the Zap is on, Zapier waits for it.
- Action
- What the Zap does after it starts: the step that writes, sends or saves something for you in an app.
- Task
- What Zapier bills: one action your Zap completes successfully. Your plan counts tasks and nothing else.
- Instant vs polling
- Instant means the app calls Zapier itself when the event happens. Polling means Zapier checks on a timer. BookingKoala is all instant.
- Filter
- A step that lets the Zap carry on only when what arrived meets your condition, and stops it quietly otherwise.
What a BookingKoala Zap really costs
BookingKoala is not a premium app: it runs on the free plan. You pay in tasks, and the trigger never costs one.
- Free plan100 tasks a month, unlimited Zaps
- Free plan Zap size2 steps: one trigger, one action
- BookingKoala triggers19 instant, never wait for a check
- Premium appNo, BookingKoala works on Free
Every successful action counts as one task, each on its own. A Zap that creates a lead for each quote spends one task per quote. A failed action is not counted, and a few apps or actions take more than one task. The free plan's real limit is the Zap's size: one trigger, one action, nothing more. A filter or a second action makes it multi-step, and that needs a paid plan. The interval grid below only applies to polling triggers, so none of it slows BookingKoala down.
Connect BookingKoala to Zapier in three steps
- 01
Open the Apps page
In your Zapier account, go to Apps and click + Add connection. A connection is your BookingKoala account linked to Zapier once, then reused by every step that touches BookingKoala.
- 02
Pick BookingKoala
Type BookingKoala in the search box of the dialog, select it, then click Add connection. You need an existing BookingKoala account first: Zapier does not create one for you.
- 03
Sign in and grant access
Sign in to BookingKoala in the tab that opens and let Zapier into the account. If the Zap touches data you do not own yourself, check first that your account has read or write rights on it.
Your first Zap: turn cancellations into leads
GoalWhen a booking is cancelled in BookingKoala, keep the customer as a lead, but only for the cancellations you choose.
- 01
Build: pick the trigger
In the editor, choose BookingKoala as the app and
Booking Cancelledas the event, then select your connection. The lightning bolt shows the trigger is instant. - 02
Test the trigger
Run the test: Zapier brings back the three most recent cancellations of the account. Pick a real one so the next steps map real values.
- 03
Add the filter
Add a Filter step. Pick one of the fields the test record shows, a rule, and the value to compare with. Use a text rule on text and a number rule on numbers.
- 04
Add the action
Add
Create Lead. In the test record, find the field that holds the customer's email address and map it into Email, the only required field. If the record has no such field, this Zap cannot work as built. - 05
Test, then Publish
Test each step and read what came back, then click Publish. With a filter, this is a multi-step Zap, so it needs a paid plan.
The 19 BookingKoala triggers
19 events start a Zap when something happens in BookingKoala, and 19 of them are instant: the app calls Zapier straight away, whatever your plan.
Booking Card Hold
Instant triggerIn Zapier“Triggered when booking's card put on hold.”
Fires when BookingKoala puts a hold on the card attached to a booking. It tells you the money is reserved, before any charge actually goes through.
Booking Charged
Instant triggerIn Zapier“Triggered when booking is charged.”
Starts the Zap once a booking has been charged. It is the event to rely on when your bookkeeping needs money that really came in, not money promised.
Booking Charge Declined
Instant triggerIn Zapier“Triggered when booking charge is declined.”
Reacts when the charge on a booking is refused. This is the trigger that saves revenue, because it reaches you while the customer still remembers the job.
Booking Completed
Instant triggerIn Zapier“Triggers when a booking is completed.”
Goes off when a booking is marked as completed. It marks the end of the service, which makes it the natural moment for anything that comes after the job.
Booking Cancelled
Instant triggerIn Zapier“Triggered when booking is cancelled.”
Triggers when a booking is cancelled. The customer is still known, the slot is now free, and both facts are worth acting on quickly.
New Invoice
Instant triggerIn Zapier“Triggered when invoice is created.”
Fires as soon as an invoice is created in BookingKoala, before anyone has paid it. It is the starting point for anything that tracks money owed.
Customer Updated
Instant triggerIn Zapier“Triggers when a customer is updated (does not trigger on Notes, Addresses, or Billing Info).”
Starts when a customer profile changes. It does not fire on everything, though: edits to Notes, Addresses or Billing Info are left out.
Booking Deleted
Instant triggerIn Zapier“Triggered when booking is deleted.”
Deleting a booking in BookingKoala, rather than cancelling it, is what sets this off. It is a separate event from a cancellation, so a Zap built on Booking Cancelled will not see it.
Charge Invoice
Instant triggerIn Zapier“Triggered when invoice is partially paid/ fully paid.”
Fires when an invoice gets paid, whether the payment is partial or full. One invoice can therefore start the Zap several times.
New Booking
Instant triggerIn Zapier“Triggers when a booking is created.”
A booking being created is all it takes: the Zap starts that moment. For most service businesses this is the heartbeat of the account, the event everything else depends on.
New Customer
Instant triggerIn Zapier“Triggers when a customer is created.”
Reacts when a customer is created in BookingKoala. It brings a fresh contact into the Zap, ready to be added wherever you keep your customer list.
New Provider
Instant triggerIn Zapier“Triggers when a provider is created.”
Fires when a provider is created, meaning a cleaner, walker, therapist or tutor joins your team in BookingKoala.
New Quote
Instant triggerIn Zapier“Triggered when quote is created.”
Every new quote created in BookingKoala starts this one. A quote is a customer showing intent without booking yet, which makes it an event worth catching quickly.
New Rating
Instant triggerIn Zapier“Triggers when a customer rates your service.”
Customer feedback lands here: the Zap starts when a customer rates your service. It is the direct line between what customers think and the people who can act on it.
Provider Deleted
Instant triggerIn Zapier“Triggers when a provider is deleted.”
Removing a provider from BookingKoala sets this trigger off. Use it to close what the provider had access to outside the platform.
Provider Payout
Instant triggerIn Zapier“Triggers when provider payments paid”
Payments to your providers are the subject here: the Zap starts once one is marked as paid. It follows the money going out to your team, the mirror of the charges coming in.
Provider Updated
Instant triggerIn Zapier“Triggers when a provider profile is updated.”
Any update to a provider profile in BookingKoala sets this off. It keeps any list of your team kept outside the platform in step with what is inside it, without anyone retyping changes.
Booking Updated
Instant triggerIn Zapier“Triggers when a booking is updated.”
Fires each time a booking is updated, for example a new date or a change of service. It lets whatever copy you keep elsewhere follow the change.
Update Invoice
Instant triggerIn Zapier“Triggered when invoice is updated.”
Edits to an existing invoice in BookingKoala start the Zap. It complements New Invoice, which only sees the creation.
The BookingKoala action
BookingKoala gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Create Lead
ActionIn Zapier“Creates a Lead in the system.”
Adds a lead to BookingKoala. It is the only way a Zap can write into the platform, and the only field it insists on is Email.
When a BookingKoala Zap breaks
Zapier attaches no help article of its own to BookingKoala, and no app-specific limit is documented. What breaks is general Zapier behaviour, applied to a booking platform.
Four cases to know before you build, one of them tied to its update events. If a Zap stops for a reason that is not here, the Zapier troubleshooting guide is the next stop.
Past bookings are never sent
A Zap only reacts to what happens after you publish it. The bookings, invoices and customers already in BookingKoala stay where they are: moving them is a separate job.Some customer edits stay silent
Customer Updated ignores changes to Notes, Addresses and Billing Info. A Zap waiting for a new address will simply never start.A bulk import held back
After a migration or a bulk import, BookingKoala can send a sudden flood of events. Zapier's flood protection may hold them back instead of running everything.Update triggers fire often
Booking Updated, Update Invoice and Charge Invoice can start several times for one record. Each run that ends in an action is a task, so watch the count.
Need help automating BookingKoala with Zapier?
A person reads every message.



