Run Fastkey criminal record checks for new BambooHR employees.
When a new employee record is created in BambooHR, trigger a criminal background check in Fastkey.
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.
Fastkey Explore Fastkey →
TriggersFires when a lock managed by Fastkey is unlocked.
Fires when Fastkey grants someone access to a space.
Fires when a visitor or guest checks in via Fastkey.
Creates a new access code or key via Fastkey.
Revokes a guest's or employee's access in Fastkey.
Registers a visitor or guest in Fastkey.
BambooHR Explore BambooHR →
TriggersFires when a new employee is added in BambooHR.
Fires when a field on an employee's profile changes in BambooHR.
Fires when an employee is offboarded in BambooHR.
Fires when an employee requests time off in BambooHR.
Creates a new employee record in BambooHR.
Updates a field on an employee's record in BambooHR.
Syncs an employee's active/terminated status in BambooHR.
Approves or denies a time-off request in BambooHR.
Common questions
Can Knit build “Run Fastkey criminal record checks for new BambooHR employees.” between Fastkey and BambooHR?
Yes — describe it in the box above and Knit's Integrations Agent researches Fastkey and BambooHR'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.