Start free
ActionAttioUpdated June 2026

How do I add a person or company to an Attio list?

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

Use this actionAll 8 Attio actions
Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

FieldTypeRequiredDescription
List ID
list_id
stringRequired–
Record ID to add
parent_record_id
stringRequired–
Record's Object
parent_object
optionsRequired–
Sample request
{
  "list_id": "{{trigger.list_id}}",
  "parent_record_id": "{{trigger.parent_record_id}}",
  "parent_object": "{{trigger.parent_object}}"
}
Returns
{
  "data": {
    "id": {
      "entry_id": "entry_abc123"
    }
  }
}

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

Triggered by

Apps that pair well as the trigger for Add Record to List.

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

Gmail → Attio
1 Gmail triggers
Slack → Attio
13 Slack triggers
Google Sheets → Attio
2 Google Sheets triggers
HubSpot → Attio
18 HubSpot triggers
FAQ

Questions about Add Record to List.

What does the Add Record to List action do in Attio?
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.
What inputs does Add Record to List require?
Required: List ID, Record ID to add, Record's Object. 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 Add Record to List support batch operations?
Yes. Run Add Record to List inside a Loop node to process arrays. TinyCommand handles Attio's rate limits automatically so you don't have to throttle manually.
More actions

Other Attio actions.

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
Create 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.
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.