Start free
AActionAircallUpdated June 2026

How do I fetch the details of a specific Aircall call?

Short answer: You can get call in Aircall by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Aircall Get Call action to a workflow, map its 1 input from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Use this actionAll 6 Aircall actions
Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

FieldTypeRequiredDescription
Call ID
callId
stringRequired12345
Sample request
{
  "callId": "12345"
}
Returns
{
  "call": {
    "id": 12345,
    "user": {
      "id": 7,
      "name": "Jane Doe"
    },
    "status": "done",
    "duration": 42,
    "direction": "inbound",
    "recording": "https://media.aircall.io/recordings/abc.mp3",
    "raw_digits": "+15551234567",
    "started_at": 1737000000
  }
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Get Call.

Any of these apps can fire this action as part of a workflow.

A
Gmail → Aircall
1 Gmail triggers
A
Slack → Aircall
13 Slack triggers
A
Google Sheets → Aircall
2 Google Sheets triggers
A
HubSpot → Aircall
18 HubSpot triggers
FAQ

Questions about Get Call.

What does the Get Call action do in Aircall?
Returns the full call record by ID — duration, direction, participants, recording URL, tags, notes. The standard lookup for workflows that received a call ID via webhook and need richer context for downstream processing.
What inputs does Get Call require?
Required: Call ID. Every input accepts a static value or a variable from any upstream node in your workflow.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if Aircall returns an error?
The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.
Does Get Call support batch operations?
Yes. Run Get Call inside a Loop node to process arrays. TinyCommand handles Aircall's rate limits automatically so you don't have to throttle manually.
More actions

Other Aircall actions.

Action
Create Contact
Adds a contact to Aircall's shared address book so the team sees the caller's name on inbound calls instead of just the phone number. Useful for "sync CRM contacts to Aircall on create" workflows that keep the contact-resolution UI accurate.
Action
List Calls
Paginated calls with filters by user, number, date range, direction, and tag. Useful for "this morning, summarise yesterday's missed calls for the team" digest workflows and for backfill workflows that catch calls missed during webhook downtime.
Action
List Users
Returns all Aircall agents/users in the account with name, email, and active status. The lookup for resolving user IDs in downstream notifications and for "show me today's on-shift agents" workflows.
Action
Log Call Note
Appends notes, tags, or disposition codes to a specific call after it ended. Useful for "AI-summarised post-call notes from a transcription service → log back to the Aircall call record" workflows that keep the call history annotated.
Action
Search Contacts
Search the shared address book by partial name, email, or phone number. Useful for resolving "is this caller already in our address book" lookups before adding from CRM.