Onbee.app Zapier integrationAutomate Onbee.app with Zapier.
The Onbee.app Zapier integration offers 4 actions and no trigger, all on the free plan. Zapier can create or update an employee and create or update an inventory item, but a change inside Onbee.app never starts a Zap on its own.
Verified Trustpilot reviews · AI, automation & growth agency
What the Onbee.app Zapier integration does for HR
Onbee.app is an HR tool built around onboarding: it holds employee and contractor records and the equipment assigned to them. Connecting it to Zapier lets other tools feed those records, so nobody retypes a new hire's name or a laptop's details by hand. Data only flows into Onbee.app.
Three results justify the setup. A new hire who appears without retyping: Create Employee builds the record from a form, a recruiting tool or a signed offer, with first and last name as the only required fields. Equipment tracked from the purchase: Create Inventory adds an item when an order or a request comes in elsewhere, and Update Inventory keeps that item current. Profiles that stay in line with the rest of the company: Update Employee changes a record when the source of truth moves, a payroll tool or a staff directory for example.
What Zapier does not do here matters just as much. Onbee.app has no trigger, so an onboarding step completed in Onbee.app cannot notify another tool. There is no search either: the two update actions need an ID that an earlier step must supply. And there is no delete action in the editor.
Before choosing a tool for HR flows, the Zapier review and Make vs Zapier give the wider picture.
Zapier vocabulary in one minute
Eight words carry this page. Each one keeps the meaning given here.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run every time the trigger event happens.
- Trigger
- The event in an app that starts the Zap. Onbee.app has none, so another app always fills this role.
- Action
- What the Zap does after it starts: the step that writes, sends or moves something for you. All four Onbee.app operations are actions.
- Task
- The unit Zapier bills: one action your Zap completes successfully. The count on your plan is a count of those.
- Polling trigger
- A trigger Zapier checks on a timer, asking the app for new items at a fixed interval and keeping only the unseen ones.
- Instant trigger
- A trigger the app reports itself, calling Zapier the moment the event happens, with no wait for the next check.
- Filter
- A step that lets the Zap go on only when what arrived meets the condition you set, and stops it otherwise.
- Connection
- Your account of an app linked to Zapier once, then reused by every step that uses that app.
What Onbee.app costs in Zapier tasks
Onbee.app is not a premium app on Zapier, so it works on the free plan. You pay in tasks, and only actions that succeed count.
- Free plan100 tasks per month, unlimited Zaps
- Free plan Zap sizeOne trigger, one action
- Employee plus item in one ZapTwo tasks, paid plan
- Failed actionNot counted
Each employee or item created or updated successfully is one task. An action that fails is not billed. The trigger of the other app costs nothing, and neither do Zapier's checks on it. On the free plan, a Zap holds two steps: that trigger and one Onbee.app action. Creating an employee and their laptop in the same Zap means two actions, so a multi-step Zap that needs a paid plan, and two tasks per new hire. A filter that keeps only permanent contracts has the same effect on the plan.
Connect your Onbee.app account in three steps
- 01
Open the Apps page
In Zapier, go to Apps and click + Add connection. You need an Onbee.app account, plus write access on any employee or item you do not own and want the Zap to change.
- 02
Choose Onbee.app
Search Onbee.app by name in the dialog, select it and click Add connection. A tab opens where you sign in to the Onbee.app account your HR team uses.
- 03
Sign in and grant access
Sign in to Onbee.app in that tab and allow Zapier to reach the account. The connection then shows on the Apps page, ready for every Zap that writes to Onbee.app.
Your first Onbee.app Zap: a new hire form creates the employee and their laptop
GoalA manager answers the new hire form; Onbee.app gets the employee record and the equipment item in one go.
- 01
Pick the trigger app
Create a Zap and choose your form tool as the app that starts it, with its new-response event. Onbee.app cannot start a Zap, so this card is always another app.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent responses of the connected account, so you map the fields on a real new hire.
- 03
Add Create Employee
Add Onbee.app with Create Employee and map First Name and Last Name from the form. Both are required, and the action fails without them.
- 04
Add Create Inventory
Add a second Onbee.app step with Create Inventory and give the item a Name. This second action makes the Zap multi-step, so it needs a paid plan.
- 05
Test, then publish
Test both actions and check the new records in Onbee.app. Then click Publish. Responses sent before that moment are not processed.
The 4 Onbee.app actions
Onbee.app gives you 4 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Create Employee
ActionIn Zapier“Creates an employee in Onbee.app”
Adds a person to Onbee.app so their onboarding can begin. Only First Name and Last Name are required; the rest can be filled later.
Create Inventory
ActionIn Zapier“Creates an inventory item in Onbee.app”
Records a new piece of equipment in Onbee.app. The Name is the only required field, which keeps the step short.
Update Employee
ActionIn Zapier“Updates an employee in Onbee.app”
Changes an employee record that already exists, which you point to with its Employee ID. Only that ID is required; the values to change are up to you.
Update Inventory
ActionIn Zapier“Updates an inventory item in Onbee.app”
Edits an equipment item already in Onbee.app, designated by its Inventory ID. That ID is required, and you fill only what needs to change.
When an Onbee.app Zap breaks
Zapier links no help article to Onbee.app, so the cases below are the general traps, applied to this app.
Four mechanisms explain what goes wrong in a Zap that writes to Onbee.app. None of them is a bug: it is how Zapier works, and each has a simple answer. For a Zap that still fails, see the Zapier troubleshooting page.
Past hires are not imported
A Zap only reacts to what happens after it is switched on. Employees hired before that moment do not reach Onbee.app; moving them is a separate job.A loop between two tools
If the trigger app watches a place your Zap also writes to, each new employee or item can start the Zap again and use up tasks fast.A bulk import held back
When the trigger app suddenly returns a huge batch, after a mass import of staff for example, Zapier's flood protection can hold the runs back.No double records from polling
On a polling trigger, Zapier remembers what it has already seen, so the same response does not create the same employee twice.
Need help automating Onbee.app with Zapier?
A person reads every message.
