Resources · Zapier integration

Nabooki Zapier integrationAutomate Nabooki with Zapier.

Nabooki Zapier integration: 3 triggers, 0 actions, 0 searches. Nabooki can start a Zap when a booking is created, updated or cancelled. All three triggers are instant, even on the free plan, but no Zap can write a booking back into Nabooki.

See the 3 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Nabooki Zapier integration does for you

The Nabooki Zapier integration turns the life of a booking into the start of an automation. Nabooki is an online platform for taking bookings and running the business around them; Zapier listens for three moments, a booking created, changed or cancelled, and passes its details to your other tools.

Three results come out of it. A booking log outside Nabooki: Booking Created starts the Zap for each new booking, and the next step can add it to a sheet anyone on the team can open. A heads-up on cancellations: Booking Cancelled fires when a booking is called off, so a message can reach the team chat while there is still time to act. A trail of changes: Booking Updated reacts when an existing booking is modified, so the copy you keep elsewhere can be noted as changed.

What Zapier does not do here: Nabooki has no action and no search on Zapier. A Zap cannot create a booking, change one or look one up inside Nabooki; the data only flows out, never back in. To weigh that against other tools, see our Make vs Zapier comparison.

Speed is the strong point. All three triggers are instant: Nabooki tells Zapier when the event happens, so the check interval of the free plan never delays these Zaps.

Vocabulary

Zapier vocabulary in one minute

Eight words you will meet in the editor, in plain English.

Zap
The automation you build on Zapier: 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 on, Zapier waits for it. All three Nabooki operations are triggers.
Action
What the Zap does once it has started: the step that writes, sends or moves something for you, here always in another app.
Task
The unit Zapier bills: one action your Zap completes successfully. The number attached to your plan is a count of those.
Polling trigger
A trigger Zapier checks on a timer, at a fixed interval set by your plan. None of the Nabooki triggers works this way.
Instant trigger
A trigger the app reports by itself: it calls Zapier the moment the event happens, so nothing waits for a check.
Filter
A step that lets the Zap go on only when what arrived meets the condition you set, and stops it there otherwise.
Multi-step Zap
Any Zap beyond one trigger and one action. A second action or a filter turns a Zap into one, and it then needs a paid plan.
Cost

What a Nabooki Zap really costs

Zapier bills actions, not triggers. Nabooki only ever starts Zaps, so what you pay depends on the steps you put after it.

  • Premium appNo, it works on the free plan
  • Free plan100 tasks a month, Zaps of two steps
  • Cost of a trigger0 tasks

A task is counted each time your Zap carries out an action and it works. The trigger never costs one, and an action that fails is not counted either. In a Zap with three actions, each success counts on its own, so it eats three times more than a one-action Zap. The free plan gives 100 tasks a month and unlimited Zaps, each capped at two steps: one trigger, one action. Add a filter or a second action and you need a paid plan. Zapier publishes the interval grid below for polling triggers; it does not apply to the three instant triggers of Nabooki.

Connect

Connect Nabooki to Zapier in 3 steps

  1. 01

    Open the Apps page

    In your Zapier account, open the Apps page. A connection is your Nabooki account linked to Zapier once, then reused by every step that needs it. You need an account on the app, plus read or write access on anything you do not own yourself and want the Zap to touch.

  2. 02

    Add the connection

    Click + Add connection, type Nabooki in the search box of the dialog and pick it from the results. Then click Add connection to open the Nabooki sign-in in a new tab.

  3. 03

    Sign in and grant access

    In that tab, sign in to Nabooki with the account that receives your bookings, then grant Zapier access to it. Back in the editor, the connection can be picked in any Zap that starts from Nabooki.

First Zap

Your first Zap: cancellations announced to the team

GoalEach time a booking is cancelled in Nabooki, a message goes out in your team chat: one trigger, one action, so it fits on the free plan.

  1. 01

    Create the Zap and pick the trigger

    Build a new Zap, choose Nabooki as the app that starts it and Booking Cancelled as the event. Select the Nabooki connection you set up earlier.

  2. 02

    Test the trigger

    Run the trigger test. Zapier brings back the three most recent items of the connected account, so the rest of the Zap is mapped on a real cancelled booking.

  3. 03

    Add the message

    Add the action in your team chat, pick the event that sends a message, and drop in the values the trigger returned. Test this step too and read what came back.

  4. 04

    Publish

    Click Publish to switch the Zap on. It reacts to cancellations made from that moment on; the ones made before stay out of the chat.

Triggers

Nabooki triggers on Zapier

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

1

Booking Cancelled

Instant trigger

In Zapier“Triggers when a new booking is cancelled.”

