Resources · Zapier integration

Lodgify Zapier integrationAutomate Lodgify with Zapier.

The Lodgify Zapier integration gives you 8 triggers, 0 actions and 0 searches. All eight are instant: a new booking, a status change or a guest message starts your Zap as soon as Lodgify reports it. Zapier listens to Lodgify here, it never writes back.

See the 8 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Lodgify Zapier integration actually does

The Lodgify Zapier integration links your Lodgify account, the vacation rental software you take bookings with, to Zapier, a service that passes events from one app to another. Lodgify is the listening side of the pair: it reports bookings, status changes and guest messages, and the other tools in your automation do the work that follows.

Three results come up again and again. A booking log that fills itself: New Booked Booking adds each confirmed stay to a spreadsheet, one row per booking, with nobody copying anything by hand. A heads-up for every guest message: Message Received in Thread pushes the text into the chat your team already reads, so a question does not sit unseen in a Lodgify thread. A clean trail of refusals: Booking Status Changed to Declined sends the declined request to your email tool or a list, which gives you one place to review what did not convert.

What Zapier does not do for Lodgify matters just as much. The app has no action and no search on Zapier, so a Zap cannot create a booking, edit one, change its status or look one up in Lodgify. Every change to a booking still happens in Lodgify itself; Zapier only carries the news out.

If writing back into Lodgify is the point of your project, see our platform comparisons before you build: the n8n vs Zapier and Make vs Zapier comparisons.

Vocabulary

Zapier words in one minute

Seven words come back on every line of this page. Here they are in plain terms, once.

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 Lodgify it is a booking, a status change or a guest message.
Action
What the Zap does once it has started: the step that writes, sends or moves something for you in another app.
Task
The unit Zapier bills: one action your Zap completes successfully. Your plan counts these and nothing else.
Polling vs instant
A polling trigger is checked by Zapier on a timer. An instant trigger is reported by the app itself the moment the event happens.
Filter
A step that lets the Zap go on only when what arrived meets your condition, and stops it there otherwise.
Connection
Your Lodgify account linked to Zapier once, then reused by every Zap and every step that uses Lodgify.
Cost

What a Lodgify Zap really costs

The Lodgify trigger itself never costs a task. Only the actions that follow it, in your other apps, are counted, and only when they succeed.

  • Lodgify trigger0 tasks
  • Each successful action1 task
  • Free plan100 tasks per month, unlimited Zaps
  • Free plan Zap size2 steps: one trigger, one action
  • Premium appNo, Lodgify works on the free plan

A Zap with three actions uses three times as much as a one-action Zap. An action that fails is not counted. Lodgify is not a premium app, so it works on the free plan, but that plan builds two steps only: one trigger, one action. A filter or a second action makes the Zap multi-step, and that needs a paid plan. The interval grid below is how often Zapier checks polling triggers on each plan; it does not apply to Lodgify, whose eight triggers are all instant.

Connect

Connect Lodgify to Zapier in three steps

  1. 01

    Open your connections

    In Zapier, go to the Apps page of your account and click + Add connection. The only prerequisite at this stage is a Lodgify account you can sign in to.

  2. 02

    Pick Lodgify

    Type Lodgify in the search box of the dialog, select it, then click Add connection. A new tab opens on the Lodgify side, which is where the next step happens.

  3. 03

    Sign in and allow access

    Sign in to Lodgify in that tab and grant Zapier access to the account. If the bookings you want to follow belong to someone else, make sure your login can at least read them.

First Zap

Your first Lodgify Zap: confirmed stays into a spreadsheet

