- Home
- Resources
- Integrations
- LeadSimple
LeadSimple Zapier integrationAutomate LeadSimple with Zapier.
The LeadSimple Zapier integration gives you 17 triggers, 12 actions and 8 searches. Every trigger is instant, so leads, processes, calls and tasks reach your other tools the moment they change, even on the free plan, with no waiting.
Verified Trustpilot reviews · AI, automation & growth agency
What the LeadSimple Zapier integration actually does
Zapier sits between LeadSimple and the rest of your tools. When something moves in LeadSimple (a lead changes stage, a call ends, a task gets done), Zapier hears about it straight away and runs the steps you chose. It also works the other way: other tools can create leads, processes and notes inside LeadSimple.
A handoff that starts itself. A lead reaches the stage you care about, Lead Changes Stage fires, and Create Process opens the follow-up process in the right Process Type. Nobody has to remember to do it.
A paper trail on every lead. Pair Search Lead with Create Lead Note and whatever happens elsewhere (a form answer, a message, a status change) lands as a note on the lead it belongs to.
Task activity your team can watch. Task Completed Manually and Task Completed Automatically split human work from auto-sent work, so you can report on one without the other.
What Zapier does not do here. There is no delete action: a Zap can create and update leads, processes, contacts, properties and units, but never remove them. Updates to contacts, properties and units only run on records that already exist. And a Zap does not reach back in time, so old leads stay where they are.
If you are still choosing a tool, see our n8n vs Zapier comparison and our Zapier review.
Zapier vocabulary in one minute
Eight words you will see in the editor. Each one is explained once here, then used as is on the rest of the page.
- 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 waits for that event and nothing else.
- Action
- What the Zap does once it has started: the step that writes, sends or moves something for you in an app.
- Task
- The unit Zapier bills. One task is one action your Zap completes successfully, and your plan counts those.
- Polling vs instant
- A polling trigger is checked on a timer. An instant trigger is reported by the app the moment it happens. All 17 LeadSimple triggers are instant.
- Filter
- A step that lets the Zap carry on only when what arrived meets the condition you set, and stops it quietly otherwise.
- Search step
- A step that looks up something that already exists in an app, so later steps can use what it found, such as a lead ID.
- Connection
- Your LeadSimple account linked to Zapier once, then reused by every step in every Zap that touches LeadSimple.
What a LeadSimple Zap really costs
LeadSimple is not a premium app, so it works from the free plan. What you pay for is tasks, not triggers.
- Free plan100 tasks a month, unlimited Zaps, two-step Zaps only
- Premium appNo, LeadSimple runs on the free plan
- Trigger typeAll 17 triggers are instant, so the interval grid does not apply
The trigger never costs a task, and neither does Zapier listening for new events. Each action that succeeds counts once, so a Zap with three actions eats three times as much as a Zap with one. An action that fails is not counted. The catch on the free plan: Zaps stop at two steps, one trigger and one action. Add a filter, a search such as Search Lead, or a second action, and you have a multi-step Zap that needs a paid plan.
Connect LeadSimple to Zapier in three steps
- 01
Open your apps and add a connection
In Zapier, go to the Apps page of your account and click + Add connection. Type LeadSimple in the dialog and pick it from the list. You need a LeadSimple account first, with access to whatever the Zap should read or change.
- 02
Sign in to LeadSimple
Click Add connection. A new tab opens on LeadSimple: sign in with the account the Zap should act as. Use one that can see the pipelines and process types you plan to automate, because the Zap only sees what that account sees.
- 03
Grant access and reuse it
Allow Zapier to access the account. The connection now shows on your Apps page, and every LeadSimple step in every Zap can reuse it without signing in again.
Your first LeadSimple Zap, step by step
GoalWhen a lead moves to a chosen stage, open a follow-up process in LeadSimple.
- 01
Create the Zap and pick the trigger
Start a new Zap, choose LeadSimple as the app and Lead Changes Stage as the event. Select your LeadSimple connection. The bolt in the editor tells you it is an instant trigger.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent items from your account, so you can pick a real lead change and map its fields in the next steps.
- 03
Add a filter
Click the plus icon and add Filter. Set the field to look at, the rule and the value, so only the stage you care about goes through. This makes the Zap multi-step, so it needs a paid plan.
- 04
Add the action
Add LeadSimple with Create Process. Choose the Process Type and the Stage the new process should start in, then map the lead details from the trigger into the remaining fields.
- 05
Test, then publish
Test the action once and check the new process in LeadSimple. If it looks right, click Publish to switch the Zap on. From then on, every matching stage change runs it.
The 17 LeadSimple triggers
17 events start a Zap when something happens in LeadSimple, and 17 of them are instant: the app calls Zapier straight away, whatever your plan.
Call Completed
Instant triggerIn Zapier“Triggers when a new call is completed.”
Starts the Zap each time a call wraps up in LeadSimple, so whatever follows a conversation can happen on its own. Log the call in a shared sheet, ping a channel or queue a follow-up.
Lead Changes Pipeline
Instant triggerIn Zapier“Triggers when a lead changes pipelines.”
Reacts when a lead jumps from one pipeline to another, which usually means the kind of work around it has changed. The Zap gets the lead at that moment.
Lead Changes Stage
Instant triggerIn Zapier“Triggers when a lead changes stages.”
The workhorse trigger: it fires whenever a lead moves to another stage. Most handoffs hang off this one, because stages are where your team marks progress.
Lead Changes Tags
Instant triggerIn Zapier“Triggers when a lead's tags change.”
Watches the tags on your leads and starts the Zap when they change. Tags are often the lightest way for a team to flag something, so this turns a click in LeadSimple into a signal for other tools.
Lead Created
Instant triggerIn Zapier“Triggers when a new lead is created.”
Runs the Zap for every new lead in LeadSimple, wherever it came from. It is the simplest way to mirror new business into a spreadsheet, a reporting tool or a welcome sequence.
Lead Opens Email
Instant triggerIn Zapier“Triggers when a lead opens email.”
Fires when a lead opens an email. That open is a small sign of interest, and this trigger lets you act on it while it is fresh.
Lead Is Reassigned
Instant triggerIn Zapier“Triggers when a lead is reassigned.”
Catches the moment a lead changes owner inside LeadSimple. The new owner may not notice right away, so this trigger is a good place to hang a heads-up.
Inbound Conversation Created
Instant triggerIn Zapier“Triggers when an inbound conversation is created.”
Fires when someone reaches out first and a new inbound conversation appears in LeadSimple. It is your hook for anything that should happen when a contact writes or calls in.
Outbound Conversation Created
Instant triggerIn Zapier“Triggers when an outbound conversation is created.”
The mirror of the inbound trigger: it runs when your side starts a new conversation from LeadSimple. Useful to keep track of outreach volume without exporting anything.
Process Changes Stage
Instant triggerIn Zapier“Triggers when a process changes stages.”
Processes in LeadSimple carry the work that follows a lead, organised by Process Type and Stage. This trigger fires each time one of them moves to another stage.
Process Changes Tags
Instant triggerIn Zapier“Triggers when a process changes tags.”
Whenever the tags on a process change, this one runs. Teams that flag blockers or priorities with tags can turn that flag into an alert outside LeadSimple.
Process Created
Instant triggerIn Zapier“Triggers when a new process is created.”
Fires on every new process, whoever or whatever opened it. If a Zap of yours creates processes with Create Process, those show up here too.
Process Reassigned
Instant triggerIn Zapier“Triggers when a process is reassigned.”
Runs when a process changes hands. Handovers are where work tends to stall, so a short automated message to the new owner saves a lot of chasing.
Task Completed
Instant triggerIn Zapier“Triggers when a task is completed.”
The broad version of the task triggers: it fires for every task marked done, however it was completed. Pick it when you do not care how the task was closed.
Task Completed Automatically
Instant triggerIn Zapier“Triggers when a task is completed automatically. An automatic task set to auto send.”
Narrows things to tasks set to auto send, the ones LeadSimple completes on its own. It lets you check that automated steps really went out.
Task Completed Manually
Instant triggerIn Zapier“Triggers when a task is completed manually. A manual task that does NOT use auto send.”
The human side: it fires only when a person completes a task that does not use auto send. That makes it the right signal for measuring team activity.
Task Created
Instant triggerIn Zapier“Triggers when a task is created.”
Fires as soon as a new task exists in LeadSimple. Good for pushing work to wherever the assignee actually looks during the day.
The 12 LeadSimple actions
LeadSimple gives you 12 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Create Call
ActionIn Zapier“Creates a Call in your account”
Records a call in LeadSimple from details held elsewhere. It wants a From Number and a To Number, both required.
Create Lead
ActionIn Zapier“Creates a Lead in one of your Pipelines. You'll need to specify a Pipeline and a Stage.”
Drops a new lead into one of your pipelines, at the stage you choose. The Zap needs both a Pipeline and a Stage to run.
Create Lead Note
ActionIn Zapier“Creates a note on a lead. You'll need to find a lead first using the 'Find Lead' search action.”
Writes a note on an existing lead. You first need the lead itself, which is what Search Lead is for, then the note text.
Create Process
ActionIn Zapier“Creates a Process in one of your Process Types. You'll need to specify a Process Type and a Stage.”
Opens a process under a Process Type you pick, starting at a given Stage. This is how a closed lead turns into actual work.
Create Process Note
ActionIn Zapier“Creates a note on a process. You'll need to find a process first using the 'Find Process' search action.”
Adds a note to a process, after a Search Process step has found it. The note text is required, and the process must already exist in your account.
Tag Conversation
ActionIn Zapier“Tags a Conversation.”
Puts a tag on a conversation. Both the Conversation and the Tag are required.
Update Contact
ActionIn Zapier“Updates a Contact in your account.”
Refreshes a contact record. Only the Contact is required, which you can find with Search Contact just before, then you map the details that changed.
Update Conversation
ActionIn Zapier“Updates a Conversation.”
Modifies an existing conversation, chosen in the required Conversation field.
Update Lead
ActionIn Zapier“Updates a Lead in one of your Pipelines. You'll need to specify a Pipeline and a Stage.”
Changes an existing lead. You point it at the Pipeline and the Lead, then set what should change.
Update Process
ActionIn Zapier“Updates a Process. You'll need to specify a Process Type and a Stage.”
Edits a process you already have. It requires the Process Type and the Process, so a search step often comes first to hand the Zap the right one.
Update Property
ActionIn Zapier“Updates a Property.”
Changes a property record. The Property field is required; Search Property finds it by name or address if the earlier steps do not carry it.
Update Unit
ActionIn Zapier“Updates a Unit.”
Edits a single unit on a property. It needs both the Property and the Unit, and Search Unit looks units up by their Unit Number.
The 8 LeadSimple searches
8 search steps look for data that already exists in LeadSimple, so a later step can use it.
Searches sit at the bottom of the action list in the editor, under the SEARCH heading. Each one finds something that already exists so a later step can use it. Several LeadSimple actions need one first: a note on a lead needs the lead. Every search adds a step, so it makes the Zap multi-step. LeadSimple offers no find-or-create variant, so a search never creates anything here.
Search Contact
SearchIn Zapier“Searches a contact in your account by name, phone number or email address.”
Finds a contact from a name, a phone number or an email address. The Search field is the only required one.
Search Lead
SearchIn Zapier“Searches a Lead in your account by name, contact email address or phone number, property address etc. You can specify a Pipeline to search within, otherwise it searches all Pipelines in your account.”
Looks up a lead by name, contact email or phone, property address and so on. Pipeline and Search are both required here.
Search Process
SearchIn Zapier“Searches a Process in your account by name, contact email address or phone number, property address etc. You can specify a Process Type to search within, otherwise it searches all Process Types in your account.”
Finds a process from a name, a contact detail or a property address. You can narrow it to one Process Type or let it cover them all.
Search Property
SearchIn Zapier“Searches a Property in your account by name or address.”
Locates a property by its name or address, with a single required Search field. Whatever it returns can feed any later step that asks for a Property.
Search Unit
SearchIn Zapier“Searches the units on the property by the Unit Number”
Looks through the units of one property by Unit Number. It needs the Property as well as the Search value, so it always works inside a single property.
Search User
SearchIn Zapier“Searches a user in your account by name or email address.”
Finds a member of your LeadSimple account by name or email address.
Get Lead
SearchIn Zapier“Gets a Lead in your account by ID.”
Pulls one lead straight from its ID, the required field. No fuzzy matching, so it returns exactly that lead or nothing.
Get Process
SearchIn Zapier“Gets a Process in your account by ID.”
Fetches one process by its ID, with no guessing involved. The ID is required.
The three settings every search exposes
- Successful if no search results are found?Left on its default, a search that finds nothing stops the Zap and skips the steps that depended on it. Switched on, the Zap carries on empty-handed.
- Create X if it doesn't exist yet?This box turns a search into a find-or-create. LeadSimple does not offer it, so expect the search to stop or carry on, never to create.
- If multiple search results are found?Three ways out when several items match: keep the first one (the default), stop the Zap, or pass all of them on at once.
When a LeadSimple Zap breaks
Zapier attaches no help article to LeadSimple and no app-specific limit is documented. What breaks is what breaks on every Zap, with a few twists from LeadSimple's own triggers.
Most surprises come from the Zap doing exactly what it was told. Here are the four cases to check before blaming LeadSimple. If a Zap still misbehaves, see our Zapier troubleshooting guide.
Old leads never come through
A Zap only reacts to what happens after you switch it on. Leads, processes and tasks that already existed are not picked up; moving that backlog is a separate job.The Zap keeps setting itself off
A Zap that writes where its own trigger watches runs again and again. Updating a lead's stage from a Zap built on Lead Changes Stage is the classic case, and it burns tasks fast.A bulk change goes quiet
A trigger that suddenly sends a huge batch, after an import or a mass reassignment, can be held back by Zapier's flood protection instead of running for every item.A search finds nothing and the Zap stops
By default, a search with no result stops the Zap there. Check the spelling the other tool sends, or switch on the setting that lets the Zap carry on.
Need help automating LeadSimple with Zapier?
A person reads every message.



