OfficeMaps Zapier integrationAutomate OfficeMaps with Zapier.
The OfficeMaps Zapier integration gives you 0 triggers, 2 actions and 1 search. It manages the people who book desks, rooms and equipment: add a newcomer, update a profile, or find who already has an account, all from the tools your team already runs.
Verified Trustpilot reviews · AI, automation & growth agency
What the OfficeMaps Zapier integration actually does
OfficeMaps lets employees book their desk, a meeting room or a piece of equipment in a shared workplace. The Zapier integration keeps the list of people who can book in step with your other tools: users are created, updated and looked up automatically, so nobody has to maintain that list by hand any more.
Three outcomes teams usually build. An account ready on day one: a new employee in your HR tool becomes an OfficeMaps user through Create User, so the first booking works on arrival. A profile that follows changes: when someone changes their name or email elsewhere, Find User locates them and Update User applies the change. No duplicates: the find-or-create option of Find User creates the person only if nobody matches.
What Zapier does not do for OfficeMaps: there is no trigger. A new booking, a cancelled room or a person added inside OfficeMaps cannot start a Zap, so nothing flows out of the app. Every Zap starts in another tool and writes into OfficeMaps. The integration also deals only with users: bookings, desks and rooms stay out of reach of any Zap, whatever plan you are on.
Not sure Zapier is the right tool for this job? The n8n vs Zapier comparison lays out the criteria side by side.
Zapier vocabulary in one minute
Eight words you will meet in the editor. Each one is explained here once, then used as is on the rest of the page.
- Zap
- The automation you build: one trigger, then one or more actions that run every time that event happens.
- Trigger
- The event that starts the Zap. OfficeMaps has none, so with this app it always comes from another tool.
- Action
- What the Zap does once started. Here, it creates or updates a user in OfficeMaps on your behalf.
- Task
- The unit Zapier bills: one action the Zap completes successfully. Your plan allowance counts those, nothing else.
- Polling vs instant
- A polling trigger is checked on a timer. An instant trigger is reported by the app itself as soon as the event happens.
- Filter
- A step that lets the Zap go on only when what arrived meets your condition, and stops it quietly otherwise.
- Search step
- A step that looks up something already stored in an app, here a user, so later steps can use what it found.
- Connection
- Your OfficeMaps account linked to Zapier once, then reused by every Zap and every step that needs it.
What it really costs you
OfficeMaps is not a premium app, so it works from the free plan. Each Create User or Update User that goes through counts as one task; one that fails is not counted.
- Trigger cost0 tasks, whatever the volume
- Each user created or updated1 task (a failed action is not counted)
- Free plan100 tasks a month, two-step Zaps only
- Premium appNo, available from the free plan
The free plan gives you 100 tasks a month and Zaps of two steps: a trigger in another app, then one OfficeMaps action. That covers creating users. Updating them needs Find User first to get the Person ID, and a search makes the Zap multi-step (more than one trigger and one action), so it needs a paid plan. How fast it reacts depends on the other app's trigger: instant ones fire at once, polling ones follow the grid below.
Connect OfficeMaps to Zapier in three steps
- 01
Open your connections
In Zapier, open the Apps page of your account and click + Add connection. You need an OfficeMaps account that is allowed to manage the users of your workplace.
- 02
Pick OfficeMaps
Type OfficeMaps in the search box of the dialog, select it, then click Add connection. A new browser tab opens on the OfficeMaps side, where you finish the job.
- 03
Sign in and allow access
Log in to OfficeMaps in that tab and grant Zapier access to the account. The connection then appears in your list, ready for every Zap that writes users.
Your first Zap: keep OfficeMaps profiles up to date
GoalWhen an employee record changes in your HR tool, find the matching OfficeMaps user and apply the change.
- 01
Build the trigger
Create a Zap and pick your HR tool as the trigger app, with the event that fires when an employee record changes. Connect the account the HR team uses.
- 02
Test with real data
Run the test. Zapier brings back the three most recent changes, so you map the next steps on a real employee and see which fields carry the email and the name.
- 03
Add Find User
Add OfficeMaps and
Find User, then fill in the fields it should match with values from the test. This search step makes the Zap multi-step, so it needs a paid plan. - 04
Add Update User
Add
Update User, put the Person ID thatFind Userreturned in the Person ID field, then map the new name or email from the HR record. - 05
Test, then publish
Run each step once and check the profile in OfficeMaps. When it looks right, click Publish: every HR change now reaches the booking tool on its own.
OfficeMaps actions
OfficeMaps gives you 2 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Create User
ActionIn Zapier“Create a new user in OfficeMaps.”
Adds a person to OfficeMaps so they can book a desk, a room or equipment, from a record that started in another tool.
Update User
ActionIn Zapier“Update a user based on their PersonID”
Changes an existing OfficeMaps profile, for example a new surname or a different email, without anyone opening the admin screens.
The OfficeMaps search
1 search step looks for data that already exists in OfficeMaps, so a later step can use it.
A search step does not change anything: it looks for a user who already exists and hands their details to the next step. Three settings decide what happens when the result is not the one you expected.
Find User
SearchFind or createIn Zapier“Finds a user or users based on multiple fields combined in an AND statement.”
Looks for one or more OfficeMaps users who match every field you fill in at once, then passes what it found, including the Person ID, to the next step.
The three settings every search exposes
- Successful if no search results are found?Left on its default, a search that finds nobody stops the Zap there. Switched on, the Zap carries on empty-handed.
- Create … if it doesn't exist yet?Ticking it turns the search into a find-or-create: it drops the setting above and asks for what is needed to create the person.
- If multiple search results are found?Keep the first match, which is the default, stop the Zap, or hand every match to the next steps at once.
When it breaks
Zapier links no help article to OfficeMaps, so the cases below combine the general limits of Zapier with what the OfficeMaps fields require.
Most of them do not throw a clear error: the Zap runs, but the profile does not look the way you expected. When you cannot see why, our Zapier troubleshooting page walks through the checks in order.
The update finds no one to change
Update User needs the Person ID that OfficeMaps returns. Without a Find User step before it, there is nothing reliable to put in that required field.The search stops the Zap
Several fields are combined, so all of them must match. One value typed differently in the HR tool is enough for Find User to come back empty and stop the Zap.Existing staff are never created
A Zap only reacts to what happens after it is switched on. People hired before stay outside OfficeMaps; bringing them in is a separate job.A bulk import gets held back
If your HR tool returns a huge batch at once, after a migration for example, Zapier's flood protection can hold it back instead of creating every user.
Need help automating OfficeMaps with Zapier?
A person reads every message.
