List Contacts: ActiveCampaign 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
Filter by Email email	string	Optional	Filter by Email. e.g. "user@example.com"
Limit limit	string	Optional	Limit. e.g. "20"
Offset offset	string	Optional	Offset. e.g. "0"

Sample request

{
  "email": "user@example.com",
  "limit": "20",
  "offset": "0"
}

Returns

{
  "meta": {
    "total": "42"
  },
  "contacts": [
    {
      "id": "123",
      "email": "user@example.com",
      "firstName": "John"
    }
  ]
}

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

FAQ

Questions about List Contacts.

What does the List Contacts action do in ActiveCampaign?

Paginated contact retrieval with filters for email, list membership, tag, status, and recently-modified time. For bulk-sync workflows that mirror AC into a warehouse or another CRM, use the timestamp filter to incrementally pull only the contacts touched since the last sync.

What inputs does List Contacts require?

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

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

More actions