Resources · Zapier integration

Livvi Zapier integrationAutomate Livvi with Zapier.

The Livvi Zapier integration gives you 3 actions, with no trigger and no search. Another app starts the Zap, and Livvi then creates or edits a booking, reads one back, or deletes it. Here is what each action does, what it costs and where it trips people up.

See the 3 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Livvi Zapier integration does for you

The Livvi Zapier integration lets Zapier, a service that chains steps between apps, write into Livvi, an access control platform for places such as apartments, holiday rentals and offices. Something happens in another tool, and Zapier turns it into a Livvi booking, or removes one.

Bookings that come from your planning sheet. When a stay or a visit is added as a row in your spreadsheet, Create or Edit a Booking writes it into Livvi. The same action also updates a booking that already exists, so the sheet can stay the place where you plan.

Cancellations that reach Livvi. Delete a Booking removes a booking when it is cancelled somewhere else, instead of leaving it to someone who remembers to do it by hand.

Booking details handed to the next step. Get a Booking reads a booking back from Livvi, so a later step can use what it holds, in a message or a line in a report.

What Zapier does not do here: start a Zap from Livvi. The app has no trigger on Zapier, so Livvi never tells Zapier that something changed on its side. Every Livvi Zap starts in another app and ends in Livvi. There is no search step either.

Before picking a tool, n8n vs Zapier and Make vs Zapier set out the criteria for each.

Vocabulary

Zapier vocabulary in one minute

Six words carry this page. Each one is explained here once, in plain English.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run each time the starting event happens.
Trigger
The event in an app that starts the Zap. Livvi has none, so the trigger always comes from another app you use.
Action
What the Zap does once started: the step that writes, sends or moves something. Livvi offers three, all about bookings.
Task
The unit Zapier bills: one action your Zap completes successfully. The allowance on your plan is counted in those.
Polling trigger
A trigger Zapier checks on a timer, asking the app for new items at a fixed interval and keeping only what it has not seen.
Filter
A step that lets the Zap go on only when what arrived meets the condition you set, and stops it otherwise.
Cost

What a Livvi Zap really costs

Livvi is not a premium app on Zapier, so it is available on the free plan. You pay in tasks, one for each Livvi action that goes through.

  • Premium appNo, works on the free plan
  • Free plan100 tasks a month, two-step Zaps
  • BilledEach successful Livvi action
  • Livvi triggersNone, the Zap starts elsewhere

The trigger of the other app never costs a task, and neither do Zapier's checks for new items. Each action that succeeds counts once, so a Zap that reads a booking with Get a Booking and then edits it uses two tasks. A failed action is not counted. The free plan gives 100 tasks a month and unlimited Zaps, but only two steps: one trigger and one action. A filter or a second action makes a multi-step Zap, which needs a paid plan. The grid below shows how often Zapier checks a polling trigger on each plan; with Livvi it applies to the trigger of the app that starts the Zap, if that trigger is a polling one.

Connect

Connect Livvi to Zapier in three steps

  1. 01

    Open your app connections

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

  2. 02

    Pick Livvi

    Type Livvi in the dialog's search box, select it and click Add connection. You need a Livvi account, plus access to the places and bookings that you do not own yourself but want the Zap to touch.

  3. 03

    Sign in and allow access

    Livvi opens in a new tab. Sign in there and grant Zapier access to the account. The connection then appears in your list, ready for the three Livvi actions.

First Zap

Your first Livvi Zap: bookings from a planning sheet

GoalEach time a row is added to your planning spreadsheet, create the matching booking in Livvi, but only for rows that meet the condition you choose.

  1. 01

    Start from your spreadsheet

    Create a Zap and pick your spreadsheet as the app that starts it, with its event for a new row. Test it so Zapier brings back real rows to work with.

  2. 02

    Add a filter

    Click the plus icon and add a Filter step. Fill its three boxes: the column to look at, the rule, and the value to compare with. Rows that fail it stop here.

  3. 03

    Add the Livvi action

    Add Livvi as the action app with Create or Edit a Booking and pick your connection. Map the values from the row into the fields the action asks for.

  4. 04

    Test the booking

    Run the action test once, then open Livvi and check that the booking is there with the right details. If something landed in the wrong field, fix the mapping now.

  5. 05

    Publish

    Publish the Zap to switch it on. With the filter it is a multi-step Zap, so it needs a paid plan; drop the filter and the two-step version runs on the free one.

Actions

Livvi actions: create, read and delete bookings

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

1

Create or Edit a Booking

Action

In Zapier“Creates or Updates a new booking.”

Writes a booking into Livvi, either a brand-new one or an update to one that already exists. It is the action most Livvi Zaps are built around.

