ActionAttioUpdated September 2026
How do I delete an Attio record?
Short answer: You can delete record in Attio by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Attio Delete Record action to a workflow, map its 2 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
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 |
|---|---|---|---|
Object object | options | Required | – |
Record ID record_id | string | Required | – |
Sample request
{"object": "{{trigger.object}}","record_id": "{{trigger.record_id}}"}
Returns
{"record_id": "{{inputs.record_id}}"}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for Delete Record.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Delete Record.
What does the Delete Record action do in Attio?
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.
What inputs does Delete Record require?
Required: Object, 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 run history shows the failed step with its input and the error message Attio returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.
Does Delete Record support batch operations?
Run Delete Record inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Attio's rate limits.
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.
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.
ActionList 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.