टीम व्यवस्थापित करा

Connect LumaKol to Zapier

Add LumaKol’s Zapier app with an API key, start Zaps from new leads, stage moves and call outcomes, and create, find or update leads from your other apps.

8 मिनिटेवेबमालक / अॅडमिनअपडेट: २ नोव्हेंबर, २०२६

सुरू करण्यापूर्वी

Owner or admin access: API & webhooks is under Integrations, which only people who can change settings see
A workspace on a paid plan: API keys cannot be created or used during the free trial
A Zapier account. Zapier’s free plan is enough for two-step Zaps

Hands typing on a silver laptop at a desk, a coffee mug and a second screen behind them

1
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
टीप: Made the key without calls:read or users:read? Open it with Edit and tick them. The key itself does not change, so nothing in Zapier needs re-entering.
2
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.
3
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.
4
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.
5
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.
6
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.
टीप: Your reference takes an ID from your own system. Create Lead never adds a second lead with the same reference, so it is a good field to match on in a sync.
7
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.

शेवटी तुमच्याकडे काय असेल

LumaKol connected to Zapier with a key that carries only what Zapier needs
Zaps that start the moment a lead arrives, moves stage or gets a call outcome
Leads created, found and updated from the other apps you use, without duplicates

सामान्य प्रश्न

Do I need a paid Zapier plan?+

Not for two-step Zaps: a LumaKol trigger with one action, or another app’s trigger with one LumaKol action, runs on Zapier’s free plan within its monthly task limit. A Zap with Find Lead and another step, or any Zap with more than two steps, needs a paid Zapier plan.

Zapier says the key is missing a permission. What do I change?+

The key lacks a permission that step needs, most often calls:read for New Call Outcome or users:read for the Assign to list. Open the key with Edit under Integrations → API & webhooks, tick the permission and save, then test the step again. The key stays the same.

Zapier says the API is available once the workspace is on a paid plan.+

API keys are created and used on paid plans only, so a workspace in its free trial cannot connect Zapier yet. Once a plan is active, create the key and connect as above.

Why did Create Lead fail for someone who is already a lead?+

Create Lead refuses a phone number that is already a lead, on purpose. Put Find Lead before it and update the lead it finds, or send Your reference with an ID from your own system.

How do I stop a Zap, or all of them?+

Turn a Zap off in Zapier and LumaKol stops sending its events. Revoke the key under Integrations → API & webhooks and every Zap that uses it stops at once; issue a new key and reconnect when you need them again.