↔
Every Aircall call lands on the right HubSpot contact with its recording, notes and outcome
Calls happen in Aircall, deals live in HubSpot. Without a link the manager writes the result of the call into the CRM by hand, or does not, and the pipeline shows deals nobody has spoken to. We connect the two so each call is logged on the matching contact and deal, a missed call creates a task, and the manager can dial from the HubSpot card without switching windows.
Before after a call the manager should write a note in HubSpot, and in a busy hour half of the calls are not written down, so the deal history has gaps.
After every call is logged on the contact by itself with the recording and duration, and the manager only adds the conclusion.
Before a lead calls at lunch, nobody picks up, and the missed call stays in the phone list until someone remembers.
After the missed call becomes a HubSpot task for the contact owner with a due time, and it shows in their daily list.
Before the phone rings, the agent sees only a number and asks the customer to repeat who they are and what they wanted.
After the agent sees the name, company and deal stage from HubSpot before answering.
Before the head of sales counts calls in Aircall and deals in HubSpot and cannot tell how many calls a won deal takes.
After calls and outcomes live on the deal in HubSpot, so the report shows calls per stage and per manager.
For those who want to check: each point links to the official documentation page it comes from.
Aircall notifies an external system about call events as they happen — call started, answered, hung up, ended, voicemail left — and sends recording links in a separate event, since they may be missing when the call ends.
Source: developers.aircall.io ↗ checked 2026-09-29Each call carries its duration in seconds and, if recording is turned on for the number, a direct link to the mp3 recording — valid for only 1 hour (the short link for 3 hours), so the file has to be saved right away.
Source: developers.aircall.io ↗ checked 2026-09-29Aircall limits its public interface to 120 requests per minute, and that ceiling is shared across the whole company account, not split per key or per person.
Source: developer.aircall.io ↗ checked 2026-09-25A call is logged on a CRM record through the API: one request creates the call with its direction, duration in milliseconds, notes and a recording link (HTTPS .mp3 or .wav only) and associates it with the contact.
Source: developers.hubspot.com ↗ checked 2026-09-29Each logged call can carry an outcome from a fixed list, such as No answer or Wrong number, which HubSpot stores as a call property.
Source: developers.hubspot.com ↗ checked 2026-09-29Privately distributed apps on Free and Starter get 100 requests per 10 seconds per app and 250,000 per day, and the daily limit is shared by all apps in the account.
Source: developers.hubspot.com ↗ checked 2026-09-29The limits come from both systems. Aircall accepts 120 requests a minute for the whole company account, not per person or per key, so on a busy call floor logging is queued and written in batches rather than the same second. HubSpot on the Starter plan and below allows 100 requests per 10 seconds for an app and 250,000 a day for the account, which is plenty for calls but matters if other apps share the same account. HubSpot has its own built-in calling; the link makes sense when your team keeps its numbers and call routing in Aircall. Aircall's recording link works for only one hour, so right after the call the pair saves the recording and gives HubSpot a permanent HTTPS link.
Three steps from a first message to work on your project.
Describe the task in the form — in text or by voice. Budget and timing are optional.
A developer studies the brief, asks about anything unclear and sends an estimate.
Once scope and price are agreed, the work begins.
or write to info@coreviaflow.space
Describe the task in text or a voice message. We look at your setup and reply with a plan.
Four services people come to us for most often. Each page explains what we do, how the work goes and where to start.
Choose the system, set up the pipeline, migrate data, train the team.
Learn more →Accounting, telephony, website, payments and messengers feed the CRM on their own.
Learn more →Orders, requests and answers around the clock, straight into your CRM.
Learn more →Flows between CRM, email, spreadsheets, payments and AI, on your own server.
Learn more →IP telephonyEUCloud calling that plugs straight into the tools your sales and support team already use
See scenarios →CRMUSUS CRM with built-in calling and no-code automation, ready to plug into the tools you already run
See scenarios →↔
Every Aircall call becomes a Salesforce record with its duration, and the recording is saved before its link expires
See scenarios →↔
HubSpot contacts reach the right Mailchimp audience with tags that match their stage, and opens and clicks return to the contact card
See scenarios →↔
Calls and texts from RingCentral land on the right HubSpot contact, missed calls become tasks, and reps dial from the HubSpot record through their own RingCentral line
See scenarios →↔Marketing leads from HubSpot become leads and contacts in Salesforce, and deal stages, owners and closed sales from Salesforce come back to HubSpot for reporting and nurturing
See scenarios →Implementation · Development · Integrations →
Aircall ↔ HubSpot — the system names are trademarks of their owners. CoreviaFlow is not affiliated with them unless stated otherwise.
