Pabbly Connect workflows that end in a phone call
Add an API request step to your Pabbly Connect workflow that posts to the URL LumaKol gives you. Each new record from your trigger app becomes a lead with the caller you choose.
- Any Pabbly trigger app
- JSON with your own keys
- Field names mapped once
Pabbly Connect at a glance
- How leads get in
- An API (Pabbly) → Execute API Request action posts each record from your workflow to the private URL on your LumaKol source.
- How fast
- As soon as the workflow reaches that step, which is right after its trigger fires.
- Repeats and retries
- A parameter called id, lead_id, enquiry_id or submission_id carrying the record’s own ID means a workflow that runs again adds the lead once.
- Where you set it up
- Pabbly Connect → your workflow → action API (Pabbly) → Execute API Request, method POST, payload type JSON.
Who it’s for
Small businesses, agencies and course sellers who already automate with Pabbly Connect: payment gateways, webinar tools, form builders, email tools, chatbots and spreadsheets. Add one step and the record that started the workflow becomes a lead in LumaKol.
- Use the parameters name, phone, email, company, city and notes, or map your own names under Field names.
- Point several workflows at one source, or give each its own source and caller.
- Send an id with each record so a workflow that re-runs does not add the lead twice.
How to connect it
- 1
Add Pabbly Connect as a lead source
In LumaKol, go to Integrations → Lead sources, choose Add source, then Pabbly Connect, and copy the webhook URL.
- 2
Add the API request action
In Pabbly Connect, create a workflow with your app as the trigger, then add the action API (Pabbly) → Execute API Request, method POST, payload type JSON.
- 3
Map the parameters
Paste the URL as the API endpoint URL and add the parameters name, phone, email, company, city and notes mapped to your trigger’s fields.
- 4
Send a test request, then turn it on
Send the step’s test request and check the source’s Activity in LumaKol. The test uses your trigger’s sample data, so a sample without a phone number shows as Not added. Turn the workflow on once a record arrives as New lead.
Which Pabbly parameters become lead fields
| What Pabbly Connect sends | Where it lands in LumaKol |
|---|---|
| name, full_name, customer_name or contact_name; or first_name with last_name | Name |
| phone, mobile, phone_number, whatsapp or contact_number | Phone |
| email or email_address | |
| company or company_name | Company |
| city, state, pincode or zip, and address | City, state, postal code and address |
| campaign or utm_campaign | Campaign |
| notes, message, requirement or enquiry | The lead’s first note |
| Facebook Lead Ads answers sent under their own names full_name, phone_number and email | Name, phone and email, with no Field names needed |
Parameter names are not case-sensitive. A name you enter under Field names on the source is used instead of the usual ones for that field. Parameters that match no field are dropped.
After the lead arrives
The person you picked gets a push that names the lead and your Pabbly Connect source, and the lead’s timeline records where it came from. One workflow can feed several apps into the same source, so name the source after the workflow. For anything routing alone cannot do, an automation rule on Lead source is Pabbly Connect can tag, assign or follow up the lead.
Common Pabbly Connect problems, and the fix
The test request shows Not added
Either the trigger’s sample record had no phone number, or the phone went out under a parameter name LumaKol does not know. Map a real phone value to a parameter called phone and send the test again.
A Field name stopped the usual names working
Once you enter a Field name for phone, LumaKol looks only for that parameter. If the workflow sends the number under another name, the lead is Not added. Clear the Field name, or send the parameter it names.
Values from the trigger go missing
LumaKol reads parameters at the top level, and inside one wrapping object. Values two levels deep, or inside lists, are ignored, so map each value you need to a top-level parameter of its own.
Too many requests while replaying old records
Each source accepts up to 120 deliveries a minute and answers “too many requests” beyond that. When sending a backlog through the workflow, spread the records over several minutes.
Questions about Pabbly Connect
Which Pabbly Connect action do I use?+
API (Pabbly) → Execute API Request, with method POST and payload type JSON, and the LumaKol URL as the API endpoint URL.
Do I have to use your parameter names?+
No. Use name, phone, email, company, city and notes, or keep your own names and enter them under Field names on the source.
Can Pabbly Connect pass on Facebook and Instagram lead ads?+
Yes. Start the workflow with the Facebook Lead Ads trigger for your Page and form, then send each lead to your LumaKol source with Execute API Request. Instagram lead ads come through the Page their Instagram account is linked to. LumaKol itself does not connect to Facebook.
What if the workflow runs twice for the same record?+
Send an id parameter with the record’s own ID and it is added once. Without one, an identical request is still recognised, and a changed request with a number that is already a lead becomes a note on that lead.