Resources · Zapier integration

Booqable Zapier integrationAutomate Booqable with Zapier.

The Booqable Zapier integration gives you 7 triggers, 3 actions and 3 searches. Every trigger is instant, so orders, payments and invoices reach Zapier as they happen. The actions only touch customers. Here is what each one does, costs and breaks.

See the 13 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Booqable Zapier integration actually does

Booqable is rental software: you take bookings online and run the orders, payments and invoices behind them. The Zapier integration lets those events start an automation in another tool, and lets other tools create, update, delete or look up Booqable customers without anyone typing them in twice.

Three results you can build on day one. A clean customer list: New Customer plus a filter plus Delete Customer removes the dummy accounts your team creates while testing the booking page. A paid-order signal: Completed Payment fires the second money lands, so the people preparing equipment hear about it without refreshing a screen. An order status feed: Reserved Order, Started Order and Stopped Order report each order as it is reserved, started and stopped in Booqable.

Now the part the app page skips. Zapier cannot create, edit or delete an order in Booqable, and it cannot issue an invoice. Every write action is about customers. If your plan is to push bookings into Booqable from another shop or form, this integration will not do it: you can only read orders, through the triggers and Find Order - By ID.

Booqable also has a Booqable Make integration page if you want to see the same app from another automation tool, and our Make vs Zapier comparison sets out the criteria that separate the two.

Vocabulary

Zapier vocabulary in one minute

Eight words come back on every line below. Here they are in plain English.

Zap
The automation you build: one trigger, then one or more actions that run each time the trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is switched on, Zapier sits and waits for it.
Action
What the Zap does after it starts: the step that writes, sends or changes something on your behalf.
Task
The unit Zapier bills. One task equals one action your Zap completes successfully, and your plan counts those.
Polling vs instant
A polling trigger is checked by Zapier on a timer. An instant trigger is reported by the app itself the moment it happens.
Filter
A step that lets the Zap continue only when the incoming data meets your condition, and stops it otherwise.
Search step
A step that looks up something that already exists in an app, so later steps can reuse what it found.
Connection
Your Booqable account linked to Zapier once, then reused by every step that talks to Booqable.
Cost

What Booqable on Zapier really costs you

Booqable is not a premium app, so it works on the free plan. The bill is counted in tasks, and only finished actions count.

  • Free plan100 tasks a month, unlimited Zaps, two steps per Zap
  • Premium appNo, Booqable runs on the free plan
  • Triggers7 instant, 0 polling
  • What counts as a taskEach action that completes successfully

The trigger costs nothing, and neither does Zapier checking for new data. Each action that succeeds is one task; an action that fails is not counted. The free plan gives 100 tasks a month and unlimited Zaps, but only two steps per Zap: one trigger, one action. Add a filter, a search or a second action and the Zap becomes multi-step, which needs a paid plan. Since all seven Booqable triggers are instant, the polling grid below never slows them down.

Connect

Connect your Booqable account in three steps

  1. 01

    Open Apps and add a connection

    In your Zapier account, go to the Apps page and click + Add connection. Type Booqable in the search box of the dialog and select it. You need a Booqable account before you start.

  2. 02

    Sign in to Booqable

    Click Add connection. A new tab opens on Booqable: sign in with the account whose customers and orders the Zap should see. Use an account that can read and edit the records you plan to automate, not only your own.

  3. 03

    Grant access

    Allow Zapier to access the account. From then on, every Booqable step in every Zap reuses this connection, so you never paste credentials into a step again.

First Zap

Your first Zap: delete test customers automatically

GoalEvery time someone on your team creates a customer called test while trying out the booking flow, Zapier deletes it before it pollutes your reports.

  1. 01

    Build: pick the trigger

    Start a new Zap, choose Booqable as the app and New Customer as the event, then select the Booqable connection you created in the previous section.

  2. 02

    Test the trigger

    Click test. Zapier brings back the three most recent customers of the account, so create one named test in Booqable first and pick it from the list.

  3. 03

    Add the filter

    From the plus icon add Filter. Pick the customer name field, a text rule that wants an exact match, and the value test. A looser rule would also delete a real client named, say, Contest Hire. This step makes the Zap multi-step, so it needs a paid plan.

  4. 04

    Add Delete Customer

    Add Booqable again with Delete Customer. In the ID field, insert the customer ID from the New Customer step, not a value you type: the Zap then deletes the customer that just arrived each time. Nothing else is required.

  5. 05

    Test, then publish

    Run the action test on your test customer and check in Booqable that it is gone. Then click Publish to switch the Zap on.

Triggers

The 7 Booqable triggers

7 events start a Zap when something happens in Booqable, and 7 of them are instant: the app calls Zapier straight away, whatever your plan.

1

