Resources · Zapier integration

OwnerRez Zapier integrationAutomate OwnerRez with Zapier.

The OwnerRez Zapier integration gives you 4 triggers, 5 actions and 3 searches. React the moment a booking or a contact is created or changed, then tag records, fill custom fields or adjust a booking. All four triggers are instant, even on the free plan.

See the 12 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the OwnerRez Zapier integration does for a rental business

OwnerRez is where vacation rental managers run their bookings, their guests and the properties they look after. Linking it to Zapier lets your bookings and contacts start work in other apps, and lets those apps write tags and custom field values back into OwnerRez.

Three outcomes worth building. First, a booking that sorts itself: Booking Created starts the Zap, and Add Tag or Set Custom Field marks it for the right cleaner, owner report or welcome sequence, without anyone opening the calendar. Second, a guest list that stays in sync: Contact Created and Contact Updated push each new or changed guest to your email tool or CRM, so marketing never works from a stale export. Third, a change that reaches the team: Booking Updated warns your housekeeping channel when dates move, and Booking Lookup pulls the full booking for the message.

What Zapier does not do here: it cannot create a booking or a contact in OwnerRez, and its three searches only find a booking, a guest or a property by ID, never by name or date. So the ID has to come from an earlier step. All four triggers are instant, which is the strong point of this integration.

Weighing tools before you commit? See Make vs Zapier and n8n vs Zapier.

Vocabulary

Zapier words, in plain English

Eight words carry this page. Here they are once, so the rest reads without a dictionary.

Zap
The automation you build in 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 switched on, Zapier waits for that event and nothing else.
Action
What the Zap does after it starts: the step that writes, sends or moves something in an app on your behalf.
Task
The unit Zapier bills. One task is one action your Zap completes successfully; your plan counts those and only those.
Instant vs polling
An instant trigger is reported by the app itself, the moment it happens. A polling trigger is checked on a timer, keeping only what is new.
Filter
A step that lets the Zap continue only when what arrived meets a condition you set, and quietly stops it otherwise.
Search step
A step that looks up something that already exists in an app, so the steps after it can use what it found.
Connection
Your OwnerRez account linked to Zapier once, then reused by every step in every Zap that touches OwnerRez.
Cost

What a Zap with OwnerRez really costs

OwnerRez is not reserved for paid plans, so the free plan can run it. You pay in tasks, and only successful actions spend them.

  • Booking or contact event0 tasks
  • Each successful OwnerRez action1 task
  • Free plan100 tasks a month, 2 steps per Zap
  • OwnerRez on the free planYes

The four triggers cost nothing, and because they are instant, the check interval of your plan does not apply to them. Each OwnerRez action that goes through is one task; a failed one is not counted. The free plan gives 100 tasks a month and Zaps of two steps, one trigger and one action. Add a filter, a second action or a search and the Zap becomes multi-step, which needs a paid plan. A few apps and actions take more than one task, though nothing here marks an OwnerRez action as one of them.

Connect

Connect your OwnerRez account in three steps

  1. 01

    Open the Apps page

    In your Zapier account, go to Apps and click + Add connection. You need an OwnerRez account, plus access to any property or record you do not own yourself but want the Zap to touch.

  2. 02

    Find OwnerRez and add it

    Type OwnerRez in the search box of the dialog, pick it from the results, then click Add connection. Zapier then opens a new tab on the OwnerRez side for the sign-in.

  3. 03

    Sign in and allow access

    Log in to OwnerRez in that tab and grant Zapier access to the account. The connection is saved once, and every OwnerRez trigger, action and search reuses it afterwards.

First Zap

Your first Zap: tag and label every new booking

GoalEach real booking created in OwnerRez gets a tag and a custom field value, ready for your team, without anyone touching it.

  1. 01

    Pick the trigger

    Start building: choose OwnerRez as the app that starts the Zap and Booking Created as the event, then select your connection.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent bookings of the account, so you set up the next steps on a real one instead of a guess.

  3. 03

    Add a filter (paid plan)

    Pick a value from the booking, a rule and the value to compare with, so blocked-off dates stop here. This trigger fires for both, and only real stays should go on.

  4. 04

    Add Add Tag

    Choose OwnerRez with Add Tag, set the Record Type to the booking and type the Tag your team filters on. Test the step and check the tag in OwnerRez.

  5. 05

    Add Set Custom Field, then publish

    Add Set Custom Field, pick the Field Definition ID and the Value. Test it, then click Publish. New to the editor? See the Zapier training.

Triggers

OwnerRez triggers

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

1

Booking Created

Instant trigger

