Resources · Zapier integration

Orioly Zapier integrationAutomate Orioly with Zapier.

The Orioly Zapier integration gives you 4 triggers, 0 actions and 0 searches. Every new or changed booking, and every new or changed contact, can start a Zap at once. Orioly sends; the work itself happens in the apps you connect after it.

See the 4 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Orioly Zapier integration is good for

Orioly is a booking and management tool for tour and activity operators. Linking it to Zapier lets each booking or customer change in Orioly set off work elsewhere: a row in a sheet, a message to the guide, a contact in your email tool. Orioly only starts things; it receives nothing back.

Three results operators build. A live bookings sheet: New Booking starts the Zap and a row is written for each reservation, so the team reads one shared file. Guides kept in the loop: Update Booking posts the change in a team channel when a reservation moves. A mailing list that grows by itself: New Contact adds each new customer to your newsletter tool, and Update Contact keeps their details in step.

All four triggers are instant. Orioly tells Zapier straight away, so the free plan's 15-minute check does not apply to any of them. A free account gets its bookings as fast as a paid one.

What Zapier does not do here matters just as much. There is no action: no Zap can create, edit or cancel a booking in Orioly. There is no search either, so a Zap cannot look up a past reservation. Data flows one way, out of Orioly, and anything you want written back has to be done by hand inside the tool. For a wider look at the platform, see the Zapier review.

Vocabulary

Zapier terms, explained simply

Seven words you will meet below, in one line each.

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. With Orioly, a booking or a contact that is created or updated.
Action
What the Zap does once started: the step that writes, sends or moves something for you. Orioly has none of its own.
Task
What Zapier bills: one action the Zap completes successfully. The allowance on your plan counts those.
Polling vs instant trigger
Zapier checks a polling trigger on a timer. An instant trigger is pushed by the app the moment the event happens.
Filter
A step that lets the Zap go on only when what arrived meets your condition, and stops it otherwise.
Search step
A step that looks up something already stored in an app, so later steps can use it. Orioly offers none.
Cost

What an Orioly Zap really costs

Orioly is not a premium app, so it works on the free plan. Zapier bills tasks, and Orioly's triggers are never one of them.

  • Premium appNo, free plan works
  • Free plan100 tasks a month, two-step Zaps
  • BilledEach successful action after Orioly
  • Trigger speedInstant on every plan

A trigger never costs a task, however many bookings come in. What counts is each successful action in the apps that follow; a failed one is not counted. The free plan gives 100 tasks a month, unlimited Zaps and two steps per Zap: one trigger, one action. Add a filter to keep only some bookings, or a second action, and the Zap becomes multi-step, which needs a paid plan. The interval grid below is for polling triggers only: all four Orioly triggers fire straight away on every plan.

Connect

Connect Orioly to Zapier in three steps

  1. 01

    Open the Apps page

    In Zapier, go to the Apps page of your account and click + Add connection. A connection is your Orioly account linked once, then reused by every Orioly trigger in every Zap.

  2. 02

    Pick Orioly

    Search for Orioly in the dialog, select it and click Add connection. You need an Orioly account first, since Zapier does not create one along the way.

  3. 03

    Sign in and allow access

    Log in to Orioly in the tab that opens and grant Zapier access. If you work on bookings in an account you do not own, check that your login can read them.

First Zap

Your first Orioly Zap: bookings straight into a sheet

GoalEach new Orioly booking that meets your condition becomes a row in a sheet the whole team can read.

  1. 01

    Start from New Booking

    Create a Zap, choose Orioly as the app that starts it and New Booking as the event, then select the Orioly connection made earlier.

  2. 02

    Test the trigger

    Run the test. Zapier pulls the three most recent bookings of the account, so you map the next steps on a real reservation instead of an empty form.

  3. 03

    Add a filter if needed

    Add a filter to let only some bookings through. It turns the Zap multi-step, so it needs a paid plan; leave it out to stay on the free one.

  4. 04

    Write the row

    Add the sheet app as the action and map the booking details into the columns. Test this step once and look at the row it creates.

  5. 05

    Publish

    Once the test row looks right, publish the Zap. Each new booking made in Orioly from then on gets its row without anyone copying it.

Triggers

Orioly triggers on Zapier

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

1

New Booking

Instant trigger

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

Starts the Zap whenever a new reservation is created in Orioly. Zapier features this one first on the Orioly page, and it is the natural base for most flows: logging sales, briefing guides, sending a welcome message from another tool.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
every new reservation should reach the people running the activity without someone forwarding it.
Watch out
it reacts to creation only; a later change needs Update Booking.
2

Update Booking

Instant trigger

In Zapier“Triggers when a booking is updated.”

