NZLeads Zapier integrationAutomate NZLeads with Zapier.
NZLeads Zapier integration: 1 trigger and 1 action, no search step. Enough to hand your Yelp leads to NZLeads so they get an automatic answer, and to pass every new NZLeads lead on to your sheet, CRM or team chat as soon as Zapier sees it.
Verified Trustpilot reviews · AI, automation & growth agency
What the NZLeads Zapier integration is for
NZLeads replies to incoming leads for you, so a prospect who reaches out does not wait for someone to pick up. The Zapier integration plugs that service into the rest of your tools: one action feeds leads into NZLeads, one trigger reports each new lead it holds.
Three results people build with it. A lead pushed in for an automatic answer: Send Lead hands a Yelp lead to NZLeads, with its lead ID, business ID and a temporary phone number. A clean lead log: New Lead starts a Zap for each new lead and writes it as a row in a spreadsheet, so nothing depends on someone copying it. A heads-up for the team: the same trigger can post the lead in a chat channel, so a person follows up after the automatic reply.
Now what it does not do. There is no search step, so a Zap cannot look up an existing NZLeads lead, and there is no action to update or delete one. Send Lead is built around Yelp: its three required fields are Yelp identifiers plus that phone number, which means leads from other sources do not fit as they are. And the trigger works by polling, not instantly, so on the free plan a new lead can wait up to 15 minutes before your Zap sees it.
Comparing platforms for lead handling? Our n8n vs Zapier comparison is the next read, and so is the Zapier review.
Zapier words, explained once
Seven terms carry the whole page. Here they are in everyday English.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run every time the trigger event happens.
- Trigger
- The event in an app that starts the Zap. Once you switch the Zap on, Zapier keeps waiting for that event.
- Action
- What the Zap does once it has started: the step that sends, writes or moves something for you in an app.
- Task
- The unit Zapier bills: one action your Zap completes successfully. Your plan's allowance is counted in tasks.
- Polling vs instant
- Polling: Zapier checks the app on a timer for new items. Instant: the app itself warns Zapier the moment something happens.
- Filter
- A step that lets the Zap carry on only when what arrived meets your condition, and stops it in every other case.
- Multi-step Zap
- Any Zap beyond one trigger and one action. A filter or a second action makes one, and it then needs a paid plan.
What an NZLeads Zap really costs
NZLeads is open to every Zapier plan, the free one included. You pay in tasks, and only for actions that succeed.
- Free plan100 tasks a month, unlimited Zaps
- Zap size on Free2 steps: one trigger, one action
- Paid plan requiredNo, NZLeads works on Free
- NZLeads trigger1 polling, 0 instant
The New Lead trigger costs nothing, however often Zapier checks for leads. Each successful action counts one task: a Zap that logs a lead and pings the team spends two per lead. A failed action is not counted. The free plan has a size limit nobody mentions: one trigger, one action. Add a filter or a second action and the Zap becomes multi-step, which needs a paid plan. The interval grid matters here, because New Lead is a polling trigger.
Connect your NZLeads account to Zapier
- 01
Go to your connections
In Zapier, open the Apps page of your account. A connection is your NZLeads account linked to Zapier once, then reused by every step that touches NZLeads. Click + Add connection.
- 02
Select NZLeads
Search for NZLeads in the dialog, select it and click Add connection. You need an NZLeads account already: Zapier signs you in to it, it does not open one for you.
- 03
Sign in and grant access
A tab opens on NZLeads. Log in with the account that handles your leads, then allow Zapier to use it. The connection then appears in your list, ready for New Lead and Send Lead.
Your first NZLeads Zap, step by step
GoalLog every new NZLeads lead in a spreadsheet and warn the sales team in their chat channel.
- 01
Create the Zap
Start a new Zap in Zapier. The editor shows an empty trigger card on top and an empty action card under it, ready to fill.
- 02
Set the trigger
Pick NZLeads, then
New Lead, then your connection. It is a polling trigger: Zapier checks for new leads at the interval of your plan. - 03
Test the trigger
Run the test. Zapier fetches the three most recent leads of your account; pick one so the next steps are mapped on real data.
- 04
Add the two actions
Add your spreadsheet app and map the lead details into a new row, then add your chat app and write the alert. Two actions make it a multi-step Zap.
- 05
Test, then publish
Test each action and check the row and the message really arrived. Then click Publish; this Zap needs a paid plan because of its second action.
The NZLeads trigger
1 event starts a Zap when something happens in NZLeads. Zapier checks for them at the interval your plan allows.
New Lead
Polling triggerIn Zapier“Triggers when there's a new lead.”
Each lead that shows up in NZLeads starts the Zap, which can then copy it to a CRM, a sheet or a sales channel. It is the only way to get NZLeads data out to the rest of your tools through Zapier, so most Zaps for this app begin here.
The NZLeads action
NZLeads gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.
Send Lead
ActionIn Zapier“Sending leads to NZLeads”
Hands a lead to NZLeads so the service can answer it automatically, with the Yelp references that identify the request and the business.
When an NZLeads Zap breaks
Zapier lists no help article and no rate limit specific to NZLeads. What goes wrong comes from the way every Zap works.
Four cases explain most surprises with this app. If one of them hits you, the Zapier troubleshooting guide walks through the fixes.
Old leads are never picked up
A Zap only reacts to leads that arrive after you switch it on. Leads already in NZLeads stay where they are; moving that backlog is a separate job.The Zap feeds itself
New Lead as trigger with Send Lead as action writes where the trigger watches: each lead sent in can start the Zap again and burn your tasks fast.A big batch gets held back
After a bulk import or a migration, a trigger that suddenly returns a huge batch of leads can be held back by Zapier's flood protection.The same lead never fires twice
On a polling trigger Zapier remembers the leads it has already seen. The same lead does not start the Zap twice, and that is by design.
Need help automating NZLeads with Zapier?
A person reads every message.