In Zapier“Triggers when a new booking is created or blocked-off is added.”

Starts the Zap whenever a booking lands in OwnerRez, and also whenever someone blocks off dates on the calendar. Both arrive through the same door, which is the detail most people miss.

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 new stay should trigger a cleaning request, a row in the owner's revenue sheet or a welcome email.
Watch out
without a filter, an owner blocking a weekend for personal use will run the same steps as a paying guest.
2

Booking Updated

Instant trigger

In Zapier“Triggers when a booking is changed.”

Fires on any change to an existing booking in OwnerRez, so the rest of your tools hear about it instead of working from the old version. It covers edits of every kind, not one specific field.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
housekeeping needs a heads-up when a checkout date shifts, or the owner report has to reflect the new stay.
Watch out
a Zap that runs Modify Booking on the booking it was triggered by changes it again, and starts itself in a loop.
3

Contact Created

Instant trigger

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

Reacts to every new contact saved in OwnerRez, so a guest record can travel to the rest of your tools the moment it exists. It does not care whether the person has booked yet.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
new guests should join your newsletter list or your CRM without a weekly export.
Watch out
contacts that existed before you published are never sent; moving that backlog is a separate job.
4

Contact Updated

Instant trigger

In Zapier“Triggers when a contact's information changes.”

Picks up every change to a contact's information in OwnerRez and hands the updated record to the next steps. Useful to keep a copy elsewhere honest.

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 guest corrects their email address and your marketing tool should stop writing to the old one.
Watch out
pair it with Contact Created when you sync guests, or new records only travel once they are edited.
Actions

OwnerRez actions

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

1

Modify Booking

Action

In Zapier“Modify a booking.”

Changes an existing booking in OwnerRez from a Zap, so an update made in another tool does not have to be retyped. Test it on a real booking first to see what it changes.

When to use it
a change confirmed by the guest in a form should land on the booking itself.
Watch out
never pair it with Booking Updated on the same booking, or the Zap feeds itself.
2

Set Custom Field

Action

In Zapier“Sets the value of a custom field on a record.”

Writes a value into one of your custom fields on a record. It needs the Field Definition ID, which points at the field, and the Value to store.

When to use it
a door code generated in another tool should sit on the booking where your team already looks.
Watch out
the custom field has to exist in OwnerRez before the Zap can fill it.
3

Clear Custom Field

Action

In Zapier“Remove any value set on a custom field.”

Empties a custom field on a record, whatever value it held. The Field Definition ID is the one required box, and it tells OwnerRez which field to wipe.

When to use it
once a stay is over, a temporary access code stored on the booking should disappear.
Watch out
the field is the only thing it asks for, so a wrong Field Definition ID wipes the wrong field.
4

Add Tag

Action

In Zapier“Add a tag to a record.”

Sticks a tag on an OwnerRez record so your team can filter and sort it inside OwnerRez. Two boxes are required: the Record Type, which says what kind of record you are tagging, and the Tag itself.

When to use it
bookings from a given channel or form should carry a label your housekeeping view filters on.
5

Remove Tag

Action

In Zapier“Remove a tag from a record.”

Takes a tag off a record once it no longer applies. The only required box is the Tag to remove, so check the spelling matches the one you added.

When to use it
a booking tagged as awaiting deposit is marked paid in your accounting tool, and the tag should go.
Searches

OwnerRez searches

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

A search step finds something that already exists in OwnerRez and passes it to the steps that follow. In the editor, searches sit at the bottom of the Action event list, under SEARCH. All three OwnerRez searches work from an ID, and adding one makes the Zap multi-step.

1

Booking Lookup

Search

In Zapier“Finds a booking by ID.”

Fetches a booking from its ID, so the steps after it can work with that booking even when the Zap started in another app.

When to use it
a Zap started in another app holds a booking ID and needs the whole booking to write a message.
Watch out
without an ID from an earlier step, there is nothing to look up.
2

Guest Lookup

Search

In Zapier“Finds a guest by ID.”

Retrieves a guest record by its ID and hands it to the next steps of the Zap. It finds by ID only, not by name or email.

When to use it
an earlier step holds the guest's ID and your welcome email needs the guest record behind it.
3

Property Lookup

Search

In Zapier“Finds a property by ID.”

Looks up a property from its ID, so the Zap knows which rental it is dealing with before acting.

When to use it
a cleaning request in your task tool should name the property it concerns, once an earlier step has given you its ID.
Watch out
like the other two, it needs an ID mapped from an earlier step.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap there and skips the steps that needed it. Switched on, the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    On apps that offer it, this turns a search into find-or-create. OwnerRez exposes no such variant, so its searches only find, they never create.
  3. If multiple search results are found?
    Three ways out when several items match: keep the first one, which is the default, stop the Zap, or pass all of them on at once.
