LumaKol
Pabbly Connect

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
A smiling woman wearing a lanyard, working on a laptop in an office

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. 1

    Add Pabbly Connect as a lead source

    In LumaKol, go to Setup → Lead sources, choose Add source, then Pabbly Connect, and copy the webhook URL.

  2. 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. 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. 4

    Test and switch on

    Send a test request, turn the workflow on and choose who gets the leads. Other key names go under Field names with Edit.

What comes in with each record

  • Name (or first and last name), phone and email
  • Company, city, state, postal code and address
  • A campaign parameter, saved as the lead’s campaign
  • The notes or message parameter, as a note

After the lead arrives

A record whose phone number is already a lead becomes a note on that lead instead of a duplicate. Records without a valid phone number are listed under Activity as Not added, and a record sent with test set to true is logged as Test without creating a lead.

Plans

Included on Growth, Business and Enterprise, and in the free trial.

Compare plans

Questions

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.

What if the workflow runs twice for the same record?+

Send an id parameter and the record is added once. Without one, a repeat with the same phone number becomes a note on the existing lead.

Why was a record Not added?+

Usually because it had no valid phone number. The source’s Activity shows each record with the reason.

Related integrations

All integrations
Find LumaKol on

Look LumaKol up on the sites software buyers check

Independent directories. Each link opens LumaKol’s own page there.

Give your team a CRM that captures every call

Set up your workspace and start capturing calls the same day.

14-day free trial · No card needed · Cancel anytime