Send Leads to LeadCentre With Make's HTTP Module
There's no LeadCentre app in Make. It works by ending your scenario with Make's HTTP module, which posts each lead to your LeadCentre URL. Any app that can start a scenario can then send leads to LeadCentre.
Via Zapier/Make: Connect it through a Zapier or Make account of your own.
What This Does
A Make scenario starts with a trigger module for the tool your leads come from. Add the HTTP app's Make a request module after it, and it posts each bundle to your LeadCentre URL as JSON. LeadCentre matches the fields and creates a lead. One bundle means one post, so you don't need to build arrays.
What you need
- A Make account of your own. Make's plans are measured in credits, including a free plan with a monthly allowance. Most actions use one credit. Its HTTP documentation doesn't list a plan restriction, but check Make's pricing page as this may change.
- A trigger for your tool. Search Make's apps to check your tool has one.
- An Admin login on your LeadCentre account, so you can create a key and match fields.
Credits and timing
How soon a lead arrives depends on your trigger:
- Instant triggers start the scenario when data arrives. Set the schedule to Immediately.
- Polling triggers check on a schedule. The default is every 15 minutes, and the shortest interval depends on your plan. Frequent checks can use up credits even when nothing is new, so watch your allowance.
Errors matter more with instant triggers
With Return error if HTTP request fails on, a 401 or 429 from LeadCentre counts as a failed run, which is what you want. But Make's scenario settings say a scenario with an instant trigger is deactivated on its first error. Turn on storing incomplete executions, so a failed run is parked for you to fix and rerun, and the scenario stays on. Polling scenarios stop after a number of consecutive errors, which you can set.
Useful For
- Businesses on a tight budget who want to try this on Make's free allowance first
- People already building Make scenarios who are comfortable with modules and mapping
- Agencies with client lead sources that vary from one account to the next
- Anyone whose form tool's own webhook sends a format LeadCentre doesn't read, such as Jotform, but which has a Make trigger
How Leads Flow Into LeadCentre
Step 1
A lead appears in your other tool
A form, ad platform, sheet or booking tool starts the scenario.
Step 2
Make runs the scenario
When the data arrives with an instant trigger, or at the next check with a polling one.
Step 3
The HTTP module posts it
Make a request sends your mapped fields to your LeadCentre URL as JSON.
Step 4
LeadCentre creates the lead
Your saved matching fills in the fields, and a push notification goes to the app.
How to Set It Up
- 1
Create a key in LeadCentre
Go to Settings > Connections. Under "Add another key", type the name of the source and press "Create". Press "Copy" and keep the URL safe, as it's only shown once. The key's name becomes the lead's source unless you send your own.
- 2
Add your trigger module
In Make, create a scenario and add the trigger for your source app. Connect your account and run it once, so Make has sample data to map from.
- 3
Add Make a request
Add the HTTP app's Make a request module. Paste your LeadCentre URL into URL, whole, and set Method to POST. Your URL already holds the key, so you don't need credentials or a query parameter. Check Make's guide if your version of the module looks different.
- 4
Set the body
Set the body content type to application/JSON and enter your fields, using a data structure so Make escapes special characters for you. Use the names in the table further down, so Smart Match can recognise them. Don't choose multipart/form-data: LeadCentre doesn't read it, and refuses it with a 415. application/x-www-form-urlencoded works too.
- 5
Set how it handles responses
Set Parse response to Yes, so you can read the results. Turn on Return error if HTTP request fails. In the scenario settings, turn on storing incomplete executions.
- 6
Listen, then run once
In LeadCentre, follow "Next: test and match fields" and press "Listen for test data". In Make, press Run once and create a lead in your source tool if it's waiting for one. The HTTP module's output should show results as test, and the fields appear under "2. Match the fields" a few seconds later.
- 7
Match the fields
Check Smart Match's suggestions, choose a field for each row or leave it on Do not use, then press "Save field matching".
- 8
Stop listening and switch on
Press "Stop listening", because anything sent while listening counts as test data, including a real lead. Set the schedule, switch the scenario on, then create a real test lead and check it appears in your Leads list.
Supported Fields
These are the names we'd use in the module's body. Smart Match recognises them, and they stay the same if you swap the trigger later. Map each one to the value from your trigger. Anything else can go into a custom field, which you can create on the matching screen.
| Field sent | Usually matched to |
|---|---|
| name, or first_name and last_name | Full name, or First name and Last name |
| phone | Phone (mobile or landline) |
| postcode | Postcode |
| service | Enquiry type |
| message | Enquiry / Message |
| lead_source | Lead source |
| created_at | Date received |
| id (your source tool's ID for the lead) | Unique ID (stops duplicates) |
Common Problems
My test data isn't showing in LeadCentre
Press "Listen for test data" first, as it stops after 15 minutes. Check the scenario actually reached the HTTP module: with a trigger waiting for new data, Run once does nothing until a lead arrives. Read the module's output: a 401 means a wrong or incomplete URL, a 415 means the body is multipart, and a 200 means it arrived, so check you have the right key's page open.
The HTTP module fails with a 415
The body content type is set to multipart/form-data, which LeadCentre doesn't read, so no lead was created. Change it to application/JSON, then test again.
A lead shows "Waiting for field matching"
It was sent before anything was matched on that key, so it's being held. Match the fields and press "Save field matching". The banner tells you how many waiting leads were added.
Make turned my scenario off
A scenario with an instant trigger is deactivated on its first error, unless storing incomplete executions is on. Check the history for the response. Repeated 401s mean the URL was replaced, and a 429 means more than 120 leads in a minute for that key. Fix it and switch the scenario on again.
A real lead didn't arrive, and the module's output says test
The key was listening, or your URL has &test=1 on it. That lead was treated as test data and won't become a lead. Press "Stop listening" or remove test=1. Then find the lead in your source tool, so you can contact them.
My credits are running out
A polling trigger can use credits each time it checks, even when nothing is new. Use a longer interval, or an instant trigger if your tool has one. Make's own scenario history shows what each run used.
I lost the webhook URL
It's shown once, and LeadCentre only keeps a scrambled copy, so it can't be looked up. Open the key and press "Replace this URL", or "Get a URL to copy" if it has never been used. Paste the new one into the HTTP module and save the scenario. Your field matching stays.
I need to rotate the key
With your scenario open, press "Replace this URL", as the old one stops at once. Paste the new one into every scenario using that key, and save. Runs in the gap get a 401, so check incomplete executions and retry them once you've updated it.
Questions About This Connection
Is there a LeadCentre app in Make?
No. It works through the HTTP module, posting to your LeadCentre URL. You won't find LeadCentre modules in Make, and it can't pull data out of LeadCentre.
Zapier or Make?
Use whichever you already pay for. Make has a free plan to start on, and Zapier's Webhooks by Zapier needs a paid plan. Check each tool has a trigger for your source, and compare costs at your lead volume.
Should the key go in the URL or a header?
Either works. Pasting the URL as given is simplest. To keep it out of the URL, remove the ?key= part and add a header called x-api-key with the key as its value.
How do I stop a rerun creating a second lead?
Send your source tool's ID for the lead as a field called id, and match it to Unique ID. A repeat is then skipped. Make sure the ID is unique across your account, including other keys.
Get Your Leads Flowing.
Set up your LeadCentre account, connect this source and see your next enquiry arrive on your phone.