Integrating Zapier with your account

Zapier is only available on our Paid plan and you'll need to make sure you setup your own Zapier account in order to integrate with it.

Link to 100's of other services using our Zapier integration. Take a look at the list of services that link to Zapier to get some ideas of how your bookings page can trigger a huge range of automatic activities.

Integrating Zapier step by step

  1. On your account click the chevron arrow next to your email address and select Integrations.
  2. Scroll down to Connect with Additional Services. Click Connect under Zapier.
  3. If you are already logged into Zapier, it will auto-connect to your Zapier account. Otherwise, it will prompt you to login to your Zapier account.
  4. Once your Zapier account is integrated with you'll see a pop-up modal with your API key and suggested Zaps with apps you are already using. Copy your API key to use within Zapier.
  5. On Zapier, you can go to Integrations > My Apps and connect to your account using this API key. 

Zapier examples

We currently support 3 triggers and one action. 

Trigger: New Booking 

This trigger will fire each time someone makes a booking on the nominated booking page. As part of the trigger, our system will send through all the data we have about the booking. This includes all the information gathered on the booking form 

Please refer to this page for shorthand codes that are available for use in Zapier. For custom fields on the booking form, a shorthand code needs to be set so that the data is available in Zapier.  

Trigger: Updated (Cancelled) Booking 

When you - or your customer - clicks on the link to cancel a booking through our system, this trigger will fire. (Note that if you simply delete a booking from the underlying calendar, our system will record it as "cancelled" but this trigger will not fire.) 

Trigger: Booking Rescheduled 

This trigger fires when the person who made the booking has decided to change the time it will start. The data included will be the same as the previous triggers.

Testing your zap batches up zaps (what would trigger that test properly) and only release them every 5 minutes. So, this can result in the test booking not coming in for 5 minutes. Zapier continues looking for the test until it comes through, which seems like long wait time (which resembles a failed test.) Although the test has not failed, Zapier has suggested these 2 workarounds:
  • Wait until immediately before the 5-minute mark to create a test booking, then test the Zap right at that 5-minute mark to try and catch the zap properly.
  • If that doesn't work, click "Skip Test & Continue", which will pull in sample data that you can use to set up the rest of the Zap.

Suggested Zaps

Once you are all set up, you might want to check out this list of possible integrations for ideas on how you can get the most out of Zapier and