ONBORD Zapier integrationAutomate ONBORD with Zapier.
ONBORD Zapier integration: 4 triggers, 0 actions, 0 searches. All four triggers are instant, so ONBORD reports each applicant event to Zapier and your Zap runs right away on any plan, free one included. Zapier listens to ONBORD here; it never writes back into it.
Verified Trustpilot reviews · AI, automation & growth agency
What the ONBORD Zapier integration actually does
ONBORD runs a digital onboarding flow for applicants. Plugged into Zapier, it becomes a source of signals: when an applicant is verified, made live, exported or deleted, ONBORD tells Zapier, and Zapier carries that news into the other tools your team works in. ONBORD is the starting point of the Zap, never the destination.
Three results people usually build. First, a heads-up for the people who review files: Applicant Verified starts a Zap that posts in a team chat once an identity check has completed, so nobody refreshes the onboarding screen waiting for it. Second, a clean record of who went live: Applicant Made Live adds a line to a spreadsheet or a CRM, which gives sales or account managers one list to work from. Third, a tidy cleanup: Applicant Deleted lets you remove or flag that person in the other tools, so a deleted applicant does not linger in a mailing list.
What Zapier does not do for ONBORD matters just as much. There is no action and no search: a Zap cannot create an applicant, change one, or look one up inside ONBORD. If your plan was to push people from a form into ONBORD through Zapier, this integration will not get you there. It only works in one direction, out of ONBORD.
If you are weighing other automation tools for this one-way flow, the Make vs Zapier and n8n vs Zapier pages sit next to this one.
Zapier vocabulary in one minute
Eight words come back on every Zapier screen. Here they are in plain English, once, before the rest of the page uses them.
- Zap
- The automation you build: one trigger, then one or more actions that run each time the trigger event happens.
- Trigger
- The event in an app that starts the Zap. Once the Zap is on, Zapier waits for that event and nothing else.
- Action
- What the Zap does after it starts: the step that writes, sends or moves something in another tool for you.
- Task
- The unit Zapier bills. One task equals one action your Zap completes successfully; your plan counts those.
- Polling vs instant trigger
- A polling trigger is checked on a timer. An instant trigger is reported by the app itself, so it never waits for a check.
- Filter
- A step that lets the Zap continue only when the incoming item meets a condition you set, and stops it otherwise.
- Connection
- Your ONBORD account linked to Zapier once, then reused by every step and every Zap that talks to ONBORD.
- Multi-step Zap
- Any Zap beyond one trigger and one action. A second action or a filter makes it one, and it then needs a paid plan.
What it really costs you
Short version: listening to ONBORD is free, and you only pay in tasks for what the Zap does afterwards.
- ONBORD trigger firing0 tasks
- Each successful action1 task
- Free plan100 tasks a month, 2 steps per Zap
- Premium appNo, works on the free plan
A trigger never costs a task, so an applicant being verified costs nothing by itself. Each action that succeeds counts once; a Zap with three actions uses three times what a one-action Zap uses, and an action that fails is not counted. The free plan gives 100 tasks a month and unlimited Zaps, but only two steps per Zap: one trigger and one action. Add a filter or a second action and the Zap becomes multi-step, which needs a paid plan. ONBORD is not a premium app, so it works on the free plan. The polling grid below does not apply here, because every ONBORD trigger is instant.
Connect your ONBORD account in 3 steps
- 01
Open the Apps page
In your Zapier account, go to Apps and click + Add connection. You need an ONBORD account first, plus access to the applicants you want the Zap to follow if they belong to someone else.
- 02
Find ONBORD
Type ONBORD in the search box of the dialog, pick it from the list, then click Add connection. Zapier keeps this connection and reuses it in every Zap that starts from ONBORD.
- 03
Sign in and grant access
A tab opens on ONBORD. Sign in with the account whose applicants you want to watch, then grant Zapier access to it. Back in Zapier, the connection appears on the Apps page, ready for your first Zap.
Your first ONBORD Zap, step by step
GoalEach verified applicant lands in a shared spreadsheet, then the review team gets a chat message.
- 01
Build: start from ONBORD
Create a Zap, pick ONBORD as the app that starts it, then Applicant Verified as the event. Select the ONBORD connection you added earlier.
- 02
Test the trigger
Run the trigger test. Zapier brings back the three most recent items of the connected account, so pick a real applicant to map the next steps on.
- 03
Add the spreadsheet action
Add a Google Sheets action and map the applicant details from the trigger into the columns of your sheet. Test the step and read what came back before going on.
- 04
Add the chat message
Add a Slack action that posts in the review channel. This second action makes the Zap multi-step, so it needs a paid plan. Test it once.
- 05
Publish
Publish the Zap to switch it on. From then on each verified applicant runs it right away, and the Zap uses two tasks per applicant.
The 4 ONBORD triggers
4 events start a Zap when something happens in ONBORD, and 4 of them are instant: the app calls Zapier straight away, whatever your plan.
Applicant Deleted
Instant triggerIn Zapier“Triggers when an applicant is deleted.”
This one starts your Zap when an applicant is removed from ONBORD. It is the event to use when you want the other tools to forget that person too, instead of keeping a stale row or contact that nobody will ever clean up by hand.
Applicant Exported
Instant triggerIn Zapier“Triggers when an applicant is exported.”
When an applicant is exported from ONBORD, Zapier receives the event and your Zap begins. Think of it as a hand-off signal: the file leaves ONBORD, and the next system hears about it without anyone copying details across.
Applicant Made Live
Instant triggerIn Zapier“Triggers when an applicant is made live.”
Your Zap kicks off when an applicant is made live in ONBORD. Of the four, it is the natural start for anything you do once an applicant is live, such as welcoming or counting them.
Applicant Verified
Instant triggerIn Zapier“Triggers when identity verification of an applicant has completed.”
ONBORD sends this event once the identity verification of an applicant has completed. It is the checkpoint compliance and onboarding teams tend to wait on, and the trigger turns it into a message or a record instead of a screen someone has to keep checking.
When an ONBORD Zap breaks
Zapier publishes no help article and no specific limit for ONBORD. What can go wrong comes from the way every Zap works.
Four cases cover almost every ONBORD Zap that stops behaving. If yours does not match any of them, the Zapier troubleshooting page is the next stop.
Old applicants never show up
A Zap only reacts to events that happen after it is switched on. Applicants verified or made live earlier are not picked up; moving that backlog is a separate job.The Zap keeps restarting itself
A Zap that writes into the place its own trigger watches sets itself off again and again. With ONBORD triggers this needs another tool feeding back into ONBORD, and it burns tasks fast.A big batch is held back
When a trigger suddenly sends a huge batch, after a bulk import or a migration, Zapier's flood protection can hold those runs back instead of firing them all.The second step will not save
On the free plan a Zap stops at one trigger and one action. A filter or a second action turns it into a multi-step Zap, which needs a paid plan.
Need help automating ONBORD with Zapier?
A person reads every message.
