Resources · Zapier integration

Leadinfo Zapier integrationAutomate Leadinfo with Zapier.

The Leadinfo Zapier integration gives you 5 triggers and no action or search. Leadinfo pushes data out, it does not take any in: shared companies, shared contacts, Lead Bot submissions and matched rules leave for your CRM or team chat the moment they happen.

See the 5 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Leadinfo Zapier integration does for you

Leadinfo identifies the companies behind your B2B website traffic and shows them in an Inbox, much like email. Zapier carries what Leadinfo finds to your other tools, without code. The flow runs one way only: from Leadinfo outward, through five instant triggers.

Three results cover most setups. First, a hand-picked company sent onward: someone clicks share in the Inbox, Share fires, and the company goes to your CRM or to a channel of your team chat. Second, rules that work while you sleep: Trigger fires whenever one of the triggers you configured inside Leadinfo matches a visitor, and Trigger Contact does the same for contacts sent through such a rule. Third, Lead Bot submissions that reach a person: Lead Bot fires when one of your Lead Bots is successfully submitted, so the submission can be routed to whoever follows up.

All five triggers are instant. Leadinfo calls Zapier itself, so the free plan's polling delay never slows you down.

What Zapier does not do with Leadinfo: it cannot write anything into Leadinfo, since there are no actions, and it cannot look anything up there, since there are no searches. Every Zap therefore starts in Leadinfo and ends in another app.

We also cover the Leadinfo Make integration, and the two platforms meet in our Make vs Zapier comparison.

Vocabulary

Zapier terms, quickly

Six words carry the rest of this page.

Zap
The automation you set up in Zapier: one trigger, then one or more actions that run each time the trigger event occurs.
Trigger
The event in an app that starts the Zap. With the Zap switched on, Zapier waits for that event to happen.
Action
What the Zap does after starting: the step that writes, sends or moves something in another app for you.
Task
The unit Zapier charges: one action that your Zap completes successfully. Plans are sized in tasks.
Polling vs instant
Polling triggers are checked on a timer. Instant triggers are reported by the app itself as soon as the event happens.
Filter
A step that lets the Zap go on only when what arrived meets a condition you set, and stops it otherwise.
Cost

What it costs in tasks

Leadinfo is not a premium app, so the integration works from the free Zapier plan.

  • Trigger cost0 tasks
  • Free plan100 tasks per month
  • Free plan Zap size2 steps
  • Premium appNo

None of the five Leadinfo triggers costs a task, and listening for them is free too. What you pay for is the action in the other app: each one that succeeds counts as one task, and a failed one does not count. On the free plan, a Zap is limited to two steps, one trigger and one action, which is exactly a Leadinfo trigger plus one destination. Add a filter, for example to keep only some companies, or a second destination, and the Zap becomes multi-step and needs a paid plan. The interval grid below applies only to polling triggers, and all Leadinfo triggers are instant.

Connect

Connect Leadinfo to Zapier

  1. 01

    Go to Apps

    In Zapier, open Apps and click + Add connection. A connection is your Leadinfo account linked to Zapier one time, then reused by every Zap that starts from Leadinfo.

  2. 02

    Select Leadinfo

    Search for Leadinfo in the dialog, pick it and click Add connection. A new tab opens where Leadinfo asks you to sign in with your own account, not a shared one.

  3. 03

    Sign in and allow

    Log in to Leadinfo and grant Zapier access. To do this you need a Leadinfo account, plus access to anything you do not own yourself and want the Zap to read from.

First Zap

Your first Leadinfo Zap

GoalCompanies you share from the Leadinfo Inbox become records in your CRM.

  1. 01

    Create the Zap

    Click Create in Zapier, choose Leadinfo as the trigger app and Share as the event, then select your Leadinfo connection.

  2. 02

    Share a company, then test

    Share one company from the Leadinfo Inbox, then run the test. Zapier brings back the three most recent items, so you map the next step on a real company.

  3. 03

    Add a filter (optional)

    From the plus icon, add a Filter and set the field, the rule and the value. Remember that a filter makes the Zap multi-step, which needs a paid plan.

  4. 04

    Add your CRM

    Add your CRM app and its create-record action. Map the company data from Leadinfo into the matching fields, then test the step and read what comes back.

  5. 05

    Publish

    Click Publish. From now on, each company you share goes to the CRM straight away. Companies shared before publishing are not sent.

Triggers

Leadinfo triggers

5 events start a Zap when something happens in Leadinfo, and 5 of them are instant: the app calls Zapier straight away, whatever your plan.

1

Lead Bot

Instant trigger

In Zapier“Triggers when a Lead Bot is successfully submitted.”

Starts the Zap when one of your Leadinfo Lead Bots is successfully submitted. The submission goes straight to whoever must follow up, without anyone watching the Inbox.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a demo request comes in through a Lead Bot after hours and should be waiting in the CRM for whoever follows up.
Watch out
you must choose both the Leadbot and the Component, so one Zap covers one bot component only.
2

Share

Instant trigger

In Zapier“Triggers when a company is manually shared in the Inbox”