GoalEach booking created as Booked in Lodgify adds a row to your spreadsheet, and only bookings that pass your filter get through.

  1. 01

    Create the Zap

    Start a new Zap, pick Lodgify as the app that starts it and choose New Booked Booking as the event. Select the Lodgify connection you added earlier.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent items of your account, so pick a real booked stay to map from rather than an empty sample.

  3. 03

    Add the filter

    Click the plus icon, choose Filter, then fill the three boxes: the field to look at, the rule, the value to compare with. Pick a text rule for text and a number rule for numbers.

  4. 04

    Add the spreadsheet step

    Add the action in your spreadsheet tool and map the booking details from the trigger into the columns. Test the step and read what came back. To build the habit on your own Zaps, the Zapier training is the next stop.

  5. 05

    Publish

    Click Publish to switch the Zap on. The filter makes it a multi-step Zap, so this one runs on a paid plan; drop the filter to keep it on the free plan.

Triggers

The 8 Lodgify triggers

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

1

Booking Change

Instant trigger

In Zapier“Triggers when a Booking is updated.”

Any update to an existing booking in Lodgify starts the Zap, and the booking as it now stands travels into the next step. It is the widest booking trigger of the eight, the one to pick when the change itself matters more than the status.

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 shared spreadsheet row in step with a booking, so whoever reads it sees the latest version and not the first one.
Watch out
only updates made after you publish the Zap count; a booking edited before that never reaches Zapier.
2

New Booking

Instant trigger

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

This one reacts to every booking created in Lodgify, whatever status it starts with, and hands it to the steps that follow. Nothing is sorted upstream: open, tentative and booked requests all come through the same door.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
feed one intake list where each new request lands once, then sort it by status in the tool that receives it.
Watch out
if only confirmed stays matter, New Booked Booking spares you a filter, and with it a multi-step Zap the free plan cannot run.
3

New Booked Booking

Instant trigger

In Zapier“Triggers when a new Booked Booking is created.”

Here the Zap waits for a booking that is created directly with the Booked status and lets the others pass by. It is the narrowest way to act on a confirmed stay from the moment it appears in Lodgify.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
add each confirmed stay to the spreadsheet your team works from, one row per booking.
Watch out
a booking that starts as Open or Tentative and gets confirmed later does not fire this trigger; Booking Status Changed to Booked covers that path.
4

Booking Status Changed to Booked

Instant trigger

In Zapier“Triggers when a Booking status changes to Booked.”

The Zap starts when an existing booking moves to the Booked status, whatever it was before. Zapier puts this trigger forward on the Lodgify page, and it is the one that catches confirmations made after the first request.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
send a confirmation email from your email tool once a request you were holding becomes a firm stay.
Watch out
a booking created straight as Booked belongs to New Booked Booking; run both Zaps if each path matters to you.
5

Booking Status Changed to Declined

Instant trigger

In Zapier“Triggers when a Booking status changes to Declined.”

As soon as a booking switches to Declined, this trigger passes it on. That gives you a clear signal for the requests that will not turn into stays, kept apart from everything else.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
log each declined request in its own spreadsheet tab so you can review them together later.
Watch out
refusals made before the Zap is published are never picked up; moving that history is a separate job.
6

Booking Status Changed to Open

Instant trigger

In Zapier“Triggers when a Booking status changes to Open.”

Bookings that change to the Open status set this Zap off. It tracks the requests that are still in play rather than the settled ones, which makes it a good watchlist feed.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
post a short note in your team chat whenever a booking moves to Open, so someone takes it from there.
Watch out
the trigger type comes from Lodgify itself and cannot be switched in the editor, so there is no timing setting to look for.
7

Booking Status Changed to Tentative

Instant trigger

In Zapier“Triggers when a Booking status changes to Tentative.”

When a booking takes the Tentative status, Zapier receives it and runs the steps you placed after it. It isolates the bookings that are neither confirmed nor refused 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
create a reminder in your task list for every tentative booking, so none of them waits without an answer.
Watch out
the test brings back the three most recent items of your account; without a recent tentative booking, you may have nothing realistic to map from.
8

Message Received in Thread

Instant trigger

In Zapier“Triggers when a new guest message is received in a thread.”

The only trigger of the set that is not about a booking: it fires when a guest writes a new message in a Lodgify thread. The message then feeds whatever step you add after it.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
forward each new guest message to the chat channel your team keeps open.
Watch out
Lodgify has no action on Zapier, so the reply itself is still written in Lodgify, never from the Zap.
When it breaks

