ActionAircallUpdated September 2026

How do I list recent Aircall calls?

Short answer: You can list calls in Aircall by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Aircall List Calls action to a workflow, map its 3 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

List Calls in Aircall — start free All 6 Aircall actions

List Calls in Aircall — start free

Inputs

The fields this action accepts.

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

Field	Type	Required	Description
Direction direction	options	Optional	–
From Unix Timestamp from	number	Optional	Return calls started after this UNIX timestamp.
Per Page perPage	number	Optional	Max 50.

Sample request

{
  "direction": "{{trigger.direction}}",
  "from": "{{trigger.from}}",
  "perPage": "{{trigger.perPage}}"
}

Returns

{
  "meta": {
    "count": 1,
    "total": 1
  },
  "calls": [
    {
      "id": 12345,
      "status": "done",
      "duration": 42,
      "direction": "inbound",
      "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 List Calls.

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

Google Sheets → Aircall

2 Google Sheets triggers

HubSpot → Aircall

18 HubSpot triggers

FAQ

Questions about List Calls.

What does the List Calls action do in Aircall?

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.

What inputs does List Calls require?

List Calls has no required inputs. Sensible defaults are applied if you leave fields blank.

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 run history shows the failed step with its input and the error message Aircall returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does List Calls support batch operations?

Run List Calls inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Aircall's rate limits.

More actions