Create OfficeMaps users from new starters in People HR.
When a new starter is added in People HR, create a corresponding user profile in OfficeMaps.
See all OfficeMaps + People HR integrations or talk to a human
4.9/5 on G2·
Google for Startups Accelerator
How Knit builds this workflow
The Agent researches both APIs and wires the trigger on one side to the action on the other — no pre-built connector required. Here is the vocabulary it has to work with.
OfficeMaps Explore OfficeMaps →
TriggersFires when a new booking or appointment is made in OfficeMaps.
Fires when a booking in OfficeMaps is changed or canceled.
Fires when a new customer books for the first time in OfficeMaps.
Creates a new booking or appointment in OfficeMaps.
Cancels or moves a booking in OfficeMaps.
Creates or updates a customer record in OfficeMaps.
Adds a booking from OfficeMaps to a connected calendar.
People HR Explore People HR →
TriggersFires when a new employee is added in People HR.
Fires when a field on an employee's profile changes in People HR.
Fires when an employee is offboarded in People HR.
Fires when an employee requests time off in People HR.
Creates a new employee record in People HR.
Updates a field on an employee's record in People HR.
Syncs an employee's active/terminated status in People HR.
Approves or denies a time-off request in People HR.
Common questions
Can Knit build “Create OfficeMaps users from new starters in People HR.” between OfficeMaps and People HR?
Yes — describe it in the box above and Knit's Integrations Agent researches OfficeMaps and People HR's public API docs (or your own uploaded docs) and builds a working workflow, whether or not either app already has a pre-built connector.
How long does it take to build?
Minutes to a first working version, not weeks — you test it against real data before it goes anywhere near production.