Attio icon

Attio

Interact with Attio API

Overview

This node allows you to delete a specific note from the Attio system by providing its unique identifier (UUID). It is useful in scenarios where you want to programmatically remove notes, for example, cleaning up outdated or irrelevant information, automating data management workflows, or integrating with other systems that trigger note deletions.

Practical examples include:

  • Automatically deleting notes after a certain period.
  • Removing notes linked to a contact or project when they are archived or deleted.
  • Cleaning up test or temporary notes created during automated processes.

Properties

Name Meaning
Note Id A UUID which identifies the note to delete.

Output

The output of this node is a JSON object representing the response from the Attio API after attempting to delete the note. Typically, this will confirm successful deletion or provide error details if the operation failed.

The output structure is:

{
  "json": {
    // Response data from the delete operation, e.g., confirmation or status message
  },
  "pairedItem": {
    "item": <index_of_input_item>
  }
}

No binary data is produced 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 corresponding to the note ID.
  • Ensure the API key has sufficient permissions to delete notes.

Troubleshooting

  • Common issues:

    • Providing an invalid or malformed Note Id (UUID) will cause the API to reject the request.
    • Insufficient permissions on the API key may result in authorization errors.
    • Network connectivity problems can cause request failures.
  • Error messages and resolutions:

    • "Operation Delete Note not found for resource Notes": This indicates a misconfiguration or unsupported operation; verify the selected resource and operation.
    • API errors returned in the JSON response usually contain descriptive messages; check these to understand the failure reason.
    • If the node throws an error about missing credentials, ensure the API key credential is properly configured in n8n.

Links and References

Discussion