LeadSource Zapier integrationAutomate LeadSource with Zapier.
The LeadSource Zapier integration gives you 1 trigger and 1 action. The trigger is instant, so a lead bought through one of your campaigns reaches your CRM the moment it arrives. The action works the other way and submits leads to be matched to a campaign.
Verified Trustpilot reviews · AI, automation & growth agency
What the LeadSource Zapier integration actually does
On LeadSource, you set up campaigns to buy leads. Zapier sits at both ends of that flow: when one of your campaigns receives a lead, Zapier hears about it at once and passes it on; and when you hold a lead yourself, Zapier can submit it to LeadSource to be matched to an available campaign.
Bought leads in your CRM before they go cold. A campaign receives a lead, Lead Received fires, and the next step creates the contact in your CRM. Your team can call while the request is still fresh, instead of finding it later in LeadSource.
An alert for whoever is on duty. The same trigger can post each new lead to a team channel, so nobody has to keep LeadSource open all day.
Leads you collect, matched for you. Submit Lead sends a lead from a form or a sheet to LeadSource, which matches it to an available campaign. It needs a phone number, a zip code and a service type.
What Zapier does not do here. One trigger, one action, nothing else: a Zap cannot create or edit a campaign, update a lead or look one up. Leads received before the Zap was switched on are not picked up.
Adding a filter or a search to a Zap makes it multi-step, and a multi-step Zap needs a paid Zapier plan. Comparing platforms? If you are still choosing a tool, see our Make vs Zapier comparison and our Zapier review.
Zapier vocabulary in one minute
Seven words you will see in the editor. Each is explained here once, then used as is.
- 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. With LeadSource, it is a lead arriving in one of your campaigns.
- Action
- What the Zap does once started: the step that writes, sends or moves something for you, such as submitting a lead.
- Task
- The unit Zapier bills: one action your Zap completes successfully. Your plan counts tasks, not leads.
- Polling vs instant
- A polling trigger is checked on a timer; an instant one is reported by the app as it happens. LeadSource's trigger is instant.
- Filter
- A step that lets the Zap carry on only when what arrived meets the condition you set, and stops it otherwise.
- Connection
- Your LeadSource account linked to Zapier once, then reused by every LeadSource step in every Zap.
What a LeadSource Zap really costs
LeadSource is not a premium app, so it works from the free plan. Zapier bills successful actions, not received leads.
- Free plan100 tasks a month, unlimited Zaps, two-step Zaps only
- Premium appNo, LeadSource works on the free plan
- Trigger typeInstant, the interval grid does not apply
The trigger never costs a task. Each action that succeeds counts once: sending a received lead to a CRM costs one task, to a CRM and a channel two. Submit Lead costs one task per lead it submits. An action that fails, for example because a required field is empty, is not counted. On the free plan, Zaps stop at 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 never applies to the instant trigger.
Connect LeadSource to Zapier in three steps
- 01
Add a connection
Open the Apps page of your Zapier account and click + Add connection. Search for LeadSource in the dialog and pick it. You need a LeadSource account, with access to the campaigns whose leads the Zap should use.
- 02
Sign in to LeadSource
Click Add connection. A tab opens on LeadSource: sign in with the account that runs your campaigns. The Zap only sees the campaigns and leads this account can see.
- 03
Grant access
Allow Zapier to access the account. The connection appears on your Apps page, and both the trigger and the action reuse it. Link it once, and every LeadSource step you add later picks it from a list.
Your first LeadSource Zap, step by step
GoalEvery lead your LeadSource campaigns receive becomes a contact in your CRM, ready for a call.
- 01
Create the Zap on Lead Received
Start a new Zap, choose LeadSource and the Lead Received event, then your connection. The bolt in the editor marks an instant trigger.
- 02
Test with a real lead
Run the test: Zapier brings back the three most recent leads your campaigns received. Pick a real one so the mapping uses real data.
- 03
Add a filter
Click the plus icon and add Filter. Set the field, the rule and the value, so only the leads your sales team handles go through. The Zap becomes multi-step and needs a paid plan.
- 04
Add the CRM action
Add your CRM and its create-contact action. Map the lead details from LeadSource into the contact's fields, then test the step once.
- 05
Check, then publish
Open the CRM and check the new contact. If it looks right, click Publish: every matching lead now lands in the CRM at once, at one task per lead.
The LeadSource trigger
1 event starts a Zap when something happens in LeadSource, and one of them is instant: the app calls Zapier straight away, whatever your plan.
Lead Received
Instant triggerIn Zapier“Triggers when a new lead is received by one of your campaigns.”
Runs the Zap each time one of your campaigns receives a new lead. It is the hook for everything that should happen once a lead you paid for comes in: a contact in your CRM, a message to the team, a line in a report.
The LeadSource action
LeadSource gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.
Submit Lead
ActionIn Zapier“Submit a lead to be matched to an available campaign.”
Sends a lead to LeadSource to be matched to an available campaign. Phone, Zip Code and Service are required, and a TCPA Compliant field says whether the lead is TCPA compliant.
When a LeadSource Zap breaks
Zapier attaches no help article to LeadSource and documents no limit of its own. What goes wrong is what goes wrong on any Zap, plus the strict fields of Submit Lead.
Most problems come from a Zap doing exactly what it was set up to do. Check these four cases first. If a Zap still misbehaves, see our Zapier troubleshooting guide.
Submit Lead fails on Service
Service only takes the listed values, such as PLUMBING, SOLAR or KITCHEN. Any other wording from your form stops the action. Map a value from the list.A required field is empty
Phone, Zip Code and Service are all required. If the source leaves one blank, Submit Lead cannot run for that lead. The failed action is not billed.Older leads never come through
A Zap only reacts to leads received after you switch it on. Earlier leads stay in LeadSource; moving them is a separate job.A sudden batch goes quiet
A trigger that suddenly sends a huge batch, after an import or a migration, can be held back by Zapier's flood protection.
Need help automating LeadSource with Zapier?
A person reads every message.
