Actions52
- Records Actions
- Comments Actions
- Objects Actions
- Attributes Actions
- List Attributes
- Create Attribute
- Get Attribute
- Update Attribute
- GET target/identifier/attributes/attribute/options
- POST target/identifier/attributes/attribute/options
- PATCH target/identifier/attributes/attribute/options/option
- GET target/identifier/attributes/attribute/statuses
- POST target/identifier/attributes/attribute/statuses
- PATCH target/identifier/attributes/attribute/statuses/status
- Lists Actions
- Entries Actions
- Workspace Members Actions
- Notes Actions
- Tasks Actions
- Webhooks Actions
- Threads Actions
Overview
This node allows you to delete an entry from a specified list in the Attio system via its API. It is useful when you want to programmatically remove specific entries identified by their unique IDs from lists, for example, cleaning up outdated or incorrect data, or automating data management workflows.
Practical examples:
- Automatically deleting a contact entry from a sales list when they unsubscribe.
- Removing obsolete records from a project tracking list as part of a cleanup routine.
- Deleting entries that no longer meet certain criteria after processing.
Properties
| Name | Meaning |
|---|---|
| List | A UUID or slug identifying the list containing the entry to delete. Example: "enterprise_sales". |
| Entry Id | A UUID uniquely identifying the entry to be deleted within the specified list. |
Output
The output is a JSON object representing the response from the Attio API after attempting to delete the entry. Typically, this will confirm successful deletion or provide error details if the operation failed.
The output structure:
{
// API response fields confirming deletion or error information
}
No binary data is output by this node.
Dependencies
- Requires an API key credential for authenticating with the Attio API.
- The node makes HTTP DELETE requests to the Attio API endpoint
https://api.attio.com/v2/lists/{list}/entries/{entry_id}. - Proper configuration of the API authentication token in n8n credentials is necessary.
Troubleshooting
Common issues:
- Invalid or missing List UUID/slug or Entry ID can cause the API to return errors.
- Expired or invalid API authentication token will result in authorization errors.
- Network connectivity problems may prevent the request from completing.
Error messages and resolutions:
- "Operation configuration not found" — indicates a misconfiguration or unsupported operation; ensure the correct resource and operation are selected.
- Authorization errors — verify that the API key credential is valid and has sufficient permissions.
- Entry not found — check that the Entry ID exists in the specified list.
- Invalid parameters — confirm that the List and Entry Id inputs are correctly formatted UUIDs or slugs.
Links and References
- Attio API Documentation (for detailed API endpoints and authentication)
- n8n HTTP Request Node Documentation (for understanding how HTTP requests work in n8n)