- Home
- Resources
- Integrations
- Onsight
Onsight Zapier integrationAutomate Onsight with Zapier.
The Onsight Zapier integration gives you 2 triggers, 0 actions and 0 searches. Onsight can start Zaps when leads or contacts appear, but Zapier cannot write anything back into it. Here is how that plays out, what it costs and what to watch.
Verified Trustpilot reviews · AI, automation & growth agency
What the Onsight Zapier integration does
Onsight is built to move your leads into a CRM or another tool without copy-paste. On Zapier it plays one role only: the starting point. When a lead or a contact appears in your Onsight account, Zapier picks it up and hands it to the app of your choice.
Three results you can get from the two triggers. A CRM that fills itself: every new lead from New Leads becomes a record in your sales tool, so nobody has to export a list by hand. A sales alert: the same trigger can post a message to your team channel, so a rep sees the lead without opening Onsight. A clean contact list: New Contact feeds your newsletter or your spreadsheet with each person added to Onsight.
Now what Zapier does not do here. Onsight has no action in Zapier, so no Zap can create, update or tag anything inside Onsight. There is no search either, so a Zap cannot look up an existing Onsight lead. The flow is one-way: out of Onsight, into something else. And both triggers are polling triggers, which means a lead does not travel the second it lands: it waits for Zapier's next check.
If your project needs Onsight to receive data, this integration will not help. If it needs Onsight leads to reach your other tools without a manual export, it fits well. For a broader view of the platform, read our Zapier review. To compare with a self-hosted option, see n8n vs Zapier.
Zapier vocabulary in one minute
Seven Zapier words appear on this page. Here is each one, defined once.
- Zap
- The automation you build on Zapier: one starting event, then one or more steps that run every time that event happens.
- Trigger
- The event that starts the Zap. Once the Zap is on, Zapier waits for it. With Onsight, a new lead or a new contact.
- Action
- What the Zap does after it starts: write, send or create something. Onsight has none, so the action always lives in another app.
- Task
- What Zapier bills: one action completed successfully. Your plan counts tasks, never triggers or checks.
- Polling vs instant
- Polling: Zapier checks on a timer and keeps only new items. An instant trigger is pushed by the app itself instead. Both Onsight triggers poll.
- Filter
- A step that lets the Zap go on only when the data meets your condition, and stops it otherwise.
- Multi-step Zap
- Any Zap beyond one trigger and one action. A filter or a second action makes one, and it then needs a paid plan.
What an Onsight Zap costs
Onsight is not a premium app, so it works on the free plan. The trigger never costs a task: only the action in the receiving app does.
- Free plan100 tasks per month
- Free plan ZapsTwo steps: one trigger, one action
- OnsightNot a premium app
- Onsight triggers2 polling, 0 instant
Zapier checking Onsight for new leads is free, however often it looks. Each lead that reaches your CRM counts as one task, and an action that fails is not billed. The free plan stops at two steps, so one Onsight trigger plus one action fits, but adding a filter to keep only some leads, or a second action, makes the Zap multi-step and paid. Because both triggers are polling triggers, your plan also sets how long a lead waits before Zapier sees it.
Connect Onsight to Zapier
- 01
Open the Apps page
In Zapier, go to the Apps page of your account and click + Add connection. A connection is your Onsight account linked once, then reused by every Zap that starts from Onsight.
- 02
Select Onsight
Search Onsight by name in the dialog that opens, pick it, then click Add connection. Signing in then happens in a new tab, on the Onsight side, with your usual Onsight login.
- 03
Sign in and allow access
Log in with your Onsight account and grant Zapier access. You need your own account, plus read access on any leads or contacts you do not own and want the Zap to see.
Your first Onsight Zap
GoalEach new Onsight lead becomes a contact in your CRM, then your sales team gets a message about it.
- 01
Build: start from Onsight
Create a Zap, choose Onsight as the starting app and New Leads as the event. Select the Onsight connection you just set up.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent leads of your Onsight account, so you map the next steps on a real lead, not a placeholder.
- 03
Add the CRM action
Add your CRM as the next step, pick its create action, and map the lead details Onsight returned into the CRM fields. Check that nothing required is left empty.
- 04
Add the team message
Add a messaging app as a third step. With two actions, the Zap becomes multi-step and needs a paid plan. On the free plan, stop at the CRM step.
- 05
Test, then publish
Test each step once and open your CRM to check the record. When it looks right, click Publish to switch the Zap on. From then on, each new lead follows.
Onsight triggers in Zapier
2 events start a Zap when something happens in Onsight. Zapier checks for them at the interval your plan allows.
New Contact
Polling triggerIn Zapier“Triggers when a new contact is added to your Onsight account”
Starts a Zap each time a contact is added to your Onsight account. The person then travels to whatever app comes next: a mailing list, a spreadsheet, a CRM. Only contacts added after the Zap is published are picked up.
New Leads
Polling triggerIn Zapier“Triggers when a new lead is created (ie. from leadgen)”
Fires when a new lead is created in Onsight, for example one that comes out of your lead generation. This is the trigger to pick when the goal is getting fresh prospects in front of sales quickly. Each lead starts the Zap once.
When an Onsight Zap breaks
Zapier links no help article to Onsight, and no Onsight-specific limit is documented. What goes wrong comes from Zapier's own rules.
Four cases to know before you count on the Zap. For deeper fixes, our Zapier troubleshooting page is the next stop.
Old leads never come through
The Zap only reacts to leads created after you publish it. Everything already in Onsight stays put, and moving that backlog is a separate job.A loop that eats tasks
If a later step writes into the very place Onsight watches, the Zap sets itself off again and again, and every lap uses another task in the receiving app.A big import is held back
When Onsight suddenly returns a huge batch, after a bulk import or a migration, Zapier's flood protection can hold the run back instead of sending everything.The same lead twice? No
On a polling trigger, Zapier keeps track of what it has already seen, so one lead does not start the Zap twice. Duplicates in the CRM usually come from the CRM side.
Need help automating Onsight with Zapier?
A person reads every message.



