Webhooks for Zapier and Make
Send each new, changed or cancelled booking to Zapier, Make or your own app: get a webhook address, add it, and send a test booking.
A webhook sends each booking to another app, such as Zapier or Make, as it's made, changed or cancelled. Get a webhook address from Zapier or Make, add it on Settings, send a test booking, and build the rest of your automation from there.
What it does
TapBook posts each booking to the address you give it, the moment it happens. From Zapier or Make you can then add it to a spreadsheet, a CRM, Slack, your job software, or anything else they connect to.
- A booking goes when it's made, changed or cancelled. You choose which.
- Every booking and request goes, including ones the phone assistant takes and ones your team adds.
- Each booking is one flat list of fields, so Zapier and Make can map them one by one. See What each booking looks like.
- A booking that doesn't go is tried again through the day.
Before you start
You need:
- An owner log-in to TapBook. Only owners can add webhooks.
- A Zapier or Make account, or your own app that takes webhooks. In Zapier, Webhooks by Zapier needs a paid plan. In Make, webhooks work on the free plan.
- The Webhooks card on Settings. If Settings has no Webhooks card, email hello@tapbook.au and we'll turn it on.
Get an address from Zapier
- In Zapier, choose Create, then Zaps.
- Choose the Trigger step, and search for Webhooks by Zapier.
- For Trigger event, choose Catch Hook, then Continue.
- Leave Pick off a Child Key empty, and choose Continue.
- Under Your webhook URL, choose Copy.
Keep Zapier open. Once you've added the address in TapBook and sent a test booking, come back and choose Test trigger. Zapier finds the test booking, and its fields are ready to use in your next step.
Get an address from Make
- In Make, choose Create a new scenario.
- Choose the big plus, and search for Webhooks.
- Choose Custom webhook.
- Choose Add, name it TapBook, and choose Save.
- Choose Copy address to clipboard.
Keep Make open. It says it's waiting for data. Once you've added the address in TapBook and sent a test booking, Make says Successfully determined, and the booking's fields are ready to use in your next module.
Add it in TapBook
- Open Settings. The card is Webhooks.
- Choose Add a webhook.
- In Address, paste the address from Zapier or Make. It starts with https://.
- Under Send it bookings that are, leave Made, Changed and Cancelled ticked, or untick the ones you don't want. Changed covers confirmed, moved, booked in, a quote sent, completed, a no-show and an undo.
- Choose Add webhook.
The toast says Webhook added. The question now shows the Signing secret. Zapier and Make don't need it, so choose Done.
You can add up to 10 addresses.
Send a test booking
- On the address, choose Send a test booking. The toast says Test booking on its way to the address's host.
- In Zapier, choose Test trigger. In Make, the webhook says Successfully determined.
- In Sent to your webhooks, under the addresses, the test shows as Test booking, Sent.
The test booking is made up from your first service and location, and has test set to true. Real bookings have it false, so you can filter tests out in Zapier or Make.
What each booking looks like
Each booking arrives as JSON, with its type, when it happened, and the booking in data:
{
"type": "booking.created",
"timestamp": "2026-09-29T19:12:00+10:00",
"data": {
"id": "3f1c9f6e-8f0e-4c55-9a3a-7d2b3d5e6f70",
"url": "https://tapbook.au/dashboard/jax-tyres-auto/bookings/3f1c9f6e-8f0e-4c55-9a3a-7d2b3d5e6f70",
"change": "booked",
"kind": "appointment",
"kind_words": "Booking",
"status": "confirmed",
"status_words": "Confirmed",
"starts_at": "2026-10-02T09:00:00+10:00",
"ends_at": "2026-10-02T10:00:00+10:00",
"time_zone": "Australia/Melbourne",
"date": "Fri 2 Oct 2026",
"time": "9:00 am",
"moved_from": null,
"service": "Logbook service",
"extras": "Tyre rotation × 2, Wiper blades",
"location": "Narre Warren",
"address": "12 Webb St, Narre Warren VIC 3805",
"team_member": "Sam",
"customer_name": "Jo Citizen",
"customer_mobile": "+61412345678",
"customer_phone_words": "0412 345 678",
"customer_email": "jo@example.com",
"notes": "Please call first.",
"answers": "Your car: Make and model: Toyota Corolla, Rego: 1AB 2CD\nDrop-off: Before 8 am",
"quote_amount": null,
"source": "website_form",
"source_words": "Website form (jaxtyres.com.au)",
"urgent": false,
"created_at": "2026-09-29T19:12:00+10:00",
"test": false
}
}type is booking.created, booking.changed or booking.cancelled. change says exactly what happened, such as booked, moved or completed. moved_from is the old time when a booking moved. date and time are in the location's time zone, written as the dashboard writes them, so you don't need a formatter step. url opens the booking in TapBook.
A quote request, call-back or enquiry has no time, so starts_at, ends_at, date and time are null.
Change, stop or remove an address
Each address shows what it gets, such as Bookings made, changed and cancelled, and a chip: On, or Stopped.
- Change lets you pick again which bookings go there. Save keeps them, and the toast says Saved.
- Remove asks Remove this webhook? Bookings stop going there, and anything still waiting to go is dropped.
- Start again turns a stopped address back on. The toast says Webhook started again.
TapBook stops an address when the app says the address is gone, or when it hasn't taken bookings for a day. The address says why. Bookings in the meantime aren't sent.
The log
Sent to your webhooks lists every booking TapBook sent, or tried to: When, Booking, Change and Status, with To and the address's host under the change. Booking opens the booking. Show more loads older rows.
Status is one of:
- Waiting or Sending: on its way.
- Sent: the app took it.
- Trying again: the app didn't answer, so TapBook tries again on its own.
- Not sent: TapBook gave up. Retry sends it again straight away, with the same webhook-id.
- Sent with a later change: this change didn't go, but a later one for the same booking did.
- Skipped: it didn't go, and the line under it says why.
A cancel, a complete and a no-show wait 10 seconds before they go, so Undo on the booking can stop them. See Confirm, move and complete bookings.
For your own app
If you're receiving webhooks in your own app, check each one came from TapBook with the Signing secret. On the address, choose Signing secret, then Copy. The toast says Secret copied.
Each booking comes with these headers, signed as Standard Webhooks describes:
webhook-id
webhook-timestamp
webhook-signaturewebhook-id stays the same on every try of that booking, so you can ignore one you've already had. Answer with any 2xx status to say you took it. TapBook doesn't follow redirects, and a 410 stops the address.
Troubleshooting
Address isn't accepted
An address must start with https:// and be on the public internet. That address is already here. means it's on the card already. Tick at least one. means no choice under Send it bookings that are is ticked.
Zapier or Make didn't get the test
Check the address on the card is the one Zapier or Make gave you. In Make, the scenario has to be waiting for data: choose Run once, then send the test booking again. In Zapier, send the test booking, then choose Test trigger.
Address stopped
The address shows Stopped and why. Fix it in Zapier or Make, such as turning the Zap or scenario back on, then choose Start again.
Add a webhook can't be pressed
You have 10 addresses already. Remove one to add another.
Updated . Still stuck? Email hello@tapbook.au