Resources · Zapier integration

Orufy Bookings Zapier integrationAutomate Orufy Bookings with Zapier.

Orufy Bookings Zapier integration: 3 triggers, 0 actions and 0 searches. Zapier hears about every new, canceled or rescheduled appointment the moment Orufy Bookings reports it, and passes it to your other tools. It cannot write anything back into Orufy Bookings.

See the 3 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Orufy Bookings Zapier integration does for you

The Orufy Bookings Zapier integration lets your booking calendar talk to the rest of your tools through Zapier, a service that chains apps together without code. You build a Zap (one automation: an event that starts it, then the steps it runs for you) that starts whenever an appointment is booked, canceled or moved in Orufy Bookings.

A live log of every booking. New Appointment fires for each appointment scheduled, so a clinic, a studio or a consultant can keep a sheet, a CRM or a team channel filled without retyping anything.

Cancellations that free the slot everywhere. Appointment Canceled tells the rest of your stack that a slot is open again, for instance to warn the person in charge or update a client file.

Moves that reach everyone. Appointment Rescheduled passes the change on, so the colleague who prepares the session is not working from the old time.

All three triggers are instant: Orufy Bookings tells Zapier when the event happens, even on the free plan, where polling triggers wait for the next check. What Zapier does not do here: write into Orufy Bookings. There is no action and no search, so a Zap can neither create, cancel nor look up an appointment. Orufy Bookings is always the first step, never a later one.

If that one-way setup does not fit your scenario, weigh the options: Zapier alternatives.

Vocabulary

Zapier words, in plain English

Eight terms come back all over this page. One line each.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run every time the trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is on, Zapier waits for it. Orufy Bookings offers three, all instant.
Action
What the Zap does once it has started: the step that writes, sends or moves something. Orufy Bookings has none, so actions live in other apps.
Task
The unit Zapier bills: one action your Zap completes successfully. The monthly count on your plan is a count of those.
Polling vs instant
Polling: Zapier asks the app for new items on a timer. Instant: the app calls Zapier the moment the event happens, nothing waits.
Filter
A step that lets the Zap go on only when what arrived meets the condition you set, and stops it otherwise.
Search step
A step that looks up something that already exists in an app for later steps. Orufy Bookings offers none, other apps may.
Connection
Your Orufy Bookings account linked to Zapier once, then reused by every Orufy Bookings trigger in all your Zaps.
Cost

What an Orufy Bookings Zap really costs

