Qualified Lead to Zoho CRM or Kylas

When an Edesy AI voice agent call ends QUALIFIED, update the lead in Kylas natively with a post-call workflow, or create or update the lead in Zoho CRM through n8n, Make or Zapier. Setup, field map, a qualification prompt and what each route can and can't do.

6 min readUpdated

When a call ends QUALIFIED, the lead in your CRM is updated straight away with status, budget, timeline and summary. Kylas works natively through a post-call workflow; Zoho CRM goes through n8n, Make or Zapier. There's no charge beyond the call at ₹6 a minute. The native Kylas step updates leads; it doesn't create them.

Works with: Kylas Native (CRM integration plus the CRM Update step; new Kylas leads can also trigger calls natively) · Zoho CRM via webhooks in n8n, Make or Zapier (call.analyzed plus their Zoho CRM actions) · any CRM via API

Note Native Zoho CRM write-back from the voice agent is planned (the connector exists but can't be connected from the dashboard yet). Request early access.

How it works#

Kylas (native)
  New lead in Kylas ──> automation rule "Lead Created" ──> AI call
                                                            │
  post-call workflow: Call Ended (outcome QUALIFIED) ──> CRM Update (Kylas lead _recordId)

Zoho CRM (via n8n / Make / Zapier)
  call.analyzed webhook ──> disposition == QUALIFIED? ──> Zoho CRM: search lead by phone
                                                       ──> update lead + add note

Before you start#

  • A voice agent that sets its outcome with the set_call_outcome tool, so QUALIFIED means what you decide. See dispositions.
  • An extraction template for the fields you want in the CRM (budget, timeline, product).
  • Kylas: a Kylas API key (Kylas Settings → Developer → API Keys).
  • Zoho CRM: an n8n, Make or Zapier account connected to Zoho CRM.

Set it up: Kylas (native)#

1. Connect Kylas#

  1. In the voice agent, go to CRM integrations (/crm/integrations) and click Add CRM Integration.
  2. Step 1: Select CRM Platform: Kylas. Enter an Integration Name (for example "Kylas Sales") and the API Key, then click Create Integration.

2. Call new Kylas leads (optional, native)#

  1. Open CRM automation rules (/crm/automation-rules) and click Create Automation Rule.
  2. Fill in Rule Name, CRM Integration (your Kylas integration), Trigger Event (Lead Created) and optional Filter Conditions, for example source = Website.
  3. Pick the Voice Agent, the Phone Number Field (the lead's phone) and, under Variable Mapping, map Kylas fields to agent variables such as customer_name and product_interest.
  4. Save. Each new lead gets a call; the Kylas lead ID travels with the call as the variable _recordId.

3. Write the result back#

  1. Open the agent, then Integrations → Post-Call Workflows → Add Workflow.
  2. Trigger: Call Ended, this agent, outcome Qualified. (Or Data Extracted plus a Condition step disposition == QUALIFIED if you need extracted fields.)
  3. Add a step from Integrations: CRM Update.
    • CRM Integration: your Kylas integration.
    • Record ID Field: _recordId for calls started by the automation rule. For calls you place through the API, pass the Kylas lead ID yourself in variables (the default field name is crm_record_id).
    • Field Updates (JSON): the Kylas fields to set, using your Kylas field API names, for example:
{
  "status": "Qualified by AI call",
  "cfBudget": "{{budget_range}}",
  "cfTimeline": "{{purchase_timeline}}",
  "cfCallSummary": "{{callSummary}}"
}
  1. Save as Draft, test, then set Active.

To create a lead in Kylas for someone who isn't in Kylas yet (for example a missed-call lead), use n8n or Make with Kylas's API, or Edesy Flow's Kylas Find or Create Lead by Phone action (Flow's webhook trigger is set up for you on request).

Set it up: Zoho CRM (n8n)#

  1. In n8n, add a Webhook node and copy the Production URL.
  2. In the voice agent, Settings → Webhooks → Add Webhook: paste the URL as Endpoint URL, choose the agent under Filter by Agent (or all agents), tick call.analyzed, and click Create Webhook. Save the secret.
  3. Verify the signature in a Code node (X-Webhook-Signature: t=...,v1=..., HMAC-SHA256 of <t>.<raw body>). See Webhook subscriptions.
  4. Add an IF node: {{ $json.body.data.disposition.toUpperCase() }} equals QUALIFIED. Normalise the case before comparing.
  5. Add the Zoho CRM node: Lead → Get Many (or search) by phone {{ $json.body.data.recipient_phone }}. If you passed a Zoho lead ID in variables, use data.variables.zoho_lead_id instead.
  6. Add Zoho CRM → Lead → Update with Lead_Status = Qualified, your custom fields from data.extracted_data, and Description or a note with data.call_summary and data.recording_url. If no lead was found, use Lead → Create (Zoho requires Last_Name, and Company in many setups).
  7. Activate.

Make: Webhooks → Custom webhook, a filter on disposition, then Zoho CRM → Search Records and Update a Record. Zapier: Webhooks by Zapier → Catch Hook, Filter, then Zoho CRM → Find Lead and Update Lead. The Edesy Zapier app isn't published yet.

Data map#

call.analyzed field Kylas (CRM Update variable) Zoho CRM field (example)
disposition = QUALIFIED trigger filter Lead_Status = Qualified
call_summary {{callSummary}} Description or a Note
extracted_data.budget_range {{budget_range}} custom field Budget
extracted_data.purchase_timeline {{purchase_timeline}} custom field Timeline
recipient_phone {{recipientPhone}} search key Mobile / Phone
variables (_recordId, zoho_lead_id) Record ID Field lead ID to update
recording_url, conversation_id {{callRecordingUrl}}, {{conversationId}} note text

Sample agent prompt#

You are Nikhil from SolarKart, a rooftop solar installer in Ahmedabad. You are calling
{{customer_name}}, who enquired about rooftop solar for their home.

Speak Gujarati-accented Hinglish; switch to Gujarati, Hindi or English if they prefer.
Find out:
1. Own house or rented? (Rented means not eligible; politely end.)
2. Average monthly electricity bill in rupees.
3. Roof type and roughly how much free roof space.
4. When they want it installed: this month, in 3 months, or just exploring.
Explain the PM Surya Ghar subsidy only in one line; don't quote exact subsidy amounts.
Call set_call_outcome with QUALIFIED if they own the house, the bill is above ₹2,000 and
they want it within 3 months; NO_DECISION if just exploring; NOT_INTERESTED if they
decline; DO_NOT_CALL if they ask not to be called.

Test it#

  1. Kylas: create a test lead in Kylas with your number (the automation rule calls you), or place a test call through the API with "variables": {"crm_record_id": "<lead id>"}.
  2. Answer as a qualified buyer. After the call, open the lead in Kylas: the fields from Field Updates are set.
  3. Zoho: place a call to a number that exists as a Zoho lead, qualify, and check the n8n run and the lead.
  4. Check the workflow's execution history (Kylas) or n8n executions (Zoho) for any failed step.
  • Call leads who enquired or opted in; CRM import lists without consent are not a basis to call.
  • Edesy does not scrub against the NCPR (DND) registry.
  • Set Settings → Call Settings → Calling Window (for example 9:00–21:00 IST); automation-rule calls outside it are held until it opens.
  • Write DO_NOT_CALL back to the CRM (for example a "Do not call" field) and add the number to Settings → Blocked Numbers.

What it can't do yet#

  • The native CRM Update step updates an existing Kylas record; it doesn't create leads, and the dashboard step doesn't add notes or log activities.
  • Zoho CRM can't be connected natively from the dashboard yet, so Zoho goes through n8n, Make or Zapier.
  • HubSpot, Salesforce, Pipedrive and LeadSquared have no native voice agent connector; use the same webhook pattern as Zoho. Bitrix24 is also available as a native CRM integration.
  • Input variables such as _recordId are echoed into post-call workflows on a best-effort basis; if a run can't find the record ID, the step fails and can be retried from the execution history.

FAQ#

What counts as "qualified"? Whatever your prompt says. The agent calls set_call_outcome with QUALIFIED when your rules are met, so write the rules in the prompt.

Can non-qualified calls update the CRM too? Yes. Add workflows for other outcomes, for example NOT_INTERESTED to mark the lead lost, or CALLBACK_REQUESTED to set a follow-up date.

Does this create duplicate leads in Zoho? Not if you search by phone (or by the Zoho lead ID you passed in variables) before creating.

Is there a cost for the CRM update? No. You pay for the call minutes only.

Can the agent look up the lead in the CRM during the call? For Kylas, Zoho and others, the agent can call any CRM API during the call through a custom HTTP function. See function calling.

Start free · Book a demo · Don't see your app? Request it

Was this page helpful?