ActionAttioUpdated September 2026

How do I update an Attio person record?

Short answer: You can update person in Attio by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Attio Update Person action to a workflow, map its 4 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Update Person in Attio — start free All 8 Attio actions

Update 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	–
Email email	string	Optional	The email address. Used as the recipient or identifier depending on context.
Phone phone	string	Optional	Phone number in E.164 format (with country code, no spaces).
Job Title job_title	string	Optional	–

Sample request

{
  "record_id": "{{trigger.record_id}}",
  "email": "e.g. user@example.com",
  "phone": "e.g. +14155551234",
  "job_title": "{{trigger.job_title}}"
}

Returns

{
  "data": {
    "id": {
      "record_id": "person_abc123"
    }
  }
}

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

Triggered by

Apps that pair well as the trigger for Update 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 Update Person.

What does the Update Person action do in Attio?

Partial update on a person record — only the passed attributes change. Useful for "enriched data from Clearbit/Apollo → write back to Attio" augmentation workflows that keep the CRM record fresh.

What inputs does Update 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 Update Person support batch operations?

Run Update 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