When a Lodgify Zap breaks

Lodgify has no limit of its own listed for Zapier. What goes wrong comes from how Zapier works, and three cases cover most of it.

Each case below is a rule of Zapier rather than a bug in Lodgify. If a Zap still misbehaves after you checked them, the Zapier troubleshooting page is where to look next.

  • Old bookings never show up

    A Zap only reacts to what happens after it is switched on. Bookings and messages that already existed are not picked up; 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 starts again and again and burns tasks fast. Lodgify has no action, so watch for this in your other tools.

  • A big batch gets held back

    When a trigger suddenly sends a huge batch, after a bulk import or a migration, Zapier's flood protection can hold those items back instead of running them all.
Need help

Need help automating Lodgify with Zapier?

A person reads every message.

FAQ

Lodgify and Zapier: common questions

01Is the Lodgify Zapier integration free?
Yes, it works on the free plan, because Lodgify is not a premium app. The free plan gives you 100 tasks per month and as many Zaps as you like, but each Zap is limited to two steps: one trigger and one action. A Lodgify booking that adds a spreadsheet row fits. The moment you add a filter to keep only some bookings, or a second action such as an email on top of the row, the Zap becomes multi-step and needs a paid plan. The eight triggers stay instant on every plan, free included.
02How many tasks does a Lodgify Zap use?
The Lodgify trigger itself costs nothing, however many bookings come through. Each action that completes successfully counts as one task. A Zap that turns every new booking into a spreadsheet row uses one task per booking. Add an email after the row and the same booking costs two. An action that fails is not counted against the plan. A few apps and a few actions take more than one task, so check the action you pick in your other tool.
03Is the Lodgify Zapier integration real time?
Yes. All eight Lodgify triggers are instant: Lodgify tells Zapier as soon as a booking is created, changes status, or a guest writes, and the Zap starts right away whatever your plan. The polling grid of the plans, which sets how often Zapier checks other apps, does not apply here. In the editor, a Zap built on an instant trigger shows a lightning bolt. The type comes from Lodgify itself, so there is no timing setting to change.
04What do you need to connect Lodgify to Zapier?
A Lodgify account, and access to the bookings you want to follow. In Zapier, open the Apps page, click + Add connection, search for Lodgify, click Add connection, then sign in to Lodgify in the tab that opens and grant Zapier access. If some bookings or threads belong to someone else, your login needs at least read access to them. The connection is made once and every Lodgify step reuses it.
05Can Zapier create or update a booking in Lodgify?
No. Lodgify offers 0 actions and 0 searches on Zapier, only 8 triggers. A Zap can react to bookings, status changes and guest messages, but it cannot create a booking, change one, move its status or look one up in Lodgify. All of that stays in Lodgify. The usual pattern is the reverse: Lodgify starts the Zap, and the actions run in your spreadsheet, email tool, task list or chat. If your project depends on writing into Lodgify, that decides the platform question.
06What if the Lodgify trigger you need does not exist?
Start with the eight that are there. New Booking catches every new request whatever its status, and a filter after it can keep only the ones that match a field, a rule and a value, on a paid plan. Booking Change catches edits the status triggers miss. If none of them reports the event you are after, Zapier cannot invent it: the list stops at what Lodgify offers on Zapier. At that point, look at whether another platform reaches Lodgify differently before you build.
07Zapier, Make or n8n for Lodgify?
It depends on three criteria rather than on a winner. First, direction: on Zapier, Lodgify only sends events out, with 8 instant triggers and no action, so check what each platform offers if you need to write into Lodgify. Second, cost: Zapier bills each successful action as a task and never the trigger, so estimate your bookings and messages times your actions. Third, timing: every Lodgify trigger on Zapier is instant, so check that the platform you compare reports the same events as quickly. Weigh the three against your project, not against a ranking.
Same platform

Other docs you might need on this stack.

Browse all integrations