ActionAttioUpdated June 2026

How do I add a person to Attio?

Short answer: Drop the "AttioCreate 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.

FieldTypeRequiredDescription
First Name
first_name
stringRequiredContact's first (given) name.
Last Name
last_name
stringRequiredContact's last (family) name.
Email Address
email
stringOptionalThe email address. Used as the recipient or identifier depending on context.
Phone Number
phone
stringOptionalPhone number in E.164 format (with country code, no spaces).
Job Title
job_title
stringOptional
Linked Company Record ID
company_id
stringOptional
Sample request
{
"first_name": "e.g. Jane",
"last_name": "e.g. Doe",
"email": "e.g. user@example.com",
"phone": "e.g. +14155551234",
"job_title": "{{trigger.job_title}}"
}
Returns
{
"data": {
"id": {
"record_id": "person_abc123",
"workspace_id": "ws_xyz"
},
"values": {}
}
}

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

Triggered by

Apps that pair well as the trigger for Create Person.

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

FAQ

Questions about Create Person.

What does the Create Person action do in Attio?
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.
What inputs does Create Person require?
Required: First Name, Last Name. 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 Create Person support batch operations?
Yes. Run Create 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.
Action
Create 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.
Action
Create 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.
Action
Delete 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.
Action
Get 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.
Action
List or Query People
Returns paginated people, optionally filtered by attribute values, list memberships, or recent activity. Useful for "all people in this list, fan out the campaign" or "sync all updated-since-yesterday records to the warehouse" patterns.

Send create person from your workflows.

Triggered by anything in the catalog. Free tier available. No credit card.