LeedsApp← All integrations

n8n

Through Zapier / Pabbly · 15 min

Send leads from any app on n8n to the project

Before you start

You need n8n Cloud or your own n8n server (self-hosted n8n is free).
Steps use n8n's HTTP Request node, which works after any trigger node.

Your n8n lead URL

Your lead URL appears here when you open this page from the LeedsApp app: open the project, then Lead integrations and n8n.

Set it up in n8n

1
Create a workflowOpen n8n and click Create Workflow.
2
Add your lead app's triggerClick + to add the first step and pick the trigger of the app where your leads arrive, such as a new form entry. Connect your account.
3
Add an HTTP Request nodeClick + after the trigger, search for HTTP Request and add it.
4
Set POST and the URLSet Method to POST and paste the lead URL from this page into URL. Leave Authentication as None. Turn on Send Body, set Body Content Type to JSON and Specify Body to Using Fields Below.
5
Add the lead's detailsUnder Body Parameters, add four rows. Type name, phone, email and city as the Name, and drag the matching field from the trigger's output into each Value.
6
Test and turn onClick Execute step. The output should show LeedsApp's reply with code: success. Then click Publish at the top right so the workflow runs for every new lead (on older n8n versions, switch the workflow to Active).

What LeedsApp saves

n8n sendsSaved on the lead asnameNamephoneMobile numberemailEmailcityCityany other key you addCustom field
Lead source: n8n. Use these four keys; LeedsApp also reads first_name + last_name and mobile. Every lead needs a name and a valid mobile number. Any other key you add is saved as a custom field. If the number is already a lead, LeedsApp adds this project to it.

If leads don't arrive

  • Open Executions and check the HTTP Request node. 400 with insufficient-data means the name or phone was empty.
  • Check Body Content Type is JSON and the URL was pasted in full, including the part after ?.
  • Check the workflow is published (older versions: Active). A workflow you only test does not run on its own.
  • A 400 reply saying The mobile number is not valid means the phone answer was not a real mobile number. Map the phone question, not another field.

Need help? Write to support@leedsapp.com