Resources · Zapier integration

LeadOrigin Zapier integrationAutomate LeadOrigin with Zapier.

The LeadOrigin Zapier integration gives you 1 trigger, 5 actions and 2 searches. A polling event for new leads, actions that create leads, contacts and deals or update and annotate a lead, and two lookups. Here is what each does and costs.

Beta app Zapier still marks this integration as beta.

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the LeadOrigin Zapier integration actually does

LeadOrigin is a CRM, a tool where sales and marketing teams keep their leads, contacts and deals, and follow each one up. Connecting it to Zapier moves that data in and out on its own: a new lead can start work elsewhere, and what happens in other tools can create or update records in LeadOrigin.

Three results come out of it. First, a deal opened for each new lead: New Lead starts the Zap, and Create Deal puts the deal in the stage you choose, which also sets its pipeline. Second, a contact or lead created without duplicates: Create Contact returns the existing contact when the email or phone already matches, and Find or Create Lead does the same job for leads. Third, a lead timeline that fills itself: Find Lead spots the right lead, then Add Note to Lead writes a note that reads like one typed in the app.

Now the limits. The only trigger watches new leads: nothing starts a Zap when a deal moves or a contact changes. No action deletes anything, and there is no update for contacts or deals, only for leads. The trigger is a polling one, so on the free plan a new lead can wait up to 15 minutes before the Zap notices it. And LeadOrigin is still flagged as a beta app on Zapier.

If you are still choosing a tool, see our n8n vs Zapier and Make vs Zapier comparisons.

Vocabulary

Zapier vocabulary in one minute

Eight words come back on every line of this page. Here they are in plain English.

Zap
The automation you build on Zapier: 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 switched on, Zapier sits and waits for it.
Action
What the Zap does after it starts: the step that writes, sends or moves something on your behalf.
Task
The unit Zapier bills. One action that completes successfully is one task, and your plan is a count of those.
Polling vs instant
A polling trigger is checked by Zapier on a timer. An instant trigger is reported by the app itself, the moment the event happens.
Filter
A step that lets the Zap continue only when what arrived meets your condition, and stops it there otherwise.
Search step
A step that looks up something already in an app, so the steps after it can use what it found.
Multi-step Zap
Any Zap beyond one trigger and one action. A second action, a filter or a search makes one, and it then needs a paid plan.
Cost

What a LeadOrigin Zap really costs

The trigger is free, and so is Zapier checking for new leads, however often it looks. Only actions that go through are billed, one task each.

  • Trigger and checksCost nothing
  • Each successful action1 task
  • Free plan100 tasks a month, 2-step Zaps
  • Search or filterMakes the Zap multi-step (paid)

LeadOrigin is not a premium app, so it runs on the free plan: 100 tasks a month and unlimited Zaps, but two steps per Zap at most (one trigger, one action). Add a search, a filter or a second action and the Zap turns multi-step, which needs a paid plan. That matters here, because many useful LeadOrigin Zaps start with Find Lead. An action that fails is not counted. New Lead is a polling trigger, so how fast it reacts follows the grid below.

Connect

Connect your LeadOrigin account in 3 steps

  1. 01

    Open your connections

    In Zapier, go to the Apps page of your account and click + Add connection. A connection is your LeadOrigin account linked once, then reused by every step that touches LeadOrigin.

  2. 02

    Find LeadOrigin

    Type LeadOrigin in the search box of the dialog, pick it from the results, then click Add connection. A new browser tab then opens on the LeadOrigin side.

  3. 03

    Sign in and allow access

    Log in to LeadOrigin in that tab and grant Zapier access to the account. You need a LeadOrigin account, plus read or write rights on any lead, contact or deal you do not own.

First Zap

Your first Zap: a deal and a note for each qualifying lead