A booking gets cancelled in Nabooki and your Zap starts with it, carrying the details of that booking to the steps that follow.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
warn the team in its usual chat, or add each cancellation as a new row in a sheet the team can open.
Watch out
it fires on every cancellation; if only some matter, a filter does the sorting, and a filter needs a paid plan.
2

Booking Created

Instant trigger

In Zapier“Triggers when a new booking is created.”

Each new booking taken in Nabooki launches the Zap, with the booking ready to be copied, announced or turned into a task elsewhere.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
keep a running sheet of every booking that people without a Nabooki login can read.
Watch out
there is no required field, so the test is your main check; read the fields it returns before mapping them.
3

Booking Updated

Instant trigger

In Zapier“Triggers when an existing booking is updated.”

Editing a booking that already exists in Nabooki runs the Zap, so the change can follow wherever you track your bookings outside the app.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
keep a log of booking changes in a sheet, or tell the person in charge that a booking moved.
Watch out
to update the matching row in another app, a step must first find that row; check at the test which values identify the booking.
When it breaks

When a Nabooki Zap breaks

Zapier links no help article and no documented limit to Nabooki, so the cases below come from how Zapier itself works.

Three of them are worth knowing before you publish. If a Zap does not behave the way you planned, see our Zapier troubleshooting guide.

  • No catch-up on the past

    A Zap only reacts to what happens after you switch it on. Bookings that already existed stay out, and moving that backlog is a separate job.

  • A Zap that sets itself off

    A Zap that writes into the very place its own trigger watches can start itself again and again, and burn through your task count. Check where each step writes.

  • Flood protection

    After a bulk import or a migration, a trigger may suddenly return a huge batch, and Zapier's flood protection can hold that batch back.
Need help

Need help automating Nabooki with Zapier?

A person reads every message.

FAQ

Nabooki and Zapier: your questions

01Is the Nabooki Zapier integration free?
Yes. Nabooki is not a premium app, so its three triggers work on the free plan of Zapier. That plan gives you 100 tasks a month and as many Zaps as you like, with one condition: each Zap holds two steps, one trigger and one action. A Nabooki trigger followed by one row in a sheet or one chat message fits exactly. Add a filter or a second action and the Zap becomes multi-step, which needs a paid plan. The trigger itself never uses a task.
02How many tasks does a Nabooki Zap use?
None for the trigger: a new, changed or cancelled booking costs nothing on its own. Each action that completes successfully counts as one task, so a Zap with one action spends one task per booking event it handles, and a Zap with three actions spends three. An action that fails is not counted against your plan. A few apps take more than one task for some actions, so keep an eye on the other app in your Zap.
03Does Nabooki start Zaps in real time?
Yes, all three of its triggers are instant. When a booking is created, updated or cancelled, Nabooki tells Zapier itself and the Zap starts right away, whatever your plan. The interval grid Zapier publishes for its plans concerns polling triggers only, so it does not apply here, and a free plan is not slower than a paid one for these events. In the editor, a Zap built on an instant trigger shows a lightning bolt.
04What does connecting Nabooki to Zapier require?
An account on the app, plus read or write access on anything you do not own yourself and want the Zap to touch. The connection is made once, from the Apps page of your Zapier account, then reused by every Zap that starts from Nabooki. None of the triggers has a required field, so once the account is connected, testing a trigger is what shows you the fields you can use in the next steps.
05Can a Zap create or reschedule a booking in Nabooki?
No. Nabooki offers no action and no search on Zapier, only three triggers. The app can start a Zap, it can never be one of its later steps. So a Zap can copy a booking, announce a cancellation or log a change elsewhere, but it cannot create, edit or cancel a booking inside Nabooki, nor look one up. Any flow that needs to write into the app cannot be built with this integration as it stands today.
06What if the Nabooki trigger you need is missing?
Then the editor cannot offer it. The Nabooki page on zapier.com shows the current list of operations, and only those can be picked when you build a Zap. Before giving up, test the three triggers and read what each one returns: the information you are after may already travel with Booking Created, Booking Updated or Booking Cancelled, and a filter or a later step can then work with it. Only the test tells you for sure.
07Zapier, Make or n8n for Nabooki?
Decide on criteria rather than on a winner. Coverage first: on Zapier, Nabooki offers three triggers and no action, so compare what each tool offers for this app before you choose. Then the billing model: Zapier counts each successful action as a task and never bills the trigger. Then the shape of your flows: anything beyond one trigger and one action needs a paid plan on Zapier. Finally, speed: all three triggers are instant, so the check interval of a plan does not apply to them.
Same platform

Other docs you might need on this stack.

Browse all integrations