- Integrations
- /
- Attio
- /
- Actions
- /
- Update Person
ActionAttioUpdated May 2026
How do I update an Attio person record?
Short answer: Drop the "Attio → Update Person" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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.
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 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 Update Person support batch operations?
Yes. Run Update Person inside a Loop node to process arrays. Tiny Command handles Attio's rate limits automatically so you don't have to throttle manually.
More actions
Other Attio actions.
Action
Add Record to List
Adds an existing record (person or company) to an Attio list — Attio's pipeline construct. Useful for "lead matches our ICP filter → add to the Q1 targets list" workflows that feed Attio's native CRM workflows.
ActionCreate Company
Creates a new company record in Attio with domain as the unique identifier (Attio auto-enriches public firmographic data from the domain). Useful for "auto-create account record when we win a deal" workflows.
ActionCreate Note
Attaches a note to a person, company, or other Attio object. Notes appear in the record's activity timeline. Useful for "AI-summarised call notes → log to the contact" workflows that keep the CRM annotated automatically.
ActionCreate Person
Creates a new person with email as the dedupe key, optional company association, custom fields. Attio's flexible data model means person records can have any custom attributes the workspace has configured — pass them all in one call.
ActionDelete Record
Permanently removes a person, company, or other Attio object by ID. Irreversible. Used for GDPR right-to-erasure or for cleanup after wrong-data imports.
ActionGet Person
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.
Send update person from your workflows.
Triggered by anything in the catalog. Free tier available. No credit card.