GoalEach new LeadOrigin lead that passes your condition gets a deal in the right stage, plus a note on its timeline saying so.

  1. 01

    Create the Zap

    Start a new Zap, choose LeadOrigin as the app that starts it and New Lead as the event. Test it: Zapier brings back the three most recent leads, so you map on a real one.

  2. 02

    Add the filter

    Click the plus icon, choose Filter, then fill the three boxes: the field to look at, the rule and the value. Use a text rule on text and a number rule on numbers.

  3. 03

    Open the deal

    Add LeadOrigin again and pick Create Deal. Give it a name built from the lead fields, then choose the Stage, which also places the deal in its pipeline.

  4. 04

    Leave a trace on the lead

    Add Add Note to Lead. In Lead, map the id from the trigger step, then write a short note. With four steps, this Zap needs a paid plan.

  5. 05

    Test, then publish

    Run each step once, then check the deal and the note in LeadOrigin. When both look right, click Publish to switch the Zap on.

Triggers

LeadOrigin trigger

1 event starts a Zap when something happens in LeadOrigin. Zapier checks for them at the interval your plan allows.

1

New Lead

Polling trigger

In Zapier“Triggers when a new lead is created in LeadOrigin.”

Starts your Zap each time a lead is created in LeadOrigin, and passes its details, id included, to the steps that follow. That id is what Update Lead and Add Note to Lead need later 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
when each fresh lead should open a deal, land in a shared sheet or alert someone outside LeadOrigin.
Watch out
a Zap started by this trigger that also runs Create Lead creates the very leads it watches, and loops.
Actions

LeadOrigin actions

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

1

Add Note to Lead

Action

In Zapier“Adds a note to a lead's timeline in LeadOrigin.”

Writes a note on a lead's timeline, where it reads exactly like a note typed in the app. It needs the lead and the note text.

When to use it
to keep a trace of what happened in other tools (a form answer, a reply) right on the lead.
Watch out
the lead must come from a Find Lead or New Lead step, or be picked by hand.
2

Create Contact

Action

In Zapier“Creates a contact in LeadOrigin (or returns the existing one if the email or phone already matches).”

Puts a contact into LeadOrigin, or hands back the one already there when its email or phone matches. Either way, the next step gets a usable contact.

When to use it
when the same person may come through several times and you want one record, not five.
Watch out
the match runs on email or phone only, so a person who changes both shows up as new.
3

Create Deal

Action

In Zapier“Creates a new deal in LeadOrigin.”

Opens a new deal in LeadOrigin. It asks for a deal name and a stage, and the stage you pick also decides which pipeline the deal sits in.

When to use it
right after New Lead, so each lead gets a deal without anyone opening the app.
Watch out
pick the stage with care; a wrong one drops the deal into the wrong pipeline.
4

Create Lead

Action

In Zapier“Creates a new lead in LeadOrigin.”

Adds a fresh lead to LeadOrigin from data an earlier step carries. Only the first name is mandatory, so even a thin record goes through.

When to use it
when a sign-up or an inbound request elsewhere should become a lead your team follows up in LeadOrigin.
Watch out
this action does not check for an existing lead; use Find or Create Lead if duplicates worry you.
5

Update Lead

Action

In Zapier“Updates an existing lead in LeadOrigin.”

Changes an existing lead in LeadOrigin. The only required field is the lead itself, then you fill just what should change.

When to use it
when a later event, in another tool, means the lead record should carry new details.
Watch out
picked by hand, the lead stays fixed, so every run edits that same record; map an id from Find Lead instead.
Searches

LeadOrigin searches

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

A search step looks up a record already in LeadOrigin and hands it to the next steps. Three settings decide what happens when the result is not the one you expected.

1

Find Contact

SearchFind or create

In Zapier“Finds a contact by email or phone number.”

Looks for a LeadOrigin contact by email or phone number and hands it to the following steps.

When to use it
before any step that needs a contact already in the CRM, so you work on it instead of guessing.
Watch out
the editor also lists Find or Create Contact. It is this same search with the create box ticked, not a separate operation, and it adds the contact when none matches.
2

Find Lead

SearchFind or create

In Zapier“Finds a lead by email or phone number.”

Tracks down a lead by email or phone number, and returns the id that Update Lead and Add Note to Lead expect.

