List Calls: Aircall action

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.

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 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 List Calls support batch operations?

Yes. Run List Calls inside a Loop node to process arrays. Tiny Command handles Aircall's rate limits automatically so you don't have to throttle manually.

More actions