Skip to main content
TradeVulcan logoTradeVulcan
App Guides
Leads Forge
Networx

Networx Leads integration for Leads Forge

Set up Networx Custom Webhook delivery for a Leads Forge deployment, including the deployment URL, API key, payload expectations, and go-live checks.

Leads Forge setup workspace with lead-source and webhook configuration
Leads Forge setup: Configure supported partner lead sources and the workflow that receives them. Sanitized demo workspace.

Overview

Leads Forge can receive supported Networx lead payloads through a deployment-specific Custom Webhook endpoint. The endpoint creates or updates the TradeVulcan lead, records the source payload in a redacted form, and lets the deployment's AI SMS and CRM booking rules continue from the same workflow used for other supported partner leads.

Where to find the setup values

  1. Open the Leads Forge app from the dashboard.
  2. Open the deployment that should receive Networx leads.
  3. Choose Partners, then Networx Leads.
  4. Generate an API key if one is not already present.
  5. Copy the Webhook URL and API Key into Networx Custom Webhook setup.

Networx Custom Webhook fields

Networx fieldRecommended value
CRMCustom Webhook
Webhook URLThe deployment-specific TradeVulcan Networx URL.
API KeyThe generated Leads Forge Networx API key.
URL ParametersLeave blank unless TradeVulcan support asks for a scoped setup.
ProductAll, unless the deployment should receive only a specific lead product.
NetworkAll, unless the deployment should receive only a specific network segment.

Accepted payload shape

The webhook accepts JSON object deliveries and JSON arrays. Leads Forge normalizes common customer, phone, email, service, address, appointment, consent, fee, source, and interview/question fields before creating the lead.

Go-live checklist

  1. Enable Networx lead intake on the deployment.
  2. Confirm consent attestation and STOP handling for automated SMS.
  3. Send one Networx test lead and verify the Last webhook panel changes from Waiting to received or accepted.
  4. Open the created lead from the dashboard and confirm the service, customer contact, address, and source details are understandable.
  5. Review CRM booking settings before enabling live booking for qualified leads.

Troubleshooting

  • 401 means the API key is missing or does not match the current deployment key.
  • 403 means the Leads Forge deployment or Networx intake is not enabled.
  • 400 means TradeVulcan received the request but could not find a lead payload to normalize.
  • After rotating the API key, update Networx before sending more leads.

Security notes

Do not paste real customer payloads, webhook keys, full phone numbers, full emails, or private Networx account data into public docs or support chat. Use the dashboard setup panel for secrets and the lead record for redacted delivery status.