When to use it
a stay or a visit planned in another tool should exist in Livvi without being typed twice.
Watch out
one action covers both cases, so check in the test whether your run created a booking or changed an existing one.
2

Delete a Booking

Action

In Zapier“Deletes a integration booking.”

Removes a booking from Livvi. Use it when the plan that created the booking no longer holds, so Livvi does not keep a booking that nobody will use.

When to use it
a cancellation recorded in your planning tool should also clear the booking in Livvi.
Watch out
the test step really runs the deletion, so try it on a booking you can afford to lose.
3

Get a Booking

Action

In Zapier“Get a Integration Booking.”

Reads one booking back from Livvi and hands its details to the steps that follow. It changes nothing in Livvi; it only fetches.

When to use it
a message or a report later in the Zap needs what the booking holds.
Watch out
it is an action, not a search, so a successful read still costs a task and adds a step to the Zap.
When it breaks

When a Livvi Zap breaks

Zapier attaches no help article to Livvi, so the cases below are the general limits that apply to a Zap ending in Livvi.

Four situations explain most Livvi Zaps that do not behave as expected. For anything else, the Zapier troubleshooting page goes further.

  • Old rows never become bookings

    A Zap only reacts to what happens after it is switched on. Rows or events that existed before you published are never sent to Livvi; moving them is a separate job.

  • A sudden batch is held back

    If the starting app suddenly returns a huge batch, after a bulk import for instance, Zapier's flood protection can hold those items back instead of running them all.

  • The same row does not run twice

    On a polling trigger, Zapier keeps track of what it has already seen, so an item that was handled once does not start the Zap again.

  • A second step needs a paid plan

    On the free plan a Zap stops at one trigger and one action. A filter, or Get a Booking followed by another action, makes it multi-step and needs a paid plan.
Need help

Need help automating Livvi with Zapier?

A person reads every message.

FAQ

Livvi Zapier integration: common questions

01Is the Livvi Zapier integration free?
Yes. Livvi is not a premium app, so the free Zapier plan can use it, with 100 tasks a month and unlimited Zaps. The limit is the shape of each Zap: one trigger and one action. A new spreadsheet row that creates a booking fits. Reading a booking with Get a Booking and then sending its details somewhere takes two actions, which makes a multi-step Zap and needs a paid plan. You also need your own Livvi account.
02How many tasks does a Livvi Zap use?
One per Livvi action that succeeds, and nothing for the trigger of the app that starts the Zap. A Zap that creates a booking for each new row uses one task per row. Get a Booking counts too, even though it only reads, so a read followed by an edit costs two tasks per run. A failed action is not counted against the plan. With 100 tasks a month on the free plan, count your runs before adding a read.
03Can a Livvi Zap react in real time?
Livvi itself has no trigger, so it never starts a Zap. How fast a Livvi booking is created depends on the trigger of the app you start from. If that trigger is instant, the app tells Zapier as soon as the event happens and the Livvi action follows right away. If it is a polling trigger, Zapier checks at the interval of your plan, every 15 minutes on the free one, before running the Livvi step.
04What does it take to connect Livvi to Zapier?
A Livvi account, plus access to the places and bookings you want the Zap to touch if they are not yours. In Zapier you open the Apps page, click + Add connection, pick Livvi, then sign in on the tab that opens and grant access. The connection is saved once and reused by every Livvi step, so you only do this once. Since Livvi has no trigger, you will also need a connection to the app that starts each Zap.
05Why can't a Zap start when something changes in Livvi?
Because the Livvi app on Zapier has no trigger at all: only three actions. Livvi never tells Zapier that a booking was created, changed or deleted on its side. Every Livvi Zap therefore starts in another app, such as a spreadsheet, a form or a calendar, and ends in Livvi. If you need to react to changes made inside Livvi, Zapier cannot do it with this integration. Plan the starting app first, then build.
06What if the Livvi operation you need is not there?
Then Zapier cannot do it with this app, because the three booking actions are the whole offer: no trigger, no search and no raw request step. Check first whether Create or Edit a Booking covers the need, since it handles both new bookings and changes. If nothing fits, the step stays manual in Livvi, or another automation tool has to be compared for what it offers on Livvi. Write the need down before choosing.
07Zapier, Make or n8n for Livvi?
Decide on criteria, not on a ranking. On Zapier, Livvi brings 3 actions and no trigger, so the real question is which app will start your Zaps and how often. Count the actions per run, since each successful one is billed, Get a Booking included. Check whether two steps are enough, since anything longer needs a paid plan. Then compare those same points across the three tools with your own booking flow in hand.
Same platform

Other docs you might need on this stack.

Browse all integrations