Start free
AActionAutopilotUpdated June 2026

How do I fetch an Autopilot contact?

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

Use this actionAll 2 Autopilot actions
Inputs

The fields this action accepts.

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

FieldTypeRequiredDescription
Contact ID or Email
contactId
stringRequiredContact ID or Email
Sample request
{
  "contactId": "{{trigger.contactId}}"
}
Returns
{
  "Email": "user@example.com",
  "Company": "Acme",
  "LastName": "Doe",
  "FirstName": "John",
  "contact_id": "person_123"
}

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

Triggered by

Apps that pair well as the trigger for Get Contact.

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

A
Gmail → Autopilot
1 Gmail triggers
A
Slack → Autopilot
13 Slack triggers
A
Google Sheets → Autopilot
2 Google Sheets triggers
A
HubSpot → Autopilot
18 HubSpot triggers
FAQ

Questions about Get Contact.

What does the Get Contact action do in Autopilot?
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.
What inputs does Get Contact require?
Required: Contact ID or Email. Every input accepts a static value or a variable from any upstream node in your workflow.
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 Get Contact support batch operations?
Yes. Run Get Contact 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
List Contacts
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.