When it breaks

When the OwnerRez Zap breaks

Zapier links no help article to OwnerRez, and no limit specific to the app is documented. What breaks is what breaks on any Zap, plus two traps that come from the triggers themselves.

  • Blocked-off dates run like bookings

    Booking Created also fires when dates are blocked off. Without a filter, an owner's personal weekend gets the same cleaning request and welcome email as a guest.

  • A booking that keeps updating itself

    Booking Updated plus Modify Booking on the same booking sets the Zap off again and again, and burns through your task count fast.

  • Past bookings and contacts never arrive

    A Zap only reacts to what happens after you switch it on. Existing bookings and guests are not picked up; moving them is a separate job.

  • An import floods the Zap

    After a bulk import or a migration, a trigger that suddenly sends a huge batch can be held back by Zapier's flood protection.

  • The search stops the Zap

    A lookup that finds nothing stops the Zap by default. Check that the ID really comes from the earlier step, or switch on the setting to carry on.

  • The custom field cannot be picked

    Set Custom Field and Clear Custom Field need a Field Definition ID. If the custom field was never created in OwnerRez, there is nothing to choose.
Need help

Need help automating OwnerRez with Zapier?

A person reads every message.

FAQ

OwnerRez and Zapier: the questions people ask

01Is the OwnerRez Zapier integration free?
Yes. Zapier does not reserve OwnerRez for paid plans, so its triggers, actions and searches all work on the free plan. That plan gives you 100 tasks a month and as many Zaps as you like, but each Zap stops at two steps: one trigger and one action. Booking Created followed by Add Tag fits. Add a filter to skip blocked-off dates, a second action or a lookup, and the Zap becomes multi-step, which needs a paid plan.
02How many tasks does an OwnerRez Zap use?
One task per action that succeeds. The four triggers never cost a task, however many bookings and contacts come through, and an action that fails is not counted against your plan. A Zap that tags each new booking spends one task per booking. One that tags it and sets a custom field spends two per booking, since every successful action counts on its own. A loop between Booking Updated and Modify Booking is the fastest way to empty a plan.
03Does OwnerRez trigger Zaps in real time?
Yes. All four OwnerRez triggers are instant: OwnerRez itself tells Zapier when a booking or a contact is created or changed, and the Zap starts right away. The plan interval grid (15 minutes on Free, 2 on Professional, 1 on Team and Enterprise) only applies to polling triggers, so it does not slow these down. On the free plan, an OwnerRez Zap starts as fast as on a paid one. In the editor, a Zap built on an instant trigger shows a lightning bolt.
04What does it take to connect OwnerRez to Zapier?
An OwnerRez account, plus access to any property or record you do not own yourself but want the Zap to touch. In Zapier, open the Apps page, click + Add connection, search for OwnerRez and click Add connection. Sign in to OwnerRez in the tab that opens and grant Zapier access. The connection is stored once and reused by every OwnerRez step. Before building, create in OwnerRez the custom fields your Zaps will fill, since those actions need a Field Definition ID.
05Why does Booking Created fire for dates that are not bookings?
Because that trigger covers two events: a new booking, and dates being blocked off on the calendar. Both start the Zap the same way, so anything downstream treats an owner's personal block like a paying stay. The fix is a filter right after the trigger that lets only real bookings through. Keep in mind that a filter makes the Zap multi-step, so it needs a paid plan. On the free plan, the only alternative is to accept both kinds of event.
06What if the OwnerRez operation needed is not on Zapier?
Then Zapier cannot do it for OwnerRez today. The app page shows twelve visible operations, read on version OwnerRezCLIAPI@1.0.6 in October 2026: four triggers, five actions and three searches. There is no action to create a booking or a contact, and the searches only find by ID. Anything beyond that list is done in OwnerRez itself. Within the list, tags and custom fields are the most flexible tools, since they let you store almost any marker on a record.
07Zapier, Make or n8n for OwnerRez?
Decide on criteria rather than reputation. On Zapier, OwnerRez offers four instant triggers, five actions and three ID-based searches, works on the free plan and costs one task per successful action. That fits well if your Zaps start from bookings and contacts and mostly tag or label records. It fits less if you need to create bookings, or to search by name or date, since Zapier offers neither here. Check whether the other tool exposes those operations for OwnerRez, and how it bills each run.
Same platform

Other docs you might need on this stack.

Browse all integrations