Completed Payment

Instant trigger

In Zapier“Triggers when a payment is completed.”

Starts your Zap when a customer finishes paying in Booqable, so the money side of a rental becomes an event other tools can react to.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a bike rental shop that only prepares a bike once the deposit is actually paid can alert the workshop as soon as the payment clears, instead of checking the dashboard between customers.
Watch out
it reports a payment, not an order. If the next step needs order details, add Find Order - By ID and remember that the search turns the Zap into a multi-step one.
2

New Customer

Instant trigger

In Zapier“Triggers when a new customer is added.”

Fires each time a customer record is added to Booqable, so a new renter can reach your other tools without a manual export.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a camera gear rental company can send every new renter to its email tool the minute they register, so the welcome message lands while they are still looking at lenses.
Watch out
a Zap built on this trigger that also uses Create Customer in Booqable will set itself off again, creating a loop that eats tasks.
3

Finalize Invoice

Instant trigger

In Zapier“Triggers when an invoice is finalized.”

Goes off when an invoice in Booqable is finalized, which is the point where the amounts stop being a draft and become a document you can send.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a party equipment business whose bookkeeper works in a separate accounting tool can hand each finalized invoice over as soon as it is locked, so nobody re-keys totals at the end of the month.
Watch out
drafts do not count. Testing this trigger brings back only invoices that were already finalized in the account.
4

Reserved Order

Instant trigger

In Zapier“Triggers when an order is reserved.”

Fires when an order is reserved in Booqable. Of the order events, it is the earliest one this integration reports.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a wedding decor rental team can post every confirmed reservation to the channel the warehouse reads, so packing starts from a real booking and not from an inquiry.
Watch out
reservations made before the Zap went live are never sent; Zapier only reacts to what happens after publishing.
5

Started Order

Instant trigger

In Zapier“Triggers when an order is started.”

Goes off the moment someone marks an order as started in Booqable, so the next step of your process can begin without a phone call.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a kayak hire business can log each pickup in a shared sheet the moment staff start the order at the counter, giving the owner a live view of what is out on the water.
Watch out
the Zap follows what staff record. If nobody starts the order in Booqable at handover, Zapier never hears about the pickup.
6

Stopped Order

Instant trigger

In Zapier“Triggers when an order is stopped.”

Runs your Zap when an order is stopped in Booqable, the counterpart of Started Order at the other end of the rental.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
an audio equipment rental company can ask for a review right after the speakers are returned, while the event is still fresh in the customer's mind.
Watch out
a stopped order is not a checked order. If damage inspection happens later, a review request sent at this point may go out before you know the gear came back intact.
7

Updated Order

Instant trigger

In Zapier“Triggers when an order is updated.”

Reports each update Booqable records on an order. It is the broadest of the seven and the noisiest.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a tent rental firm that keeps a running change log for its crew can append each edit to that log, so the people on site know the latest version of the booking.
Watch out
one order can fire this many times in a day. Never use it to create a new record somewhere, or every edit will produce a duplicate.
Actions

The 3 Booqable actions

Booqable gives you 3 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Create Customer

Action

In Zapier“Create a new customer.”

Adds a new customer to Booqable from data that arrived in another tool. Only the Name is required, and Booqable expects it to be the company name in most cases.

When to use it
a B2B event supplier collecting quote requests in a web form can open the customer record before anyone quotes.
Watch out
it does not check for an existing customer, so a returning client gets a second record.
2

Delete Customer

Action

In Zapier“Delete a customer.”

Removes a customer from Booqable using its ID, which is the only field the action asks for.

When to use it
cleaning out test or spam accounts, behind a filter that only lets those names through.
Watch out
there is no undo step in the Zap, so always put a filter in front and test it on a dummy record first.
3

Update Customer

Action

In Zapier“Update a customer.”

Changes an existing customer in Booqable. It needs two things: the customer ID and the Name, even if you only want to fix one detail.

When to use it
when a client updates its company name in your CRM, the same change can flow into Booqable.
Watch out
since Name is required, map the current name if it should stay the same, or you risk overwriting it.
Searches

The 3 Booqable searches

3 search steps look for data that already exists in Booqable, so a later step can use it.

A search step finds a customer or an order that already exists and passes it to the next steps. In the action list, Booqable searches sit under their own SEARCH heading at the bottom. Three settings decide what happens when the result is not what you expected.

1

Find Customer - By ID

Search

In Zapier“Search for Customer by ID.”

Fetches one Booqable customer when an earlier step already holds its ID.

When to use it
pulling the full customer record into a Zap that started from an order event.
Watch out
the Customer ID is mandatory, so this search only works when an earlier step really carries one.
2

Find Customer - By Name or Email

Search

In Zapier“Search for Customer by name or email.”

