AActionAutopilotUpdated September 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.
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 |
|---|---|---|---|
Contact ID or Email contactId | string | Required | Contact 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.
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 run history shows the failed step with its input and the error message Autopilot returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.
Does Get Contact support batch operations?
Run Get Contact inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Autopilot's rate limits.
More actions