When to use it
whenever an outside event concerns a lead and you need its record first.
Watch out
Find or Create Lead is this same search with creation switched on; it builds the lead when none is found, rather than stopping the Zap.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap there. Switched on, the Zap goes on empty-handed.
  2. Create X if it doesn't exist yet?
    Ticking it turns the search into a find-or-create: it drops the setting above and asks for the fields to 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 on at once.
When it breaks

When a LeadOrigin Zap breaks

Zapier attaches no help article to LeadOrigin, so the cases below are the general traps, the ones that hit Zaps built on this app most often.

None of them shows during the test. They appear once the Zap runs on real leads. If a Zap still misbehaves, see our Zapier troubleshooting guide.

  • Old leads are never picked up

    A Zap only reacts to what happens after you switch it on. Leads created before publishing stay out; moving that backlog is a separate job.
  • New Lead feeding Create Lead

    A Zap that writes leads into LeadOrigin while New Lead watches for them sets itself off again and again, and drains the task count fast.
  • A bulk import gets held back

    After a mass import or a migration, New Lead can suddenly return a huge batch, and Zapier's flood protection may hold the Zap back.
  • The same lead never fires twice

    Zapier remembers the leads it has already seen on a polling trigger. Editing a lead does not send it through New Lead again.
Need help

Need help automating LeadOrigin with Zapier?

A person reads every message.

FAQ

LeadOrigin and Zapier: common questions

01Is the LeadOrigin Zapier integration free?
Yes, for two-step Zaps. LeadOrigin is not a premium app, so the free plan takes it, with 100 tasks a month and unlimited Zaps. The catch is the shape of the Zap: the free plan builds one trigger and one action, nothing more. Many useful LeadOrigin Zaps start with Find Lead or Find Contact, and a search makes the Zap multi-step, which needs a paid plan. No price is quoted here, because plan pricing changes too often to stay accurate.
02How many tasks does a LeadOrigin Zap use?
One task for each action that completes successfully. The New Lead trigger never costs a task, and neither do Zapier's checks for new leads, however often they run. A Zap that opens a deal for each new lead uses one task per lead. A Zap with three actions uses three per run, since each successful action counts on its own. An action that fails is not billed, so a broken run does not eat your allowance.
03Does LeadOrigin send new leads to Zapier in real time?
No. New Lead is a polling trigger: Zapier asks LeadOrigin for new leads at a fixed interval, and that interval depends on your plan. On the free plan it is every 15 minutes, on Professional every 2 minutes, on Team and Enterprise every minute. On paid plans you can also run a check by hand from the editor. The type is set by the app itself and cannot be changed in Zapier.
04What do you need to connect LeadOrigin to Zapier?
A LeadOrigin account, plus read or write rights on any lead, contact or deal you do not own but want the Zap to touch. The connection is made from the Apps page of your Zapier account: add a connection, search LeadOrigin, sign in to it in the tab that opens, then grant Zapier access. Every LeadOrigin step then reuses that same connection, so you set it up once per account.
05Will Create Contact make duplicates in LeadOrigin?
Not when the email or phone already matches. In that case Create Contact returns the existing contact instead of making a new one, and the next steps work on that record. The match only looks at email and phone, though, so a person who comes back with different details for both will be created again. Create Lead has no such check at all; for leads, use Find or Create Lead, which looks first and only creates when nothing matches.
06What if the LeadOrigin operation you need is not there?
Then Zapier cannot do it for this app today. The list covers one trigger on new leads, five actions (create a lead, a contact or a deal, update a lead, add a note to a lead) and two searches, on contacts and leads. There is no trigger on deals or contacts, no delete, and no update for contacts or deals. The editor only shows what LeadOrigin has published, and nothing can be added from your side.
07Zapier, Make or n8n for LeadOrigin?
It depends on your criteria, not on a ranking. On Zapier, LeadOrigin brings one polling trigger, five actions and two searches, and its useful Zaps tend to be multi-step, so a paid plan comes quickly. The deciding points sit elsewhere: how many runs you expect each month, how much branching logic you need, who will maintain the flows, and whether self-hosting matters to you. Weigh those against your own setup before choosing.