Fires when someone on your team manually shares a company from the Leadinfo Inbox. It turns a human judgment call, this visitor looks promising, into an automatic hand-off to another tool.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
someone spots a target account in the Inbox and wants it posted in your team chat.
Watch out
nothing fires unless a person clicks share, so it is only as regular as your team's habit.
3

Sharing a Contact

Instant trigger

In Zapier“Triggers when a Contact is shared with Zapier”

The person-level counterpart of Share: it fires when a contact is shared with Zapier from Leadinfo, so a named individual, rather than a whole company, reaches your other apps.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
you pick a decision maker at a visiting company and want that person added to a mailing list.
Watch out
it covers manual contact sharing; contacts sent by a rule come through Trigger Contact instead.
4

Trigger

Instant trigger

In Zapier“Triggers when a configured trigger inside Leadinfo is matched”

Reacts when one of the rules you set up inside Leadinfo, which Leadinfo itself calls triggers, matches a visitor. Your own criteria decide what reaches Zapier, without anyone clicking anything.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
every company that matches your ideal customer rule in Leadinfo should open a deal automatically.
Watch out
the rule lives in Leadinfo, not in Zapier, so a broad rule can flood the destination with runs and tasks.
5

Trigger Contact

Instant trigger

In Zapier“Triggers when a Contact is shared with Zapier via a Trigger”

Fires when a contact is sent to Zapier through one of your Leadinfo rules. It is the automatic version of Sharing a Contact, built for teams that want people, not just companies, pushed out by criteria.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
contacts from companies that match a target rule should go into an outreach sequence without manual review.
Watch out
it depends on a Leadinfo rule configured to share contacts; without one, it never fires.
When it breaks

When a Leadinfo Zap breaks

Zapier ties no help article to Leadinfo and lists no rate limit for it. The failures you will run into are Zapier's general ones.

  • Past visitors never come through

    A Zap only reacts to what happens after you publish it. Companies and contacts shared before that stay in Leadinfo; moving them out is a separate job.

  • A broad rule floods the Zap

    If a Leadinfo rule suddenly matches a huge batch of visitors, Zapier's flood protection can hold those runs back instead of firing them all at once.

  • Empty Lead Bot settings

    The Lead Bot trigger needs a Leadbot and a Component to watch. Without a Lead Bot in the connected account, that trigger cannot be set up at all.
Need help

Need help automating Leadinfo with Zapier?

A person reads every message.

FAQ

Leadinfo Zapier integration: frequent questions

01Is the Leadinfo Zapier integration free?
Yes, on the Zapier side. Leadinfo is not a premium app, so it works with the free plan, which offers 100 tasks a month and unlimited Zaps. Each free Zap is limited to two steps: one trigger and one action. A Leadinfo trigger with one destination fits that exactly. Add a filter or a second destination and the Zap becomes multi-step, which needs a paid plan. Your Leadinfo subscription itself is a separate matter.
02How many tasks does a Leadinfo Zap use?
The Leadinfo trigger itself costs nothing. Only the actions in the destination apps count, one task each time one succeeds. A Zap that sends each shared company to your CRM uses one task per company. A Zap that also posts in your team chat uses two. Failed actions are not counted. With the Trigger event, a broad rule can match many visitors, so estimate volume before you pick your plan.
03Are Leadinfo triggers real time?
Yes. All five Leadinfo triggers are instant: Leadinfo tells Zapier the moment the event happens, and the Zap starts right away whatever your plan. The polling grid, where the free plan checks every 15 minutes, does not apply to any of them. In the Zapier editor, a Zap built on an instant trigger shows a lightning bolt, which is an easy way to confirm it. No setting needs to be changed to get that speed.
04What does it take to connect Leadinfo to Zapier?
A Leadinfo account you can sign in to, plus access to anything you do not own and want the Zap to read. You start from the Apps page in Zapier with + Add connection, pick Leadinfo, sign in in the tab that opens and allow access. For the Lead Bot trigger, the account also needs at least one Lead Bot with its component, since both must be picked in the trigger.
05Why can't a Zap send data into Leadinfo?
Because the integration has no action. All five operations are triggers, so Leadinfo can only start Zaps, never receive data from them. You cannot create a company, update a contact or add a note in Leadinfo through Zapier. Plan each Zap so Leadinfo is the source and another app, such as a CRM or a chat tool, is the destination. Anything that must change inside Leadinfo stays a manual task.
06What if the Leadinfo operation you want does not exist?
With five triggers and nothing else, anything that writes to Leadinfo or searches it is out of reach on Zapier today, and no setting changes that. Check first whether a rule inside Leadinfo combined with the Trigger event covers the need, since it lets you decide what gets sent. Otherwise, look at the Make integration or another platform and compare what each connector actually offers. Checking the integration page from time to time shows any change.
07Zapier, Make or n8n for Leadinfo?
It comes down to criteria, not a ranking. Zapier gives five instant Leadinfo triggers ready to use, which covers pushing Leadinfo data to one or two tools. Make also has a Leadinfo integration, worth comparing operation by operation. For n8n, check whether a native connector exists before choosing. Volume, budget, who maintains the flows and how complex the logic is should drive the decision. Neither answer is wrong in general.
Same platform

Other docs you might need on this stack.

Browse all integrations