Short answer: Drop the "Attio → Get 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 |
|---|---|---|---|
Person Record ID record_id | string | Required | — |
{"record_id": "{{trigger.record_id}}"}
{"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.
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.