AActionAutopilotUpdated June 2026

How do I list Autopilot contacts?

Short answer: You can list contacts in Autopilot by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Autopilot List Contacts 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.

Inputs

The fields this action accepts.

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

FieldTypeRequiredDescription
Bookmark (pagination)
bookmark
stringOptionalBookmark (pagination)
Sample request
{
"bookmark": "{{trigger.bookmark}}"
}
Returns
{
"contacts": [
{
"email": "user@example.com",
"FirstName": "John",
"contact_id": "person_123"
}
],
"total_contacts": 100
}

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

Triggered by

Apps that pair well as the trigger for List Contacts.

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

FAQ

Questions about List Contacts.

What does the List Contacts action do in Autopilot?
Paginated contact list with filters by segment, journey, custom-field value. For sync workflows that mirror Autopilot into a warehouse, paginate with the recent-update filter to incrementally pull only touched records.
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 Autopilot 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. TinyCommand handles Autopilot's rate limits automatically so you don't have to throttle manually.
More actions

Other Autopilot actions.

Action
Get Contact
Returns the contact by ID or email with all standard and custom fields plus current journey participations. Useful for enrichment workflows that need a snapshot of Autopilot state before downstream decisions.