Resources · Zapier integration

Onpipeline Zapier integrationAutomate Onpipeline with Zapier.

The Onpipeline Zapier integration gives you 9 triggers, 7 actions and 2 searches to connect your sales CRM to the rest of your tools without code. Here is what each one does, what it costs in practice and where it usually breaks.

See the 18 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Onpipeline Zapier integration actually does

A Zap is the automation you build on Zapier: one event that starts it, then one or more steps that run each time that event happens. With Onpipeline, the starting event is a deal, a person, an organization or a calendar event created or changed in the CRM, and the steps can also write people, organizations, deals and leads back into it.

Three results come up most. Won deals leave the CRM: Deal Is Won hands the closed deal to your invoicing or onboarding tool so nobody retypes it. Leads arrive without copy and paste: a web form or an ad tool feeds Add Lead (Leads In), and the person shows up in the Leads In list ready to qualify. Records stay aligned: Updated Person or Updated Organization pushes each change to your mailing tool, and Update Person brings corrections the other way.

All nine triggers are polling triggers. Zapier checks Onpipeline at regular intervals, so on the free plan a new deal can wait up to 15 minutes before the Zap starts. Nothing in the editor turns them into instant ones.

What Zapier does not do for this app: there is no delete action, no trigger on leads, and the searches only work from an ID, so you cannot look up a person by name or email. There is no find-or-create either.

If you are still choosing a platform, see Make vs Zapier and n8n vs Zapier, or the Zapier review.

Vocabulary

Zapier words, in plain English

Seven words come back all over this page. One sentence each.

Trigger
The event in an app that starts the Zap. Once the Zap is on, Zapier waits for that event and starts each time it happens.
Action
What the Zap does once it has started: the step that writes, sends or moves something on your behalf.
Task
The unit Zapier bills: one action that your Zap completes successfully. Your plan counts these and nothing else.
Polling vs instant
A polling trigger is checked by Zapier on a timer; an instant one is reported by the app itself. Every Onpipeline trigger is polling.
Filter
A step that lets the Zap go on only when what arrived meets your condition, and stops it there otherwise.
Search step
A step that looks up a record already in an app, so the steps that follow can reuse what it found.
Connection
Your Onpipeline account linked to Zapier once, then reused by every step of every Zap that touches Onpipeline.
Cost

What it really costs in tasks

Onpipeline is not a premium app, so it runs on the free plan. The trigger never costs a task, and checking Onpipeline for new deals is free however often Zapier looks. Only an action that goes through is counted.

  • Premium appNo, available on the free plan
  • Free plan100 tasks a month, two-step Zaps
  • Trigger checksCost no task
  • Onpipeline triggers9 of 9 polling

The free plan gives you 100 tasks a month, with Zaps of two steps only: one trigger, one action. A filter, a search or a second action makes it a multi-step Zap, which needs a paid plan. A three-action Zap uses three times the tasks of a one-action Zap. Since every trigger here is polling, the plan also sets how fast things move, as in the grid below. On paid plans that interval can also be changed.

Connect

Connect Onpipeline to Zapier in three steps

  1. 01

    Open your Apps page

    In your Zapier account, go to Apps and click + Add connection. You need an Onpipeline account first, with access to the deals and contacts you want the Zap to read or change.

  2. 02

    Pick Onpipeline

    Type Onpipeline in the search box of the dialog that opens, select the app, then click Add connection. A new tab opens on the Onpipeline sign-in page.

  3. 03

    Sign in and grant access

    Log in with your Onpipeline account in that tab and give Zapier access to it. The connection then sits in your list, and every later Zap can reuse it without asking again.

First Zap

Your first Zap: from new contact to new deal

GoalWhen a person is created in Onpipeline, keep only the ones that matter, then open a deal for them.

  1. 01

    Choose the trigger

    Pick Onpipeline as the app that starts the Zap, then New Person as the event, and select the Onpipeline connection you created earlier.

  2. 02

    Set the time zone and test

    Set Time Zone to the one your CRM uses. Then test: Zapier brings back the three most recent people from your account, so you map on a real record.

  3. 03

    Add a filter

    From the plus icon, add Filter. Pick the field to look at, the rule and the value to compare with. A text rule only works on text, so match the type.

  4. 04

    Add the deal

    Choose Onpipeline again and Add Deal. Fill the three required inputs, the deal owner, the pipeline and the deal name, mapping the person's data where it fits.

  5. 05

    Test, then publish

    Run each step once and read what came back. When the deal shows up in the right pipeline, click Publish. With the filter, this is a multi-step Zap and needs a paid plan.

Triggers

Onpipeline triggers

9 events start a Zap when something happens in Onpipeline. Zapier checks for them at the interval your plan allows.

1

Deal Is Won

Polling trigger

In Zapier“Triggers when a deal is updated as won”

Picks up a deal at the point it gets marked as won in Onpipeline and passes it to whatever comes next, usually the tools that take over after the sale.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
a signed deal should create the customer in your invoicing tool or open an onboarding project without anyone asking.
Watch out
the required Time Zone must match the CRM's, or carry the same UTC offset.
2

