Short answer: Drop the "Attio → Create Person" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
First Name first_name | string | Required | Contact's first (given) name. |
Last Name last_name | string | Required | Contact's last (family) name. |
Email Address email | string | Optional | The email address. Used as the recipient or identifier depending on context. |
Phone Number phone | string | Optional | Phone number in E.164 format (with country code, no spaces). |
Job Title job_title | string | Optional | — |
Linked Company Record ID company_id | string | Optional | — |
{"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}}"}
{"data": {"id": {"record_id": "person_abc123","workspace_id": "ws_xyz"},"values": {}}}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.