ActionAttioUpdated September 2026

How do I fetch a single person from Attio?

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

Get Person in Attio — start free All 8 Attio actions

Get Person in Attio — start free

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
Person Record ID record_id	string	Required	–

Sample request

{
  "record_id": "{{trigger.record_id}}"
}

Returns

{
  "data": {
    "id": {
      "record_id": "person_abc123"
    },
    "values": {
      "name": [
        {
          "full_name": "Jane Doe",
          "last_name": "Doe",
          "first_name": "Jane"
        }
      ],
      "company": [
        {
          "target_record_id": "company_xyz"
        }
      ],
      "job_title": "CEO",
      "phone_numbers": [
        {
          "phone_number": "+15550100"
        }
      ],
      "email_addresses": [
        {
          "email_address": "jane@acme.com"
        }
      ]
    }
  }
}

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

Triggered by

Apps that pair well as the trigger for Get Person.

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

Google Sheets → Attio

2 Google Sheets triggers

HubSpot → Attio

18 HubSpot triggers

FAQ

Questions about Get Person.

What does the Get Person action do in Attio?

Returns the person record by ID with all configured attributes (standard + custom) plus list memberships and linked company. The standard lookup for enrichment workflows or for resolving person IDs to readable identity in downstream notifications.

What inputs does Get Person require?

Required: Person Record ID. 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 Attio returns an error?

The run history shows the failed step with its input and the error message Attio 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 Person support batch operations?

Run Get Person 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 Attio's rate limits.

More actions