Orufy Bookings is not a premium app (Zapier's label for apps kept for paid plans and trials), so it works from the free plan. Your budget is counted in tasks.

  • Premium appNo, free plan OK
  • Free plan tasks100 per month
  • Free plan Zap sizeTrigger + one action
  • Orufy Bookings triggers3 instant, 0 polling

The trigger never costs a task, so the appointments Orufy Bookings reports are free. What you pay for are the actions that follow in other apps: each one that succeeds counts on its own, one that fails does not. The free plan gives 100 tasks a month and two-step Zaps: one trigger, one action. Log the booking and also notify a channel, or add a filter, and it becomes a multi-step Zap that needs a paid plan. The polling grid below never slows these triggers down, since all three are instant.

Connect

Connect Orufy Bookings to Zapier in three steps

  1. 01

    Open Apps and add a connection

    In your Zapier account, open the Apps page and click + Add connection. A dialog opens with a search box. The connection you create here will serve all three Orufy Bookings triggers.

  2. 02

    Pick Orufy Bookings and confirm

    Type Orufy Bookings in the dialog, select it, then click Add connection. A new tab opens on the Orufy Bookings side, where you sign in with your account.

  3. 03

    Sign in and grant access

    Sign in to Orufy Bookings and grant Zapier access. You need an account on the app, plus read or write access on anything you don't own yourself but want the Zap to touch.

First Zap

Your first Orufy Bookings Zap: a booking log your team can read

GoalEvery new appointment booked by a physiotherapy clinic lands as a row in the shared planning sheet.

  1. 01

    Pick the trigger

    Building starts with the event. Choose Orufy Bookings and New Appointment, select your connection, then fill the required subscription scope setting.

  2. 02

    Test on a real booking

    Run the test. Zapier brings back the three most recent appointments of the connected account, so you map fields on a real booking instead of an empty example.

  3. 03

    Add the action in your sheet

    Add the action that follows, here a new row in the planning sheet, and map the appointment details from the trigger into the matching columns.

  4. 04

    Test the action

    Run the action once and open the sheet. If the row looks right, the Zap is ready; if not, fix the mapping now rather than after the first real bookings.

  5. 05

    Publish

    Click Publish to switch the Zap on. From then on, every appointment booked in Orufy Bookings goes to the sheet. Bookings made before that stay out.

Triggers

The 3 Orufy Bookings triggers on Zapier

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

1

New Appointment

Instant trigger

In Zapier“Triggers when a new appointment is scheduled.”

Starts the Zap each time someone schedules an appointment in Orufy Bookings, which makes it the entry point for most booking automations: logging, confirming, preparing the session.

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 physiotherapy clinic that wants every new booking added to the planning sheet the front desk works from.
Watch out
the subscription scope setting is required on this trigger, and the Zap only sees appointments booked after it is published.
2

Appointment Canceled

Instant trigger

In Zapier“Triggers when an appointment is cancelled.”

Kicks in when an appointment is canceled, so the slot that just opened up is known everywhere it matters, not only inside the booking calendar.

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 yoga studio that wants the teacher warned in the team channel each time a student drops out of a private session.
Watch out
a Zap built on New Appointment never hears about cancellations; this trigger needs its own Zap, with its own required subscription scope.
3

Appointment Rescheduled

Instant trigger

In Zapier“Triggers when an appointment is rescheduled.”

Fires when an existing appointment moves to another time, which keeps every copy of the schedule outside Orufy Bookings in step with the real one.

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 consultant who keeps client files in a CRM and wants the next meeting time corrected there whenever a client moves it.
Watch out
like the other two, it needs the required subscription scope, and it stands apart from New Appointment, so plan a separate Zap.
When it breaks

When an Orufy Bookings Zap breaks

Zapier attaches no help article to Orufy Bookings and documents no limit specific to it. What goes wrong comes from how Zaps work in general, plus the one required setting of its triggers.

  • Past bookings are not replayed

    A Zap only reacts to what happens after it is switched on. Appointments already in Orufy Bookings never pass through it; moving that backlog is a separate job.

  • A wave of bookings gets held back

    If a large batch of appointments arrives at once, after a migration for instance, Zapier's flood protection can hold the batch back instead of running every one.

  • The subscription scope left empty

    All three triggers require the subscription scope setting. Until it is filled, the trigger cannot be tested and the Zap cannot be published.

  • The free plan stops at two steps

    Logging a booking and notifying a channel means two actions, which makes a multi-step Zap. On the free plan, keep one action per Zap or move to a paid plan.
Need help

Need help automating Orufy Bookings with Zapier?

A person reads every message.

FAQ

Orufy Bookings and Zapier: common questions

01Is the Orufy Bookings Zapier integration free?
Yes, within the limits of the free Zapier plan. Orufy Bookings is not a premium app, so no paid Zapier plan is needed to use it. The free plan gives 100 tasks a month and builds two-step Zaps: one trigger, one action. That covers a Zap that logs each new appointment in a sheet. A second action or a filter turns it into a multi-step Zap, which requires a paid plan. Your Orufy Bookings subscription is a separate matter.
02How many Zapier tasks does an Orufy Bookings Zap use?
None for Orufy Bookings itself, since it only offers triggers and a trigger never costs a task. What counts are the actions that follow in other apps: each one that succeeds is billed once, one that fails is not. A Zap that logs a booking in a sheet uses one task per appointment; one that also posts to a team channel uses two. Zapier notes that a few apps and actions take more than one task, so check usage after the first real bookings.
03Is Orufy Bookings on Zapier real time?
Yes. New Appointment, Appointment Canceled and Appointment Rescheduled are all instant triggers: Orufy Bookings tells Zapier when the event happens and the Zap starts right away, even on the free plan. The polling grid, every 15 minutes on Free, only applies to polling triggers, and this app has none. In the editor, a Zap built on an instant trigger shows a lightning bolt. The speed of what follows then depends on the apps you chain after it.
04What does it take to connect Orufy Bookings to Zapier?
An Orufy Bookings account, plus access to anything you don't own but want the Zap to follow. In Zapier, open Apps, click + Add connection, search for Orufy Bookings, click Add connection, then sign in to Orufy Bookings in the tab that opens and grant access. Once connected, each trigger asks for one required setting, the subscription scope, before you can test it. The same connection then serves all three triggers in all your Zaps.
05Why does a canceled appointment still show in the tool fed by New Appointment?
Because a Zap has exactly one trigger, and a Zap built on New Appointment only hears about new bookings. Cancellations come through Appointment Canceled, and moves through Appointment Rescheduled. To keep a sheet or a CRM accurate, build one Zap per event, each with its own required subscription scope and its own action in the target tool. On the free plan each of those Zaps stays at two steps, which is enough for one update per event.
06What if the Orufy Bookings action you need isn't on Zapier?
Then Zapier cannot do it for Orufy Bookings today, and it is the case for any write: the app offers no action and no search, only three triggers. Nothing can create, cancel or move an appointment in Orufy Bookings from a Zap. Two ways around it: use the three events to drive your other tools, which is what this integration does well, or check whether another automation tool covers writing into Orufy Bookings. List the operations your scenario requires first, then compare.
07Zapier, Make or n8n for Orufy Bookings?
Decide on criteria, not on brand. On Zapier, Orufy Bookings brings three instant triggers and nothing else, so it works as a starting point for Zaps that update other apps. If you only need to react to new, canceled or rescheduled appointments, that covers it. If you need to create or change bookings in Orufy Bookings, the operation is missing here, so check what the other tools offer for this app. Count your steps too: anything beyond one action needs a paid Zapier plan.
Same platform

Other docs you might need on this stack.

Browse all integrations