Networx Zapier integrationAutomate Networx with Zapier.
Networx on Zapier comes with 1 trigger and 1 action, and no search. This Networx Zapier integration hands every lead a contractor receives from the platform to another tool, then can send Networx a flow log with the status of the run.
Verified Trustpilot reviews · AI, automation & growth agency
What the Networx Zapier integration does for you
Networx is a lead generation platform: it helps contractors find work by putting them in touch with homeowners. Through Zapier, each of those leads can start a Zap, an automation made of one trigger (the event that starts it) and one or more actions (what it then does for you). The lead leaves Networx and reaches the tools you already use.
Three results are within reach. A lead log you control: New Lead adds every request to a spreadsheet, so the whole team sees the same list without logging in to Networx. An alert that reaches the right person: the same trigger can feed an email or a messaging tool, so whoever handles the job hears about it at once. A delivery receipt back to Networx: Send Flow Log sends Networx the status of the run and the response from the last webhook, along with the Lead ID and Client ID it asks for.
Good news on timing: New Lead is an instant trigger. Networx itself tells Zapier about the lead, so the Zap starts right away even on the free plan. The polling interval of the plans never comes into play here.
What Zapier does not do with Networx: there is no search, so a Zap cannot look up an older lead. There is no action to create, change or close a lead either. The integration brings new leads out and sends a log back in, and that is the whole scope.
Comparing platforms before you commit? See our Make vs Zapier comparison, or open our Zapier review.
Zapier vocabulary in one minute
A handful of words carry this whole page. Here they are, kept simple.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run each time that event happens.
- Trigger
- The event in an app that starts the Zap. Once the Zap is switched on, Zapier waits for it, here a new Networx lead.
- Action
- What the Zap does once it has started: the step that writes, sends or moves something for you, such as a flow log.
- Task
- What Zapier bills: one action your Zap completes successfully. The allowance on your plan counts those, nothing else.
- Instant trigger
- A trigger the app reports itself. It calls Zapier the moment the event happens, so nothing waits for a scheduled check.
- Polling trigger
- The other kind: Zapier asks the app for new items at a fixed interval. Networx has none; its interval depends on the plan.
- Filter
- A step that lets the Zap go on only when what arrived meets the condition you set, and stops it otherwise.
- 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 a Networx Zap really costs
Networx is not a premium app: it runs on the free plan. You pay in tasks, and the trigger is never one of them.
- New Lead triggerNever costs a task
- Successful action1 task each
- Failed actionNot counted
- Free plan100 tasks a month, unlimited two-step Zaps
- Premium appNo
Receiving a lead costs nothing. Each action that succeeds counts as one task; an action that fails is not counted. So a Zap that adds a row and then sends a flow log uses two tasks per lead, and it needs a paid plan, because the free plan stops at two steps. The interval grid below belongs to every Zapier plan, but it does not apply to New Lead: that trigger is instant. A few apps and a few actions also take more than one task when they complete.
Connect your Networx account in 3 steps
- 01
Start from the Apps page
In Zapier, open Apps and click + Add connection. Search for Networx in the dialog, select it, then confirm with Add connection. Everything starts from your Zapier account, not from inside Networx.
- 02
Sign in to Networx
Log in to Networx in the tab that opens. You need an account on the app, plus read or write access on anything you do not own yourself and want the Zap to touch.
- 03
Grant access once
Grant Zapier access to the account. The connection (your Networx account linked once) is then reused by every step that uses Networx, in this Zap and in any later one.
Your first Zap: log each lead, then confirm it to Networx
GoalAdd every new Networx lead to a spreadsheet, then send Networx a flow log about that run.
- 01
Build: pick Networx and New Lead
Create a Zap, choose Networx as the app that starts it and New Lead as the event, then pick the connection you added. The editor marks this instant trigger with a lightning bolt.
- 02
Test the trigger on a real lead
Run the trigger test. Zapier brings back the three most recent leads of the account, so you choose a real one and map from actual data.
- 03
Add the spreadsheet row
Add your spreadsheet as the first action, choose the action that adds a row, and map each column to a value of the lead.
- 04
Add Send Flow Log (paid plan)
Add Networx again with Send Flow Log. Fill its four required fields, Lead ID, Client ID, Is Success and Webhook Response; check at test what each one expects. With two actions, the Zap is multi-step and needs a paid plan.
- 05
Test, then publish
Run each step once and read what came back before going further. When both actions look right, publish the Zap to switch it on: each lead then costs two tasks if both actions succeed.
The Networx trigger
1 event starts a Zap when something happens in Networx, 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 received.”
Each new lead received on Networx becomes a new start for your Zap, one run per lead. It is the only door out of Networx on Zapier, so every Zap you build here begins with it.
The Networx action
Networx gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.
Send Flow Log
ActionIn Zapier“Sends execution logs including status and response from the last Webhook.”
Sends Networx a log of the run: whether it worked, and the response returned by the last webhook, with the Lead ID and Client ID the action asks for.
When a Networx Zap breaks
Zapier attaches no help article to Networx, so the cases below are Zapier's general limits. They hold here as on any other app.
Go through them before you switch the Zap on. If a run still surprises you, see our Zapier troubleshooting guide.
Old leads stay where they are
A Zap only reacts to what happens after you switch it on. Leads Networx sent you before that are not picked up; moving them is a separate job.A Zap that sets itself off
As a general precaution: a Zap that writes into the very place its own trigger watches can start itself again and again and burn through your tasks fast.Flood protection on big batches
When a trigger suddenly returns a huge batch, after a bulk import or a migration, Zapier's flood protection can hold it back.Four required fields to fill
Send Flow Log needs Lead ID, Client ID, Is Success and Webhook Response. All four are required: check at test what each one expects before you publish.
Need help automating Networx with Zapier?
A person reads every message.
