- Home
- Resources
- Integrations
- LimoExpress
LimoExpress Zapier integrationAutomate LimoExpress with Zapier.
The LimoExpress Zapier integration gives you 9 triggers, 2 actions and 1 search. Enough to follow every reservation from booking to no-show, track invoices and new clients, and create clients or bookings in LimoExpress from your other tools.
Verified Trustpilot reviews · AI, automation & growth agency
What the LimoExpress Zapier integration does for you
Connecting LimoExpress to Zapier means a Zap, the automation you build on Zapier, keeps an eye on your limousine booking platform and passes what happens there to your other tools, or feeds it from them. Twelve operations are available: nine events to react to, two things to create, and one way to look up a reservation.
Three results worth building. A no-show log that keeps itself: Reservation Finished - No Show fires when a trip ends without its passenger, and a row lands in your spreadsheet, ready for the follow-up. Bookings that skip the retyping: a request comes through a form on your site, and Create Reservation puts it in LimoExpress with its pickup place, time and price. Cash in, on record: each Invoice Paid adds a line to the sheet that tracks what has been collected.
What Zapier does not do here. Nothing updates, cancels or deletes a reservation or a client: the two actions only create. The only search finds a reservation by its internal number, not by client or date. And none of the nine triggers is instant: they all work by polling, so Zapier checks LimoExpress on a timer, and a free plan sees changes later than a paid one.
If that set does not fit your case, see our Zapier alternatives page and our Zapier review.
Zapier vocabulary in one minute
Eight words come back all along this page. Here they are once, in plain English, so nothing slows you down later.
- Zap
- Your automation 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 switched on, Zapier waits for it to happen.
- Action
- What the Zap does once it has started: the step that creates, sends or writes something for you.
- Task
- The unit Zapier bills: one action your Zap completes successfully. Your plan's allowance counts these and nothing else.
- Polling trigger
- A trigger Zapier checks on a timer. It asks the app for its latest items and keeps only the ones it has not seen.
- Instant trigger
- A trigger the app reports itself, the moment the event happens. LimoExpress has none of these on Zapier.
- Filter
- A step that lets the Zap carry on only when what arrived meets your condition, and stops it there otherwise.
- Search step
- A step that looks up a record that already exists, so the steps after it can use what it found.
What a LimoExpress Zap really costs
LimoExpress is not a premium app, so it works from the free plan. Zapier counts in tasks, and the trigger never costs one.
- Premium appNo, available on the free plan
- Free plan100 tasks a month, two-step Zaps
- TriggerNever costs a task
- LimoExpress triggersAll polling, checked on your plan's timer
Each action that goes through counts once; one that fails is not billed. Zapier checking LimoExpress for new reservations costs nothing, however often it looks. A Zap that logs every no-show in a sheet spends one task per no-show. The free plan gives 100 tasks a month and Zaps of two steps only: one trigger, one action. Add a filter, a second action or Find Reservation, and the Zap becomes multi-step, which needs a paid plan. The plan also sets how often Zapier checks, as the grid shows.
Connect your LimoExpress account in three steps
- 01
Open the Apps page
In your Zapier account, go to Apps and click + Add connection. A connection is your LimoExpress account linked to Zapier once, then reused by every step that talks to it.
- 02
Pick LimoExpress
Type LimoExpress in the search box of the dialog, select it in the results and click Add connection. A new tab opens on the LimoExpress side, where the sign-in happens.
- 03
Sign in and allow access
Log in with your LimoExpress account and grant Zapier access. If the Zap will touch clients or reservations someone else manages, check first that this login has read or write rights on them.
Your first Zap: every no-show logged for follow-up
GoalWhen a LimoExpress reservation finishes as a no-show and meets your condition, add a row to your spreadsheet of no-shows.
- 01
Create the Zap
Start a new Zap from your Zapier dashboard. The editor opens on an empty trigger step, waiting for the app and the event that should set everything off.
- 02
Set the trigger
Pick LimoExpress, then
Reservation Finished - No Show, and choose your connection. Test it: Zapier brings back the three most recent matching reservations, so you map on a real one. - 03
Add the filter
From the plus icon, add Filter and fill its three boxes: the field to look at, the rule and the value to compare with. Only reservations that pass go on. This makes the Zap multi-step.
- 04
Add the spreadsheet row
Add your spreadsheet with the action that creates a row, and map each column from what the trigger brought back about the reservation.
- 05
Test, then publish
Run each step once, read what came back and check the row. Then click Publish. No-shows from before that moment are not added; on the free plan, new ones show up at the next check.
LimoExpress triggers in Zapier
9 events start a Zap when something happens in LimoExpress. Zapier checks for them at the interval your plan allows.
New Client
Polling triggerIn Zapier“Triggers when a new clients/partner is created.”
Starts the Zap for each client or partner newly added to LimoExpress. Both kinds of record come through the same trigger.
Invoice Paid
Polling triggerIn Zapier“Triggers when an invoice is paid.”
Fires when an invoice in LimoExpress is marked as paid. It is the moment money is confirmed, which makes it the right signal for anything financial.
New Passenger
Polling triggerIn Zapier“Triggers when a new passenger is created.”
Goes off each time a new passenger is created in LimoExpress, the person who actually rides, as opposed to the client who books.
Reservation Canceled
Polling triggerIn Zapier“Triggers when a reservation is canceled.”
Kicks off when a reservation is canceled in LimoExpress. The trip will not happen, and whatever was prepared around it may need undoing.
New Reservation
Polling triggerIn Zapier“Triggers when a new reservation gets created.”
Runs for every reservation newly created in LimoExpress, whoever entered it. This is the trigger most booking Zaps start from.
Reservation Finished
Polling triggerIn Zapier“Triggers when a reservation is finished.”
Fires once a reservation is marked as finished, the ride done and closed in LimoExpress.
Reservation Finished - No Show
Polling triggerIn Zapier“Triggers when a reservation is finished with a passenger NO SHOW.”
Reacts when a reservation closes with the passenger marked as a no-show. The driver went, the passenger did not.
Reservation Updated
Polling triggerIn Zapier“Triggers when a reservation is updated.”
Triggered whenever an existing reservation is changed in LimoExpress, whatever the change.
New Invoice
Polling triggerIn Zapier“Triggers when a new invoice is created.”
This one runs when a new invoice is created in LimoExpress, before anyone has paid it.
LimoExpress actions in Zapier
LimoExpress gives you 2 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Create Client
ActionIn Zapier“Create a client into LimoExpress platform.”
Adds a client to LimoExpress from data arriving elsewhere. It needs a full name, an email, a phone, an address and the commission percentage agreed with them.
Create Reservation
ActionIn Zapier“Create a reservation into LimoExpress platform.”
Books a trip straight into LimoExpress: pickup place, pickup time, price, whether it is paid, type, baby seats and suitcases.
LimoExpress search in Zapier
1 search step looks for data that already exists in LimoExpress, so a later step can use it.
A search step looks up something that already exists and hands it to the next steps. LimoExpress has one, and it finds a reservation by its internal number. You will find it at the bottom of the Action event list, under SEARCH.
Find Reservation
SearchIn Zapier“Finds a Reservation in the system”
Fetches a reservation from its internal number and passes its details to the steps that follow.
The three settings every search exposes
- Successful if no search results are found?Left as is, a search that finds nothing stops the Zap there and skips the steps that needed it. Switched on, the Zap goes on without the reservation.
- Create X if it doesn't exist yet?On apps that offer it, this box turns a search into find or create. Find Reservation has no such variant, so a missing reservation is never created this way.
- If multiple search results are found?Three ways out when several records match: keep the first one, which is the default, stop the Zap, or pass them all on at once.
When a LimoExpress Zap breaks
Zapier attaches no help article to LimoExpress, and no limit specific to the app is documented. What goes wrong comes from the rules every Zap follows.
Four situations explain most surprises, and all of them come from the rules every Zap follows rather than from LimoExpress. If one of them has you stuck, open our Zapier troubleshooting page.
The past is never picked up
A Zap only reacts to what happens after you publish it. Reservations, invoices or clients from before stay out; moving them is a separate job.A Zap that sets itself off
A Zap that writes where its own trigger watches, like New Reservation followed by Create Reservation, can restart on its own output and drain your tasks.A big batch gets held back
A bulk import of clients or reservations can make a trigger return a huge batch at once. Zapier's flood protection may hold it back.Edits never count as new
Zapier remembers what it has seen on a polling trigger. A client or passenger edited later is not new, so New Client or New Passenger stays silent.
Need help automating LimoExpress with Zapier?
A person reads every message.



