Webhook

Send leads from any app that can call a webhook to the project

How it works

A webhook sends lead details from your marketing tool to LeedsApp the moment a lead comes in. Point your tool at the webhook URL below and send each lead as JSON.

Your webhook

The u, p and k values in the URL tell LeedsApp which project the lead is for. Do not edit them. No other key or password is needed.

Body fields

namestringREQUIREDThe visitor's name.
phoneNumberstringREQUIREDWith the country code, like +919876543210.
emailstringOPTIONALSend an empty string when it is left blank.
citystringOPTIONALSend an empty string when it is left blank.
any other keystringOPTIONALSaved on the lead as a custom field.

Other field names we accept

Your tool can use its own field names. These are read as name, phone number, email and city.

Name · 51 names
namefull_nameuser_namefirst_namelast_namefnamelnamegiven_name
Phone number · 47 names
phonenumbermobilenumbermobilemobile_numbercellcell_numberphonephone_number
Email · 37 names
emailemail_addressemail_ide_maile_addresselectronic_mailemail_contactemail_input
City · 45 names
citycity_nametowntown_namelocalitydistrictdistrict_namestate

Set it up in your tool

Zapier
  1. Create a Zap. Log in at zapier.com, click + Create in the left sidebar and choose Zap workflows.
  2. Pick where your leads come from. Search for the app where your leads arrive (a form, ad or booking tool) and pick its event for a new lead or new entry. Connect your account in that app when Zapier asks.
  3. Test the trigger. Open the Test tab and click Test trigger. Pick one lead and click Continue with selected record.
  4. Add Webhooks by Zapier. Click + to add an action. Search for Webhooks by Zapier, pick the event POST and click Continue.
  5. Paste your LeedsApp URL. Set Payload Type to JSON. In URL, paste the lead URL from this page.
  6. Map the lead's details. Under Data, add four rows. Type the key on the left and pick the matching answer from your app on the right: name, phone, email and city.
  7. Test and publish. Click Test step. A reply with status 200 means LeedsApp got the lead. Then click Publish so the Zap stays on.
Full Zapier guide →
Pabbly
  1. Create a workflow. Log in at connect.pabbly.com, click Create Workflow and name it, for example Sunrise Interiors leads.
  2. Set the trigger. In the Trigger step, choose the app where your leads arrive and its new-lead event. Connect it and bring in one test lead.
  3. Add API by Pabbly. In the Action step, choose the app API by Pabbly and the action event Execute API Request.
  4. Set POST and the URL. Set the method to POST, Payload Type to JSON and authentication to No Auth. Paste the lead URL from this page into the endpoint URL box.
  5. Map the lead's details. Under Set Parameters, add four rows: name, phone, email and city. In each value box, pick the matching answer from the trigger step.
  6. Test and switch on. Click Save and Send Test Request. A reply with status 200 means LeedsApp got the lead. Make sure the workflow is switched on.
Full Pabbly Connect guide →
Make (Integromat)
  1. Create a scenario. Log in at make.com, open Scenarios and click Create a new scenario.
  2. Add your lead app. Click the big + and pick the app where your leads arrive, with its module that watches for new leads or entries. Connect your account.
  3. Add HTTP Make a request. Click + next to the first module, search for HTTP and choose Make a request.
  4. Set the URL and body type. Set Authentication type to No authentication. Paste the lead URL from this page into URL. Set Method to POST, Body content type to application/JSON and Body input method to JSON string.
  5. Type the lead's details. In the body box type the four keys below. Between each pair of quotes, drop in the matching value from your lead app's module.
  6. Test and turn on. Click Run once and send one test lead from your app. The HTTP module should show status 200. Save the scenario and switch it on.
Full Make guide →
HubSpot
  1. Start a Zap with HubSpot. In Zapier click + Create › Zap workflows. For the trigger pick HubSpot, event New Form Submission, connect your HubSpot account and choose the form.
  2. Test the trigger. Submit the form once yourself, then click Test trigger so Zapier picks up a real submission to map.
  3. Add Webhooks by Zapier. Add the action Webhooks by Zapier, event POST.
  4. Paste your LeedsApp URL. Paste your LeedsApp URL in URL and set Payload Type to JSON.
  5. Map the fields and test. Under Data add name (First name + Last name), phone, email and city, then click Test step; a reply with code: success means LeedsApp got the lead.
  6. Publish. Click Publish. New submissions reach the project within a minute or two.
Full HubSpot Forms guide →
Marketo
  1. In Marketo open Admin → Webhooks and click New Webhook.
  2. Paste the webhook URL above as the URL, set Request Type to POST and Request Token Encoding to JSON.
  3. In Template, write the body with lead tokens, for example {"name": "{{lead.First Name}} {{lead.Last Name}}", "phoneNumber": "{{lead.Mobile Phone Number}}", "email": "{{lead.Email Address}}"}.
  4. Add the flow step Call Webhook with this webhook to the Smart Campaign that runs when a lead fills your form.
IndiaMART · has its own page

IndiaMART sends leads with its own format, so it has its own lead URL. Open the IndiaMART page →

Your own tool
  1. Send a POST request to the webhook URL above, with the body as JSON.
  2. Include name and phoneNumber; add email, city and any other keys you have.
  3. A reply with status 200 means the lead was saved. See Responses for the other replies.

If leads don't arrive

  • Check the webhook URL was copied in full, including the part after ?
  • Check name and phone number are mapped. Use flat keys; nested objects are not read.
  • A reply saying phone number is not valid means the number is not a real mobile number; send it with the country code, e.g. +91 98765 43210.
  • Use Send in the console to check the URL works.

Need help? Write to support@leedsapp.com