Lets Insure Zapier integrationAutomate Lets Insure with Zapier.
The Lets Insure Zapier integration gives you 1 trigger, 1 action and 0 searches. Small, but enough to push every new lead out of the CRM the moment it appears, or to drop leads into it from the tools where they first show up.
Verified Trustpilot reviews · AI, automation & growth agency
What the Lets Insure Zapier integration actually does
Lets Insure is a CRM made for insurance agents, where leads, quotes and the client pipeline live. Linking it to Zapier means two things only: something happens when a lead is created in Lets Insure, and other tools can create leads in Lets Insure without anyone copying them by hand.
A lead that nobody misses. The New Lead trigger reports each new lead the moment it is created. Follow it with a message to your team chat and the right person hears about it before checking the CRM.
A pipeline that fills itself. Create Lead works the other way round. When a lead appears somewhere else first (a form, a sheet, an inbox), the Zap writes it into Lets Insure so the record exists where your agents work.
A copy of each lead outside the CRM. Same trigger, different destination: a row in your spreadsheet for every new lead, which gives you a running list you can sort and share without granting anyone access to the CRM itself.
Now the limits, because they matter here. Zapier sees only two operations on this app. There is no trigger for a new quote or a moved deal, no action to update or delete a lead, and no search to check whether a lead already exists before creating it. If your process depends on any of those, the integration as it stands will not cover it. If you are still deciding whether Zapier suits your agency at all, read our Zapier review before building anything on it.
Zapier vocabulary in one minute
Seven words come back on every page of this kind. Here they are in plain English, once.
- Zap
- The automation you build: 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 switched on, Zapier 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 your Zap completes successfully counts as one task on your plan.
- Polling vs instant
- Polling: Zapier checks the app on a timer. Instant: the app calls Zapier itself the moment the event happens.
- Filter
- A step that lets the Zap continue only when the incoming data meets a condition you set, and stops it otherwise.
- Connection
- Your Lets Insure account linked to Zapier once, then reused by every step that touches Lets Insure.
What it really costs
Lets Insure is not a premium app, so it runs on the free plan. What you pay for is tasks.
- Premium appNo, works on the free plan
- Free plan100 tasks a month, two-step Zaps
- TriggerFree, instant on every plan
- Each successful action1 task
The New Lead trigger never costs a task, and neither does Zapier watching for new leads. Each Create Lead (or any other action) that goes through counts as one task, and a failed one is not counted. So a Zap that posts one message per lead spends exactly one task per lead. The free plan gives 100 tasks a month and builds Zaps of two steps only: one trigger, one action. Add a filter or a second action and the Zap becomes a multi-step Zap, which needs a paid plan.
Connect your Lets Insure account
- 01
Open your connections
In Zapier, go to the Apps page of your account and click + Add connection. You need a Lets Insure account before you start, plus access to any leads you do not own but want the Zap to touch.
- 02
Pick Lets Insure
Type the app's name in the dialog that appears, select Lets Insure in the results, then click Add connection. A new browser tab opens on the Lets Insure side to finish the link.
- 03
Sign in and grant access
Log in to Lets Insure in that tab and allow Zapier to use the account. If the leads you want to touch belong to a colleague, make sure your login can read or write them.
Your first Zap: alert the team about the leads that matter
GoalEach new Lets Insure lead that meets your condition becomes a message in your team chat.
- 01
Create the Zap
Start a new Zap and choose Lets Insure as the app that starts it, with New Lead as the event. Select the connection you set up earlier.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent leads of the account, so you can pick a real one and map its fields in the next steps.
- 03
Add the filter
Click the plus icon, add Filter, then fill the three boxes: the field to look at, the rule, the value. Pick a text rule for text and a number rule for numbers.
- 04
Add the message
Add your chat tool as the action and drop the lead fields from the test into the message. Remember: the filter makes this a multi-step Zap, so a paid plan is required.
- 05
Test, then publish
Run each step once and read what came back, including the message as it lands in the chat. When it looks right, click Publish to switch the Zap on.
The Lets Insure trigger
1 event starts a Zap when something happens in Lets Insure, 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 is created.”
Fires each time a lead is added to Lets Insure and hands the following steps everything the CRM knows about it, so you can route, copy or announce that lead without opening the app.
The Lets Insure action
Lets Insure 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“Creates a new lead in the CRM”
Writes a new lead into Lets Insure from data another app collected, so the prospect is in the pipeline without retyping.
When it breaks
Zapier attaches no help article to Lets Insure, and no app-specific limit is documented. What breaks here are the general rules of Zapier.
Four situations come back most often. None of them shows an error at build time, which is why they surprise people. When a run does go wrong, start from our Zapier troubleshooting page and the task history of the Zap.
Old leads never show up
A Zap only sees leads created after it is published. Everything already in Lets Insure stays where it is, and importing the backlog is a separate job.The Zap keeps setting itself off
New Lead plus Create Lead on the same account is a loop: each created lead fires the trigger again and burns through your tasks fast.A bulk import goes quiet
When hundreds of leads arrive at once after an import or a migration, Zapier's flood protection can hold the batch back instead of running them all.The filtered Zap needs a paid plan
A filter turns the Zap into a multi-step Zap. On the free plan, Zaps stop at two steps, so the filtered version needs a paid plan.
Need help automating Lets Insure with Zapier?
A person reads every message.