New Deal

Polling trigger

In Zapier“Triggers when a new deal is created.”

Catches every deal that gets created in Onpipeline, whoever creates it and in whichever pipeline, and hands it to the next step.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
the sales manager wants a chat message or a spreadsheet row for each new opportunity, to follow the pipeline without logging in.
Watch out
add a filter if only one pipeline matters, since the trigger itself takes them all.
3

New Event

Polling trigger

In Zapier“Triggers when a new calendar event is created.”

Starts the Zap when a new event is added to the Onpipeline calendar, a meeting or a call booked with a prospect for instance.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
meetings planned in the CRM should also land in the shared calendar the rest of the team reads.
Watch out
a wrong Time Zone shifts every meeting by the gap between the two zones, which is easy to miss in a test.
4

New Organization

Polling trigger

In Zapier“Triggers when a new organization is created.”

Reacts to each company record created in Onpipeline, so the account exists elsewhere too without being typed twice.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
your accounting or support tool needs the same list of client companies as the CRM, from the start.
Watch out
it only sees organizations created after the Zap is published; the ones you already have stay where they are.
5

New Person

Polling trigger

In Zapier“Triggers when a new contact person is created.”

Fires on each contact person added to Onpipeline, by a salesperson or by another Zap, and passes that person on.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
every new contact should join a mailing list or receive a welcome sequence from your email tool.
Watch out
if another Zap uses Add Person, those people start this one too; check that chain before publishing.
6

Updated Organization

Polling trigger

In Zapier“Triggers when organizations are updated.”

Goes off when an organization already in Onpipeline changes, so the copies of that company in your other tools can follow.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
a company moves or changes its details and your billing tool must not keep the old version.
Watch out
pairing it with Update Organization on the same record makes a loop that eats tasks.
7

Updated Deal

Polling trigger

In Zapier“Triggers when deals are updated.”

Watches existing deals and starts the Zap whenever one of them is changed, whatever the change is.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
a forecast spreadsheet should stay in step with the amounts and stages your team edits in the CRM.
Watch out
for closed deals only, Deal Is Won is the narrower choice and needs no filter.
8

Updated Event

Polling trigger

In Zapier“Triggers when calendar events are updated.”

Follows calendar events that get moved or edited in Onpipeline, so a rescheduled meeting does not live on under its old time elsewhere.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
the copy of a meeting in a shared calendar has to move when the salesperson moves it in the CRM.
Watch out
set the same Time Zone as in New Event, or the two Zaps disagree.
9

Updated Person

Polling trigger

In Zapier“Triggers when persons are updated.”

Notices changes to contact persons already stored in Onpipeline and sends the updated record along.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
a contact's details corrected in the CRM should reach your mailing or support tool too.
Watch out
a Zap that answers with Update Person on that same person starts itself over and over.
Actions

Onpipeline actions

Onpipeline gives you 7 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Add Organization

Action

In Zapier“Add a new Organization”

Creates a company record in Onpipeline from data collected in another tool.

When to use it
a business signs up on your website and the company should exist in the CRM before anyone calls.
Watch out
Organization Name is required, and the action creates a new record each time it runs.
2

Add Person

Action

In Zapier“Add a new Person”

Adds a contact person straight to Onpipeline, outside the leads list.

When to use it
a known customer books a call and should land among your contacts, not among prospects to qualify.
Watch out
first name and family name are both required, so a form that only asks for a full name needs splitting first.
3

Add Deal

Action

In Zapier“Creates a new deal”

Opens a new deal in Onpipeline, with an owner, a pipeline and a name.

When to use it
a quote request on your site should become an opportunity assigned to the right salesperson.
Watch out
Deal Owner, Select Pipeline and Deal Name are all required, so decide who owns these deals before building the Zap.
4

Add Lead (Leads In)

Action

In Zapier“Creates a new Lead in the CRM (Leads IN)”

Drops a new lead into the Leads In list, the CRM's inbox for prospects nobody has qualified yet.

When to use it
contact forms, webinar signups or ad leads should wait there for a salesperson to sort them.
Watch out
like Add Person, it requires a first name and a family name.
5

Update Deal

Action

In Zapier“Updates existing Deals”

Changes a deal that already exists rather than creating another one.

When to use it
a payment confirmed in your billing tool should move or edit the matching deal in the CRM.
Watch out
Deal ID is required; the Zap must carry it from an earlier step, since no search here finds deals.
6

Update Organization

Action

In Zapier“Updates an organization.”

Edits a company record already stored in Onpipeline.

When to use it
details corrected in your accounting tool should reach the CRM without a second round of typing.
Watch out
Organization ID is required; start the Zap from New Organization or Updated Organization so the ID comes with it.
7

Update Person

Action

In Zapier“Updates a person record”

Modifies an existing contact person instead of adding a duplicate.

When to use it
someone updates their profile in your customer portal and the CRM should follow.
Watch out
Person ID is required, so your other tool needs to keep the Onpipeline ID somewhere.
Searches

