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 interacts with the Attio API to delete a specific task by its ID. It is useful in automation workflows where tasks need to be programmatically removed from Attio, such as cleaning up completed or obsolete tasks, synchronizing task lists between systems, or managing task lifecycle automatically.
For example, you might use this node to delete a task after it has been marked as done in another system, or to remove tasks that are no longer relevant based on certain conditions in your workflow.
Properties
| Name | Meaning |
|---|---|
| Task Id | The ID of the task to delete. |
The "Task Id" property expects a string representing the unique identifier of the task you want to delete.
Output
The output JSON contains the response from the Attio API after attempting to delete the specified task. Typically, this will include confirmation of deletion or details about the deleted task.
If an error occurs (e.g., invalid task ID or authorization failure), the output will contain an error message describing the issue.
No binary data is output by this node.
Dependencies
- Requires an API key credential for authenticating with the Attio API.
- The node sends HTTP DELETE requests to the Attio API endpoint for tasks.
- The base URL used is
https://api.attio.com. - Proper configuration of the API authentication token in n8n credentials is necessary.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Task Id will result in an error from the API.
- Missing or incorrect API authentication token will cause authorization errors.
- Network connectivity issues can prevent successful API calls.
Error messages and resolutions:
"Operation ... not found for resource ...": This indicates a misconfiguration or unsupported operation; ensure the correct Resource and Operation are selected.- API errors returned in the output JSON under an
errorfield usually indicate problems like invalid IDs or permission issues. Verify the Task Id and API credentials. - If the node fails but "Continue On Fail" is enabled, errors will be included in the output JSON instead of stopping execution.
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)