Connect LumaKol to Zapier

Create a key for Zapier

Integrations → API & webhooks → Create key. Name it Zapier, so the key list and the security log say which tool uses it, and tick the five permissions below. The key starts with lk_live_ and is shown once, so copy it before you close the dialog.

• leads:read: New Lead, Lead Moved Stage, Find Lead and the Stage list
• leads:write: Create Lead, Update Lead and Add Note to Lead
• calls:read: New Call Outcome
• users:read: the Assign to list of your callers
• webhooks:manage: lets Zapier switch your LumaKol triggers on and off

Add LumaKol to your Zapier account

Open the Zapier integration page on lumakol.com and choose Add LumaKol in Zapier. Zapier shows an invitation to LumaKol’s app: accept it while signed in to the Zapier account that will own your Zaps. After that, LumaKol appears when you search for it in the Zap editor.

Connect your workspace

In a Zap, pick LumaKol as the app, choose an event and then Sign in. Paste the key into API key and leave LumaKol address as it is. Zapier checks the key at once and names the connection after your workspace, so a team with more than one workspace can tell the connections apart.

Start a Zap from LumaKol

Pick one of the three triggers. LumaKol sends each event to Zapier the moment it happens, so a Zap does not wait for a polling interval. Test trigger loads up to three recent records so you can map their fields in the next steps.

• New Lead: a lead added by hand, from a lead source or web form, through the app or the API, or by a Google Sheets or CRM sync. Leads from a file import (CSV or Excel) do not start it.
• Lead Moved Stage: a lead moves to another pipeline stage, such as Booked, Won or Lost, by hand, through a call outcome or by an automation rule. The record carries the lead with its new stage.
• New Call Outcome: a caller logs the result of a call, on the phone or on the web. The record carries the lead plus the outcome, whether the call connected, its length in seconds, the note and the next follow-up.

Send leads and updates into LumaKol

For the other direction, pick LumaKol as the app of an action step.

• Create Lead: Name and Phone number are required, and a number without a country code is read in your workspace’s country. A number that is already a lead is refused, so a Zap that runs twice adds the person once. Leave Assign to empty and your assignment rules pick the caller.
• Update Lead: changes only the fields you fill in. It needs the Lead ID from an earlier step, such as a LumaKol trigger or Find Lead.
• Add Note to Lead: writes a note on the lead’s timeline, where the caller reads it before the next call.
• Find Lead: looks a lead up by phone number, email or Your reference. A phone number also matches a lead’s additional numbers.

Find first, then create or update

To keep another tool in step without duplicates, search before you write: Find Lead by phone or Your reference, then Update Lead with the Lead ID it returns. Zapier counts a Zap with a search and another step as a multi-step Zap, which needs a paid Zapier plan, and it does not publish a Zap whose last step is a search.

Test, publish and check the runs

Test each step in the editor, then publish the Zap. Zapier’s Zap history lists every run with what LumaKol received and returned. In LumaKol, the lead’s timeline shows what a Zap added, and Integrations → API & webhooks shows when the Zapier key was last used.