Onpipeline searches

2 search steps look for data that already exists in Onpipeline, so a later step can use it.

A search step looks up a record that already exists so later steps can use it. In the editor, searches sit at the bottom of the Action event list, under SEARCH. Three settings decide what happens next.

1

Find Organization

Search

In Zapier“Finds an Organization in Onpipeline.”

Fetches one organization from Onpipeline using its ID, which is the only way in.

When to use it
another tool stores the Onpipeline ID and you want the full company record before an update or a message.
Watch out
no lookup by company name, and no find-or-create version; without the ID this step has nothing to work with.
2

Find Person

Search

In Zapier“Finds a Person in Onpipeline”

Retrieves a contact person through their Person ID and hands the record to the following steps.

When to use it
just before Update Person, to check what the CRM holds before overwriting it.
Watch out
the ID is required, so this search cannot tell you whether an email address is already in the CRM.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, an empty search stops the Zap and skips what depended on it. Switched on, the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    This box turns a search into a find-or-create. Onpipeline offers none, so neither of its searches can create the missing record.
  3. If multiple search results are found?
    Keep the first match, which is the default, stop the Zap, or pass every match along at once.
When it breaks

When an Onpipeline Zap breaks

Zapier links no help article to Onpipeline and documents no limit specific to it. The traps below are the ones every Zap shares, and two of them hit this app hard.

Read them before publishing. If a Zap is already misbehaving, the Zapier troubleshooting page is the place to start.

  • No catch-up on the past

    A Zap only reacts to what happens after you switch it on. Deals and people already in Onpipeline are not picked up; moving that backlog is a separate job.

  • Update triggers that loop

    Updated Deal plus Update Deal on the same record, or Updated Person plus Update Person, sets the Zap off again and again and burns through your tasks.

  • Bulk imports get held back

    If a trigger suddenly returns a huge batch, after an import or a migration, Zapier's flood protection can hold it back instead of running everything.

  • No double runs on one item

    Zapier remembers what a polling trigger has already seen, so the same deal or person does not start the Zap twice. Useful, and why a retest may bring nothing new.
Need help

Need help automating Onpipeline with Zapier?

A person reads every message.

FAQ

Onpipeline and Zapier: common questions

01Is the Onpipeline Zapier integration free?
Yes, Onpipeline is not a premium app, so it works on Zapier's free plan. That plan gives you 100 tasks a month and unlimited Zaps, each limited to two steps: one trigger and one action. Adding a filter, a search step or a second action turns it into a multi-step Zap, which requires a paid plan. On the free plan, triggers are also checked every 15 minutes, which matters here because every Onpipeline trigger is a polling one.
02How many tasks does an Onpipeline Zap use?
Only completed actions are counted. The trigger is free, and so is every check Zapier makes on Onpipeline for new deals or people, however often it looks. An action that fails is not billed either. A Zap with one action uses one task per run, a Zap with three actions uses three. So a Zap that adds a lead and then opens a deal costs two tasks each time. A few apps and actions count more than one task when they complete.
03Are Onpipeline triggers real time?
No. All nine are polling triggers: Zapier asks Onpipeline for new items at a fixed interval, which depends on your plan. That interval is 15 minutes on Free, 2 on Professional and 1 on Team and Enterprise. The type comes from the app and cannot be switched in the editor. On paid plans the interval can be changed, and a check can also be run by hand from the editor when you need a result straight away.
04What do you need to connect Onpipeline to Zapier?
An Onpipeline account, plus read or write access on any record you do not own and want the Zap to touch. On Zapier, open the Apps page, click + Add connection, search for Onpipeline and confirm with Add connection. A tab opens where you sign in and grant Zapier access. Then, in each trigger, set the required Time Zone to the one your CRM uses, or to one with the same UTC offset.
05Why are Onpipeline dates shifted in a Zap?
Almost always because of the Time Zone setting. Every Onpipeline trigger requires one, and it must be the zone your CRM uses, or a zone with the same UTC offset. Pick another and meetings from New Event or Updated Event arrive moved by the gap between the two zones. Set it the same way on every trigger of the account, test on one of the three recent items Zapier brings back, and compare with the CRM.
06What if the Onpipeline operation you need does not exist?
Check whether existing steps cover it first. Every update needs the record ID, so start from the trigger that carries it: Updated Person before Update Person, Updated Organization before Update Organization, New Deal or Updated Deal before Update Deal. What the integration offers no way to do is delete a record, start on a new lead, or search by name or email; both searches need an ID, and no setting changes that on Zapier today.
07Zapier, Make or n8n for Onpipeline?
Decide by criteria, not by brand. On Zapier, Onpipeline comes with 9 polling triggers, 7 actions and 2 searches, and works on the free plan for two-step Zaps checked every 15 minutes. If speed matters, the plan sets the interval; if your flows need filters or several actions, a paid plan is required. Then check, operation by operation, whether the other platform offers the trigger or action you rely on, and how it counts what it bills.
Same platform

Other docs you might need on this stack.

Browse all integrations