Fires when an existing reservation changes in Orioly. The Zap then gets the booking in its new state, which lets you keep other tools from drifting out of date: the planning sheet, the guide's schedule, the customer record in your CRM.

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 customer moves their tour and the guide should hear about it before arriving at the meeting point.
Watch out
one booking can change several times, and each change starts the Zap again and spends tasks.
3

New Contact

Instant trigger

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

Launches the Zap each time a new contact is created in Orioly. That makes it the clean entry point for anything about customers rather than reservations: a newsletter list, a CRM, a review request sent by another app later on.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
you want each new customer in your email marketing tool without exporting lists by hand.
Watch out
contacts that existed before the Zap was published are not sent; bring them over separately.
4

Update Contact

Instant trigger

In Zapier“Triggers when a contact is updated.”

Runs when a contact's details are changed in Orioly. Paired with an update step in another app, it keeps the same person consistent across your tools after a correction or a new piece of information.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
your CRM should reflect what the front desk corrects in Orioly, with no double entry.
Watch out
if a Zap writes back into the same Orioly contact through another route, it can set itself off in a loop; keep the flow one way.
When it breaks

When an Orioly Zap breaks

Zapier ties no help article to Orioly, and no app-specific limit is documented. What follows are the general rules that apply to every Zap.

Three cases cover most surprises. If a Zap still misbehaves, the Zapier troubleshooting page is the next stop.

  • No catch-up on old bookings

    A Zap reacts only to what happens after it is switched on. Reservations and contacts already in Orioly stay where they are; moving that backlog is a separate job.

  • A Zap that sets itself off

    If a Zap writes into the very place its own trigger watches, it fires again and again and burns through the task count fast.

  • Big imports held back

    A trigger that suddenly returns a huge batch, after a bulk import or a migration, can be held back by Zapier's flood protection.
Need help

Need help automating Orioly with Zapier?

A person reads every message.

FAQ

Orioly Zapier integration: frequently asked questions

01Is the Orioly Zapier integration free?
Yes. Orioly is not a premium app, so its four triggers are open to the free plan. That plan gives 100 tasks a month and unlimited Zaps, with one firm limit: two steps per Zap, meaning one trigger and one action. Sending every new booking to a sheet fits. Adding a filter, a search or a second action makes the Zap multi-step, and that needs a paid plan. The triggers themselves never cost a task.
02How many tasks does an Orioly Zap use?
None for the Orioly part. Triggers never cost a task, so a booking that starts a Zap is free in itself. What counts is each successful action that follows in another app: one action, one task per booking; three actions, three tasks. Failed actions are not counted. Keep an eye on Update Booking and Update Contact, since every change starts the Zap again and each run spends its own tasks.
03Does Orioly send bookings to Zapier in real time?
Yes, all four triggers are instant. Orioly tells Zapier the moment a booking or contact is created or updated, and the Zap starts at once. The interval grid, 15 minutes on Free, 2 on Professional and 1 on Team and Enterprise, only applies to polling triggers, so it never slows Orioly down. A free account gets bookings as fast as a paid one, and the editor shows a lightning bolt on these Zaps.
04What do you need to connect Orioly to Zapier?
An Orioly account, plus read access to any bookings or contacts you do not own and want the Zap to use. In Zapier, open the Apps page, click + Add connection, pick Orioly, then sign in and grant access in the tab that opens. The connection is made once and then reused by every Orioly trigger, in every Zap you build afterwards. Your Orioly login must exist before you start, since Zapier does not create one.
05Why do old Orioly bookings never reach the Zap?
Because a Zap only reacts to what happens after it is switched on. Orioly reports new events to Zapier, but nothing sends the bookings and contacts that already existed when you published the Zap. Testing the trigger brings back the three most recent items to help with mapping, but that is a sample, not an import. Moving the existing list is a separate job, done outside the Zap, before or after you publish it.
06What if the Orioly operation you need does not exist?
Then the integration cannot do it today. On Zapier, Orioly offers four triggers, New Booking, Update Booking, New Contact and Update Contact, and nothing else: no action to create or cancel a booking, no search to find one. Anything that writes into Orioly has to happen in Orioly itself. Zapier can still carry each booking to tools with richer steps, and the work continues there, one task per successful action.
07Zapier, Make or n8n for Orioly?
Use criteria, not a ranking. Coverage: on Zapier, Orioly has four instant triggers and no action, so check whether the other tool can also write into Orioly if you need that. Cost: on Zapier the triggers are free and only the actions that follow are billed, though a filter means a paid plan. Upkeep: a small tour operator without a developer will usually favor the tool where the triggers are ready to use.
Same platform

Other docs you might need on this stack.

Browse all integrations