LeadExec Zapier integrationAutomate LeadExec with Zapier.
The LeadExec Zapier integration has 1 trigger, 1 action and 0 searches. New Lead tells Zapier the instant a lead reaches a campaign, and Create Lead pushes leads from your other tools into LeadExec, so distribution starts without copy and paste.
Verified Trustpilot reviews · AI, automation & growth agency
What the LeadExec Zapier integration is for
LeadExec centralizes lead distribution: leads come in from several sources and are routed from one place. With Zapier, you build a Zap (an automation that waits for one event, then runs steps in other apps) to feed LeadExec from your forms and to tell other tools when a lead arrives.
Two operations, three common results. Every source feeding one hub: a form or landing page tool sends its entries to Create Lead, assigned to the right campaign and lead source. Instant alerts: New Lead pings your team chat the moment a campaign receives a lead, with no timer in between. A clean log: the same trigger writes each lead into a spreadsheet for reporting outside LeadExec.
The trigger is instant: LeadExec tells Zapier the moment a lead arrives, so even the free plan reacts at once.
Know what is not there. The Zapier integration exposes only these two operations: no search to find an existing lead, no update, no delete. A Zap can receive a lead or create one, and that is all it can do here. Everything else in LeadExec stays outside your Zaps, so plan those parts of the process by hand or in another tool. If your workflow needs more, the n8n vs Zapier and Make vs Zapier comparisons help you check other tools.
Zapier words in one minute
Seven terms come back on this page. Here they are in plain words.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run every time that trigger event happens.
- Trigger
- The event in an app that starts the Zap. Once the Zap is on, Zapier simply waits for that event.
- 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 task is one action your Zap completed successfully, and your plan counts those.
- Instant vs polling
- An instant trigger is reported by the app the moment it happens. A polling trigger is checked by Zapier on a timer.
- Filter
- A step that lets the Zap continue only when what arrived meets your condition, and stops it quietly otherwise.
- Multi-step Zap
- Any Zap beyond one trigger and one action. A second action or a filter makes one, and it then needs a paid plan.
What a LeadExec Zap really costs
Zapier bills tasks, and only a successful action produces one. LeadExec is not a premium app, so it works from the free plan.
- Trigger0 tasks, every time
- Each successful action1 task
- Free plan100 tasks a month, two-step Zaps only
- LeadExec premium?No, available on the free plan
New Lead never costs a task, however many leads arrive. Each lead Create Lead writes successfully costs one; a failed attempt is not billed. The free plan gives you 100 tasks a month and Zaps of two steps, one trigger and one action. A filter or a second action makes the Zap multi-step, which needs a paid plan. The interval grid below concerns polling triggers; New Lead is instant, so it does not apply to it, but it can apply to the trigger of another app that feeds Create Lead.
Connect LeadExec to Zapier in 3 steps
- 01
Open your connections
In Zapier, go to the Apps page of your account and click + Add connection. A connection is your LeadExec account linked once, then reused by every Zap that touches it. You need a LeadExec account first.
- 02
Pick LeadExec
Type LeadExec in the dialog's search box, select it, then click Add connection. A new browser tab opens on the LeadExec side, which is where the actual sign-in happens.
- 03
Sign in and grant access
Log in to LeadExec in that tab and allow Zapier to reach the account. If the Zap will use campaigns or lead sources you do not manage yourself, check that your account has access to them first.
Your first LeadExec Zap
GoalAlert your team the moment a campaign receives a lead, but only for leads that meet your condition.
- 01
Set the trigger
Create a Zap, choose LeadExec as the app and New Lead as the event, then your connection. Pick the Lead Source and the Campaign to watch; both are required.
- 02
Test on real leads
Run the trigger test. Zapier brings back the three most recent leads of that campaign, so you set up the next steps on a real lead instead of placeholder data.
- 03
Add the filter
Click the plus icon, pick Filter, then fill the three boxes: the field to look at, the rule, and the value to compare with. Use a text rule on text, a number rule on numbers.
- 04
Add the message
Add your team chat as the action and map the lead's details into the message. The filter makes this a multi-step Zap, so it needs a paid plan.
- 05
Test and publish
Test each step and read what came back, then publish to switch the Zap on. Leads received before that moment are not picked up.
LeadExec triggers on Zapier
1 event starts a Zap when something happens in LeadExec, and one of them is instant: the app calls Zapier straight away, whatever your plan.
New Lead
Instant triggerIn Zapier“Triggers when a new lead has been received.”
Starts your Zap each time LeadExec receives a lead for the campaign and lead source you chose. It is the only event LeadExec sends to Zapier, so every outbound workflow begins here.
LeadExec actions on Zapier
LeadExec gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.
Create Lead
ActionIn Zapier“Create a new lead inside of LeadExec.”
Adds a new lead to LeadExec from any other app and assigns it to the campaign you name, so distribution starts as soon as the lead exists.
When a LeadExec Zap breaks
Zapier links no help article to LeadExec and documents no limit of its own. What breaks here is what breaks on any Zap, plus one loop this pair of operations makes easy.
Read these four cases before you publish. If a Zap already misbehaves, the Zapier troubleshooting guide takes you through the checks in order.
Old leads are never replayed
A Zap only reacts to what happens after it is switched on. Leads LeadExec received before that stay where they are; moving that backlog is a separate job.The campaign loop
A Zap that starts on New Lead and ends with Create Lead on the same campaign and source creates a lead that starts it again, burning tasks until you stop it.Bulk imports get held back
Push a large batch of leads at once and the trigger suddenly reports a huge pile. Zapier's flood protection can hold those runs back instead of firing them all.No double leads from a polling source
When the app feeding Create Lead uses a polling trigger, Zapier remembers what it has already seen, so the same entry does not create two leads in LeadExec.
Need help automating LeadExec with Zapier?
A person reads every message.
