Make scenarios that put leads in front of callers
Add an HTTP → Make a request module to your scenario, posting JSON to the URL LumaKol gives you. Each new record from the scenario becomes a lead in the queue of the caller you choose.
- Any Make trigger module
- Raw JSON request
- Field names mapped once
Make at a glance
- How leads get in
- The HTTP → Make a request module posts each bundle to the private URL on your LumaKol source, as JSON or as form fields.
- How fast
- As soon as the scenario reaches the HTTP module, so it follows however the scenario is scheduled or triggered.
- Repeats and retries
- Include the record’s own ID as id and a scenario that processes the same bundle again adds the lead once.
- Where you set it up
- Make → your scenario → add the module HTTP → Make a request, method POST.
Who it’s for
Operations and growth teams that run their lead flow in Make (formerly Integromat): enriching leads, filtering by country or budget, routing by product, then handing the qualified ones to sales callers. LumaKol is the last module, and the lead lands in a calling queue.
- Filter and enrich in Make first, then send only the leads worth a call.
- Use the keys name, phone, email, company, city and notes, or your own names mapped under Field names.
- Include an id key so a scenario that runs again does not add the lead twice.
How to connect it
- 1
Add Make as a lead source
In LumaKol, go to Integrations → Lead sources, choose Add source, then Make, and copy the webhook URL.
- 2
Add the HTTP module
Create a scenario with your app as the first module, then add HTTP → Make a request: the URL, method POST, body type Raw and content type JSON (application/json).
- 3
Build the request body
In Request content, write JSON with the keys name, phone, email, company, city and notes mapped from earlier modules. Or choose body type application/x-www-form-urlencoded and add the same keys as fields.
- 4
Run once, read Activity, switch on
Run the scenario once and open the source’s Activity in LumaKol to see what the bundle became: New lead, Repeat, Not added with a reason, or Test. Then switch the scenario on.
Which keys in the request LumaKol reads
| What Make sends | Where it lands in LumaKol |
|---|---|
| name, full_name, fullname, customer_name, contact_name or lead_name; or first_name with last_name | Name |
| phone, mobile, phone_number, mobile_number, contact, contact_number, whatsapp or tel | Phone |
| email, email_address or mail | |
| message, notes, comments, requirement, enquiry or description | The lead’s first note |
| Any of these keys inside one wrapping object, such as data | Read as if they were at the top level |
| Keys two levels deep, and lists | Ignored |
| id, lead_id, leadid, enquiry_id or submission_id | Kept so the same record is added once |
| test set to true | Logged as Test, no lead |
Company, city, state, postal code, address and campaign keys are read too. Keys are not case-sensitive; a key you set under Field names replaces the usual names for that field, and keys that match nothing are left out.
After the lead arrives
Each lead lands in the queue of the person you picked, with a push naming the lead and the source. If one scenario serves several brands or clients, give each its own Make source and URL: each then has its own callers, stage and tags, and its own list on the Leads page. A rule on A new lead is not called in time can pass on any lead nobody rings.
Common Make problems, and the fix
A message with quotes breaks the request
A mapped value that contains a quote or a line break can make hand-written Raw JSON invalid, and LumaKol then gets nothing it can read: the first such request shows as Not added and later ones look like repeats of it. Build the body with JSON → Create JSON and map its output, or send form fields instead.
The HTTP module returns 413 or 429
413 means the request was larger than 64 KB, so send only the fields a caller needs. 429 means more than 120 deliveries reached the source in one minute; slow the scenario down when it works through a backlog.
The name arrives but the phone doesn’t
The phone is probably nested two levels deep or inside a list in the bundle. Map the single value into a top-level key called phone, rather than passing the whole object through.
Only the first bundle became a lead
An id that is the same in every bundle, such as a scenario or form ID, makes later bundles look like repeats. Map each record’s own ID to id, or leave the key out.
Questions about Make
Is Make the same as Integromat?+
Yes. Integromat was renamed Make; the HTTP → Make a request module is the one to use.
Do I have to send JSON?+
No. LumaKol also reads application/x-www-form-urlencoded and multipart form data, so you can add the keys as fields in the HTTP module instead of writing JSON by hand.
How do I test without creating a lead?+
Add "test": true to the JSON. The record shows under the source’s Activity as Test and no lead is created.
Step-by-step setup guide
Related integrations
All integrations- ZapierLumaKol’s own Zapier app: new leads, stage moves and call outcomes out, leads and notes in.Set up guide
- Pabbly ConnectLeads from any app in a Pabbly Connect workflow, sent with an API request step.Set up guide
- API 和 WebhookScoped API keys for your software, and signed webhooks for every key event.Set up guide