Connect with a HubSpot private app token. Leadialer finds the contact by phone number (or creates it), then logs a timeline note for every completed call, booking, warm-lead flag, and opt-out — so your team sees Alex's work exactly where they already live.
Your acquisitions team lives on the HubSpot contact timeline, so that's where Leadialer's AI dialer reports. After each conversation, Alex's result — the outcome, the lead score, and a written summary of what the seller said — appears as a timestamped note on the contact, right alongside your emails and tasks. Bookings, warm-lead flags, and STOP opt-outs land the same way.
Matching is done by phone number: Leadialer searches your HubSpot contacts for the lead's number and attaches the note there, or creates the contact (first name, last name, phone) if it's new. Setup is one private app token — no OAuth dance, no middleware, no per-seat cost on the Leadialer side.
call.completedTimeline note with the call outcome, lead score, and the AI's conversation summary.
appointment.bookedTimeline note with the appointment date and time in your timezone, flagged if it was a reschedule.
lead.warmTimeline note with the lead score and the channel that warmed the lead up.
lead.opted_outTimeline note recording the STOP request so your sequences can be stopped too.
By exact phone number match. If no contact has that number, Leadialer creates one with the lead's first name, last name, and phone, then attaches the note to it.
Just crm.objects.contacts read and write. Leadialer doesn't touch deals, tickets, or any other object.
No — it writes contacts and timeline notes only. Use HubSpot workflows on contact activity if you want downstream automation.
No. Pushes are best-effort and asynchronous — the dialer never waits on HubSpot.