Officemaps + StackGo
Officemaps at the intake step of a compliance workflow.
Officemaps publishes 0 trigger events and 4 actions on its public Zapier listing. That is what a StackGo connector would be built on.
Also listed under Client onboarding
OfficeMaps giving employees better flexibility and control over their working environments with desk, room, and asset booking management.
Description supplied by Officemaps.
Named fields, not a link to a portal. These are the fields StackGo writes on the systems it connects to today; a Officemaps connector would offer the same.
- Verification status
- Risk rating
- Last checked
- Report link
- Verified name
- Date of birth
- Document checked
- Screening result
- Beneficial owners
- Form responses
- Verification report (PDF)
Every field is optional. What each one holds, and which carry personal data, is set out once in what “integrates with” actually means.
- Create User
Officemaps's own write operations. The result goes onto the record you already work in.
Officemaps’s public integration surface
The rest of what Officemaps exposes on Zapier, beyond the ones above. This is the raw material a connector would use.
- Update User
- Find User
- Find Site Level Names
Names are Officemaps’s own, read from its public Zapier listing on 28 August 2026.
Common questions about Officemaps
How would a check result show up in Officemaps?
Through Officemaps’s own write operations: “Create User”. You choose which fields are written, and you can also run it one-way, with nothing written back to Officemaps at all.
Questions taken from what people actually search in Australia. We answer only the ones our own data answers.
Officemaps is made by zapier.com/officemaps.com. We are not affiliated with them.
Want Officemaps connected?
Requests decide the build order. Tell us and we will tell you where it sits.
Request this integrationReady to make onboarding minutes, not hours?
Start free and run your first check today, or book a demo and we will walk you through it.