Zapier automations for a calling team: six Zaps worth building

A calling team works from its queue: who to call next, and what was said last time. The rest of the business keeps its records somewhere else, in a booking tool, the spreadsheet the owner reads on Sunday, the chat channel where wins get cheered or the system the accounts team uses, and a lot of office time goes into copying from one to the other.

LumaKol’s Zapier app connects the queue to the rest without code. It has three triggers (New Lead, Lead Moved Stage and New Call Outcome), three actions (Create Lead, Update Lead and Add Note to Lead) and a search (Find Lead). Each of the six Zaps below uses only those pieces. Setup, from the API key to the first published Zap, is in the step-by-step guide.

The API key Zapier needs

Every Zap connects through an API key created under Integrations → API & webhooks, which works on every paid LumaKol plan. Give Zapier its own key, named Zapier, with leads:read, leads:write, calls:read, users:read and webhooks:manage. The ones most often left out are calls:read, which New Call Outcome needs to load its test records, and users:read, which fills the Assign to list.

1. A booking or chat becomes a lead in a caller’s queue

Trigger: a new booking, chatbot conversation or webinar registration in any tool Zapier connects. Action: LumaKol Create Lead. Map the person’s name and phone to Name and Phone number, and put the tool’s name in Source so reports show which channel produced the calls. Leave Assign to empty and LumaKol’s assignment rules pick the caller.

Check Integrations → Lead sources first. Google Forms, Typeform, Jotform, IndiaMART, Google Ads lead forms and many more connect to LumaKol directly, with no Zapier step to pay for or maintain. Use Zapier for the tools that have none.

2. Facebook lead ads straight to a caller’s phone

Trigger: Facebook Lead Ads, New Lead. Action: Create Lead, mapping the form’s full name, phone number and email. LumaKol does not connect to Facebook directly, so a Zap like this is the route for Facebook and Instagram lead forms. Because Create Lead refuses a phone number that is already a lead, someone who fills in the form twice is still called once.

3. Every call result in the owner’s spreadsheet

Trigger: LumaKol New Call Outcome. Action: Google Sheets, Create Spreadsheet Row. Map the lead’s name, phone and assigned agent, then the outcome, whether the call connected, its length in seconds and the note. The owner gets a running log of every result without a LumaKol login, and the sheet can feed whatever chart they like.

If the leads already come from a Google Sheet synced to LumaKol, the sync itself can write outcomes back into that sheet’s empty columns, with no Zap needed. See the Google Sheets guide.

4. A message in the team channel for every win

Trigger: Lead Moved Stage. Add a Filter by Zapier step so the Zap carries on only when Stage is your won stage, then Slack, Send Channel Message with the lead’s name, the assigned agent and the last outcome. Lead Moved Stage fires for every move, whether by hand, through a call outcome or by an automation rule, so without the filter the channel would get a message each time. Zapier counts the filter as a step, so check that your Zapier plan allows Zaps with more than two steps.

5. Keep another system in step: find first, then update

Trigger: a record changes in the other system, such as a deal updated in your accounts or booking tool. Steps: LumaKol Find Lead by phone number or Your reference, then Update Lead with the Lead ID it returns, changing the stage, the assigned caller, the follow-up or the tags. Because the Zap searches before it writes, the two systems stay matched and nobody gets added twice.

Your reference takes an ID from your own system, and Create Lead never adds a second lead with the same one, so it is a good field to match on in a sync. For HubSpot, Pipedrive and Zoho CRM, LumaKol has a direct two-way sync that needs no Zap.

6. Context on the lead before the next call

Trigger: something the caller should know, such as a reply to a quote email or a new support ticket from the same customer. Steps: Find Lead by email or phone, then Add Note to Lead. The note lands on the lead’s timeline, so the caller has read it before dialling.

Which of these run on Zapier’s free plan

Zapier’s free plan runs two-step Zaps within a monthly task limit. Zaps with more steps need a paid Zapier plan, and Zapier will not publish a Zap whose last step is a search. Zapier also marks some apps as premium, which need a paid plan whatever the number of steps; its app directory shows which. On LumaKol’s side, every Zap here uses the same API key.

Three things that trip people up

• A key without calls:read or users:read. Zapier reports a missing permission. Open the key with Edit under Integrations → API & webhooks, tick the permission and test again: the key itself does not change.
• Create Lead on someone who is already a lead. The number is refused on purpose. Search first, or send Your reference with an ID from your own system.
• Expecting a file import to start New Lead. Leads from a CSV or Excel import do not start the trigger, so a large upload does not run a Zap for every row.

Start with the one Zap that removes a copy-and-paste job somebody does every day, then add the rest as the team asks for them. The Zapier integration page has the button that adds LumaKol to your Zapier account.