The recording nobody could open
Before a manager copies the recording link into Salesforce, and a day later the link no longer opens.
After the file is saved right after the call, and the Salesforce record keeps a link that keeps working.
Every Aircall call becomes a Salesforce record with its duration, and the recording is saved before its link expires
Sales teams that call from Aircall and keep clients in Salesforce usually lose the calls in between: the manager forgets to log the conversation, a new number never becomes a record, and the recording link found a day later no longer opens. The Aircall ↔ Salesforce pair logs every finished call on the right Salesforce record, creates a record for an unknown number, picks up the recording the moment Aircall reports it is ready, and sends phone numbers from Salesforce to Aircall so agents see who is calling. Below: what exactly moves, which scenarios we cover and which capabilities of both systems we rely on.
Before a manager copies the recording link into Salesforce, and a day later the link no longer opens.
After the file is saved right after the call, and the Salesforce record keeps a link that keeps working.
Before calls are logged only when the manager remembers, and reports undercount the work.
After every finished call is in Salesforce with its duration, and a new number becomes a record on its own.
Before a missed call stays in the Aircall history, and nobody calls back.
After the owner of the record gets a call-back task in Salesforce.
For those who want to check: each point links to the official documentation page it comes from.
The access key needed to connect is created once in the company's account settings, and its secret part is shown only at that moment — Aircall doesn't store it in a retrievable form afterward.
Source: developer.aircall.io ↗ checked 2026-09-25Aircall 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-25Aircall 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-29A contact can be created in Aircall through the API; a phone number is required, and a contact created this way is automatically shared across the whole company.
Source: developers.aircall.io ↗ checked 2026-09-29REST API gives programmatic access to Salesforce records, metadata and search without using the Salesforce interface itself.
Source: developer.salesforce.com ↗ checked 2026-09-25The limits come from both systems. The recording link from Aircall works for only one hour (its short version for three hours), so the pair downloads the file right after Aircall reports it is ready; a recording exists only for numbers where recording is switched on. Aircall allows 120 requests per minute for the whole company, so on busy days the pair queues its work instead of losing it. A contact is created in Aircall only with a phone number, and it becomes visible to the whole company. Calls are made in Aircall itself; the pair moves data and does not put a phone inside Salesforce.
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 →Cloud calling that plugs straight into the tools your sales and support team already use
See scenarios →Enterprise CRM with a live event feed and no-code automation across every record type
See scenarios →Every Aircall call lands on the right HubSpot contact with its recording, notes and outcome
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 →Important Salesforce changes arrive in the right Slack channel as they happen, and a button in the message updates the record back in Salesforce
See scenarios →Claude reads PDF attachments on Salesforce records, drafts notes and follow-up emails and sorts incoming leads, and nothing is written back until a person approves it
See scenarios →Implementation · Development · Integrations →
Aircall ↔ Salesforce — the system names are trademarks of their owners. CoreviaFlow is not affiliated with them unless stated otherwise.