Looks a customer up by name or by email address, the two things another tool is most likely to know about them.

When to use it
before Update Customer, to get the ID that action requires from a contact coming out of your CRM.
Watch out
how close the match must be is decided by Booqable, so test it with a real spelling variant before trusting it.
3

Find Order - By ID

Search

In Zapier“Search for Order by ID.”

Retrieves a Booqable order from its ID, so a later step can use details that the starting event did not include.

When to use it
after Completed Payment, to attach the order to the payment notice you send your team.
Watch out
it is the only way to read an order from an action step; Zapier offers no action that changes one.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, an empty search stops the Zap and skips the steps that depended on it. Switch it on and the Zap continues with nothing in hand.
  2. Create X if it doesn't exist yet?
    This box turns a search into a find-or-create. Booqable exposes no such variant on Zapier, so you will not see it on these three searches.
  3. If multiple search results are found?
    Three choices when several records match: keep the first one (the default), stop the Zap, or pass all of them on.
When it breaks

When the Booqable Zap breaks

Zapier attaches no help article to Booqable, and no app-specific limit is documented. The failures you will meet come from how Zapier itself works.

Here are four to know before you publish. Each one is avoidable once you know where it hides. If a Zap misbehaves anyway, our Zapier troubleshooting page is the next stop.

  • Old orders never arrive

    A Zap only reacts to what happens after you publish it. Reservations and payments that existed before stay where they are; moving that backlog is a separate job.

  • The customer loop

    A Zap that starts on New Customer and ends with Create Customer in the same account triggers itself again and again, burning through your tasks.

  • Bulk imports get held back

    Import hundreds of customers at once and Zapier's flood protection can pause the batch instead of running a Zap for every single one.

  • Updated Order creates duplicates

    Each edit to an order fires the trigger again. Pair it with a create action elsewhere and one booking turns into several records.
Need help

Need help automating Booqable with Zapier?

A person reads every message.

FAQ

Booqable and Zapier: common questions

01Is the Booqable Zapier integration free?
Yes, Booqable is not a premium app, so it runs on Zapier's free plan. That plan includes 100 tasks a month and unlimited Zaps, but each Zap is limited to two steps, one trigger and one action. As soon as you add a filter, a search such as Find Customer - By ID, or a second action, the Zap becomes multi-step and needs a paid plan. The example Zap on this page, with its test-customer filter, falls into that category.
02How many Zapier tasks does a Booqable Zap use?
One task per action that completes successfully. The trigger is free, and so is the waiting: Zapier does not bill for listening to Completed Payment or Reserved Order. If a Zap runs a single action like Create Customer, each run costs one task. If it runs two actions, each successful run costs two. An action that fails is not counted against your plan. Watch Updated Order in particular, because every edit to an order is a new run and therefore new tasks.
03Do Booqable triggers run in real time?
Yes. All seven Booqable triggers are instant: Booqable tells Zapier as soon as the event happens, and the Zap starts at once. The polling intervals that depend on your plan, 15 minutes on Free and down to 1 minute on Team and Enterprise, do not apply to them. In the Zap editor, a Zap built on an instant trigger shows a lightning bolt, which is a quick way to confirm it. This is the main reason a free plan works well for Booqable.
04What does it take to connect Booqable to Zapier?
A Booqable account, and access to the customers and orders the Zap will touch. You open the Apps page in Zapier, click + Add connection, pick Booqable, then sign in to Booqable in the tab that opens and grant access. The connection is stored once and reused by every Booqable step. If you work on records owned by a colleague, make sure your Booqable account can read and edit them, or the actions will fail.
05Why does Update Customer ask for a name when only the ID changes?
Because both fields are mandatory on that action: the customer ID tells Booqable which record to change, and Name is required on every update. If the step that feeds it has no name, map the existing one from a Find Customer search so it stays untouched. Leaving a blank or wrong value there is the quickest way to rename a client by accident, so test the action on a dummy customer before publishing.
06What if the Booqable action you need is not on Zapier?
Then Zapier cannot do it through this integration today. Booqable exposes three actions, all on customers, and three searches. Creating or editing orders and issuing invoices are not available. The usual paths are to rethink the flow so Booqable is the source and another tool receives the data, or to check whether another automation platform covers the gap. Either way, list the exact operation missing before you choose, so the comparison stays concrete.
07Zapier, Make or n8n for Booqable?
It depends on your criteria rather than on a winner. On Zapier, Booqable brings seven instant triggers, three actions that only touch customers and three searches, and it works on the free plan. The deciding question is whether the operation your flow needs is on that list: writing orders or invoices is not. Compare what each platform offers for Booqable on its own integration page before committing a team to one of them.
Same platform

Other docs you might need on this stack.

Browse all integrations