Can a Voice Bot Update HubSpot Lead Status Live?

Can a voice bot integrate with HubSpot to log call outcomes and update lead status in real time?

Yes. A voice bot can log every call in HubSpot as a Call activity on the contact (outcome, summary, duration and recording) and update the contact's Lead Status automatically. With an end-of-call webhook this lands within seconds of hangup. If you need it while the caller is still on the line, for example to flag a hot lead before transfer, the agent can write to HubSpot mid-call through a custom tool.

What separates a working setup from a messy CRM is three decisions: how the call is matched to the contact, how bot outcomes map to HubSpot values, and when the write happens. This guide covers all three, with the payloads and code.

The short version

"Real time" for a CRM usually means before a rep looks at the record. The end-of-call webhook meets that bar for almost every team. Use the mid-call route only where an action depends on the update happening during the conversation.

Step 1: Match the call to the right HubSpot contact

The most common failure is writing the outcome to the wrong record, or to none. Avoid it by sending the HubSpot contact ID with the call, instead of searching by phone number afterwards.

When you place an outbound call through the Calls API, pass the ID as a variable:

curl -X POST https://voice-agent.edesy.in/api/v1/calls \
  -H "Authorization: Bearer $EDESY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "agentId": 1042,
    "phoneNumber": "+14155550142",
    "variables": {
      "first_name": "Dana",
      "hubspot_contact_id": "104901"
    },
    "callbackUrl": "https://your-app.com/hooks/voice/call-ended"
  }'

variables is echoed back in the end-of-call payload, so your handler knows exactly which contact to update. The same variables can be used in the agent's script, so the bot can greet the lead by name.

If the call is triggered by HubSpot itself (a new lead fills a form and gets called within a minute), see auto-calling new HubSpot leads with n8n. The contact ID is already in the trigger data there.

Inbound calls have no ID up front. Search HubSpot by the caller's number (POST /crm/v3/objects/contacts/search with a phone filter), and create the contact if nothing matches.

Step 2: Map bot outcomes to HubSpot values

HubSpot stores two different things, and a voice bot should set both:

• Call disposition (hs_call_disposition): what happened on this call. It is set with an internal GUID, not a label.
• Lead Status (hs_lead_status): where the lead now stands in your sales process.

HubSpot's default call dispositions and their GUIDs, from HubSpot's calls API guide:

A practical mapping from voice-bot outcomes to both fields:

Lead Status options can be customised per portal, so check the internal values under Settings → Properties → Lead Status before relying on the defaults above.

To get the finer outcomes (interested vs not now vs not a fit), set up post-call data extraction with a field like lead_outcome that only accepts a fixed list of values. A fixed list maps cleanly to a table like this one; free text does not.

Step 3: Receive the end-of-call webhook and write to HubSpot

Edesy gives you two ways to be told a call has ended:

The per-call callback payload looks like this (snake_case, disposition lowercased):

{
  "event": "call.completed",
  "timestamp": "2026-10-16T09:32:16Z",
  "data": {
    "conversation_id": "c3f1b6e2-8f5a-4a1e-9d21-7f0a2c4b9e11",
    "phone_number": "+14155550142",
    "duration": 74,
    "disposition": "qualified",
    "transcript_summary": "Dana runs a 12-person agency, wants a demo next Tuesday.",
    "recording_url": "https://…",
    "variables": { "first_name": "Dana", "hubspot_contact_id": "104901" }
  }
}

A minimal handler that logs the call and updates Lead Status (Node.js, using a HubSpot private app token):

const HS = "https://api.hubapi.com";
const hs = (method, path, body) =>
  fetch(HS + path, {
    method,
    headers: {
      Authorization: `Bearer ${process.env.HUBSPOT_TOKEN}`,
      "Content-Type": "application/json",
    },
    body: body && JSON.stringify(body),
  }).then((r) => r.json());

const DISPOSITION = {
  connected: "f240bbac-87c9-4f6e-bf70-924b57d47db7",
  no_answer: "73a0d17f-1163-4015-bdd5-ec830791da20",
  voicemail: "b2cf5968-551e-4856-9783-52b3da59a7d0",
};

// Only move leads forward from these; never overwrite a rep's decision.
const SAFE_TO_OVERWRITE = new Set(["", "NEW", "OPEN", "ATTEMPTED_TO_CONTACT"]);

app.post("/hooks/voice/call-ended", async (req, res) => {
  res.sendStatus(200); // acknowledge fast, then do the work
  const { event, timestamp, data } = req.body;
  const contactId = data.variables?.hubspot_contact_id;
  if (!contactId) return;

  const reached = event === "call.completed";
  const outcome = event === "call.voicemail" ? "voicemail" : reached ? "connected" : "no_answer";

  // 1. Log the call on the contact timeline
  await hs("POST", "/crm/v3/objects/calls", {
    properties: {
      hs_timestamp: timestamp,
      hs_call_title: "AI voice agent call",
      hs_call_body: data.transcript_summary ?? "",
      hs_call_duration: String((data.duration ?? 0) * 1000), // HubSpot wants milliseconds
      hs_call_direction: "OUTBOUND",
      hs_call_status: reached ? "COMPLETED" : "NO_ANSWER",
      hs_call_disposition: DISPOSITION[outcome],
      hs_call_to_number: data.phone_number,
      hs_call_recording_url: data.recording_url, // must be HTTPS
    },
    associations: [{
      to: { id: contactId },
      types: [{ associationCategory: "HUBSPOT_DEFINED", associationTypeId: 194 }], // call → contact
    }],
  });

  // 2. Update Lead Status, but only if no rep has moved it on
  const contact = await hs("GET", `/crm/v3/objects/contacts/${contactId}?properties=hs_lead_status`);
  const current = contact.properties?.hs_lead_status ?? "";
  if (!SAFE_TO_OVERWRITE.has(current)) return;

  const next =
    data.disposition === "qualified" ? "OPEN_DEAL" : reached ? "CONNECTED" : "ATTEMPTED_TO_CONTACT";
  await hs("PATCH", `/crm/v3/objects/contacts/${contactId}`, {
    properties: { hs_lead_status: next },
  });
});

The private app needs crm.objects.contacts.read and crm.objects.contacts.write, the scopes HubSpot documents for its calls API. Create it under Settings → Integrations → Private Apps.

For production, switch to a webhook subscription. The per-call callback is delivered once with no retry, so if your endpoint is down for a minute those outcomes are lost. Subscriptions are signed and retried. Verify the signature, and use the event id as an idempotency key so a retry never logs the same call twice. The webhook subscriptions docs have verification code in several languages.

Writing the extracted answers too

call.ended tells you the call happened. call.analyzed fires after post-call analysis and carries the summary and extracted fields, such as lead_outcome, budget, timeline, callback_time and objection. Map each to a HubSpot contact property (create custom properties for the ones HubSpot lacks) and write them in one PATCH. That is how the CRM ends up holding what the lead actually said, not just "call completed".

No-code alternative

Point the webhook at an n8n Webhook node, a Make custom webhook or a Zapier catch hook, then add two HubSpot steps: create engagement (call) and update contact. The mapping table above still applies. Our Google Sheets guide shows the same pattern with a sheet as the destination.