Search Contacts: 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
Phone Number phoneNumber	string	Optional	+15551234567
Email email	string	Optional	—

Sample request

{
  "phoneNumber": "+15551234567",
  "email": "{{trigger.email}}"
}

Returns

{
  "meta": {
    "count": 1,
    "total": 1
  },
  "contacts": [
    {
      "id": 501,
      "last_name": "Doe",
      "first_name": "Jane",
      "company_name": "Acme Inc"
    }
  ]
}

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

FAQ

Questions about Search Contacts.

What does the Search Contacts action do in Aircall?

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.

What inputs does Search Contacts require?

Search Contacts 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 Search Contacts support batch operations?

Yes. Run Search Contacts 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