- Home
- Resources
- Integrations
- Lobbytrack
Lobbytrack Zapier integrationAutomate Lobbytrack with Zapier.
The Lobbytrack Zapier integration gives you 7 triggers, 6 actions and 0 searches. Sign-ins and sign-outs at the front desk can feed other apps, and other apps can add visitors or employees to Lobbytrack without anyone typing them twice.
Verified Trustpilot reviews · AI, automation & growth agency
What the Lobbytrack Zapier integration actually does
It connects your visitor desk to the rest of your tools. A Zap (the automation you build on Zapier) can start when someone signs in or out in Lobbytrack, or when a visitor, a visit or an employee record appears. It can also write into Lobbytrack: add a visitor, add an employee, or fetch the details of a record.
A visitor log that keeps itself. Visitor Signed In and Visitor Signed Out each start a Zap, so arrivals and departures end up in a spreadsheet or any app you already use for records.
A host directory that stays in step. When a new person joins your team in another app, Add Employee creates them in Lobbytrack with first name, last name and email, the three fields it requires.
Expected guests, already on the list. Add Visitor registers someone ahead of time, and its Is Blocked option puts that person on the watchlist instead.
What Zapier does not do with Lobbytrack: none of the 7 triggers is instant, so every one waits for Zapier's next check. There is no search step either. The four Get actions only accept an ID handed over by a Lobbytrack trigger, so you cannot look someone up by name. And no action signs a person out, edits or deletes a record: the actions add or read, nothing else.
There is no Lobbytrack page for Make or n8n on this site; see our n8n vs Zapier comparison.
Zapier vocabulary in one minute
Eight words come back on every line of this page. Here they are once, in plain language.
- Zap
- The automation itself: one trigger, then one or more actions that run each time the trigger event happens.
- Trigger
- The event that starts the Zap, such as a visitor signing in. Once the Zap is on, Zapier waits for it.
- Action
- What the Zap does once it has started: the step that writes, sends or moves something, like adding a visitor.
- 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 on a timer; an instant one is reported by the app at once. All Lobbytrack triggers are polling.
- Filter
- A step that lets the Zap continue only when what arrived meets your condition, and stops it otherwise.
- Connection
- Your Lobbytrack account linked to Zapier once, then reused by every Lobbytrack step in every Zap.
- Multi-step Zap
- Any Zap beyond one trigger and one action. A second action, a filter or a search makes one, and it needs a paid plan.
What a Lobbytrack Zap really costs
Lobbytrack is not a premium app: it works on the free plan. You pay in tasks, and only for actions that succeed.
- Free plan100 tasks a month, unlimited Zaps
- Free plan limitTwo steps: one trigger, one action
- Premium appNo, works on the free plan
- Instant triggers0 out of 7
The trigger never costs a task, however often Zapier checks Lobbytrack for new sign-ins. Each action that works counts as one task; one that fails is not counted. A sign-in that adds a row elsewhere is one task. Add a filter or a Get action in between and the Zap becomes multi-step, which needs a paid plan. All 7 triggers are polling, so the interval grid below decides how soon a sign-in is picked up.
Connect Lobbytrack to Zapier in 3 steps
- 01
Open the Apps page
In your Zapier account, go to Apps and click + Add connection. You need a Lobbytrack account first, plus access to any records you do not own yourself but want the Zap to read or write.
- 02
Pick Lobbytrack
Type Lobbytrack in the search box of the dialog, select it and click Add connection. A new tab opens on the Lobbytrack side so you can sign in there.
- 03
Sign in and grant access
Log in to Lobbytrack in that tab and allow Zapier to use the account. The connection then appears on your Apps page and every Lobbytrack step reuses it from now on.
Your first Zap: log each visitor sign-in, with a filter
GoalEach time a visitor signs in, a filter checks one field you choose, and only the matching sign-ins become a new row in your spreadsheet.
- 01
Create the Zap and pick the trigger
Start a new Zap, choose Lobbytrack and the Visitor Signed In event, then select your connection. This trigger is polling: Zapier checks Lobbytrack on your plan's interval.
- 02
Test it on a real sign-in
Run the test. Zapier brings back the three most recent sign-ins of the connected account, so you map the next steps on real visitor data rather than placeholders.
- 03
Add the filter
Click the plus icon, choose Filter, then set its three boxes: the field to look at, the rule, and the value. Use a text rule on text and a number rule on numbers.
- 04
Add the spreadsheet step
Add your spreadsheet app with its add-row action and map the visitor fields from the trigger into the columns you want. Test the step and check the row it creates.
- 05
Publish
Click Publish to switch the Zap on. With a filter it counts as multi-step, so a paid plan is required. From now on, each new matching sign-in costs one task.
The 7 Lobbytrack triggers
7 events start a Zap when something happens in Lobbytrack. Zapier checks for them at the interval your plan allows.
Employee Signed In
Polling triggerIn Zapier“Triggers when an employee signs in.”
Starts your Zap when a member of staff signs in at the desk. Each sign-in reaches the next steps with the employee's details, ready to be copied into another app.
Employee Signed Out
Polling triggerIn Zapier“Triggers when an employee signs out.”
The mirror of the previous one: the Zap runs when a member of staff signs out. Paired with the sign-in trigger in a second Zap, it gives you both ends of the presence.
New/Updated Employee
Polling triggerIn Zapier“Triggers when an employee / host is added or updated.”
Fires when an employee, also called a host in Lobbytrack, is added or changed.
New/Updated Visit
Polling triggerIn Zapier“Triggers when a visit is added or updated.”
Reacts to a visit being created or edited in Lobbytrack. The visit is the appointment itself, distinct from the person who comes, and it carries its own ID.
New/Updated Visitor
Polling triggerIn Zapier“Triggers when a visitor is added.”
Watches the visitor records, the people who come to your premises. The label says new or updated, while the official description only mentions visitors being added.
Visitor Signed In
Polling triggerIn Zapier“Triggers when a visitor signs in.”
Starts the Zap when a guest checks in at the front desk. It is the most direct way to know, in another app, that someone has arrived.
Visitor Signed Out
Polling triggerIn Zapier“Triggers when a visitor signs out.”
Runs when a guest signs out on leaving. Combined with the sign-in, it tells you who is still on site according to Lobbytrack.
The 6 Lobbytrack actions, grouped by what they do
Lobbytrack gives you 6 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Add Employee
ActionIn Zapier“Adds a new employee.”
Creates a new employee in Lobbytrack from data that arrives in another app. First name, last name and email are all required.
Add Visitor
ActionIn Zapier“Adds a new visitor.”
Registers a visitor in Lobbytrack with a first and last name, the two required fields. The optional Is Blocked switch adds the person to the watchlist.
Get Employee
ActionIn Zapier“Retrieves the details for an employee / host.”
Fetches the full details of an employee, or host, from the Employee ID a Lobbytrack trigger returned.
Get Location
ActionIn Zapier“Retrieves the details of a location.”
Reads the details of one of your Lobbytrack locations, using the Location ID that a trigger handed over.
Get Visit
ActionIn Zapier“Retrieves the details for a visit.”
Pulls the details of one visit from the Visit ID provided by a Lobbytrack trigger.
Get Visitor
ActionIn Zapier“Retrieves the details for a visitor.”
Looks up a visitor's record from the Visitor ID a Lobbytrack trigger returned, and passes it to the following steps.
When a Lobbytrack Zap breaks
Zapier attaches no help article to Lobbytrack, and the source gives no Lobbytrack-specific limit. The surprises come from how Zapier itself works.
Four situations account for most of them. If one hits you, see our Zapier troubleshooting page.
Past sign-ins are never picked up
A Zap only reacts to what happens after you switch it on. Visitors who signed in before that stay out of your log; moving that history is a separate job.A bulk import is held back
If Lobbytrack suddenly returns a huge batch, for example after importing a staff list, Zapier's flood protection can hold those items back.The same record does not fire twice
On a polling trigger Zapier remembers what it has already seen, so the same visitor or sign-in never starts the Zap a second time.A Zap that feeds its own trigger
New/Updated Employee plus Add Employee in one Zap is a loop: each new employee fires the trigger again and burns through your tasks fast.
Need help automating Lobbytrack with Zapier?
A person reads every message.



