AttioInstall

Overview

This node allows you to delete a specific record from an object in the Attio system by specifying the object's identifier and the record's unique ID. It is useful when you want to programmatically remove outdated, incorrect, or unwanted records from your Attio database.

Common scenarios:

• Cleaning up old contact records from a "people" object.
• Removing obsolete entries from custom objects in your Attio workspace.
• Automating data maintenance workflows where records need to be deleted based on certain triggers.

Example:
You have a workflow that detects duplicate contacts and uses this node to delete the duplicate record by providing its UUID.

Properties

Output

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

The output structure:

{
  "json": {
    // API response confirming deletion or error information
  },
  "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 specified object and record.
• Ensure the API key has sufficient permissions to delete records.

Troubleshooting

• Common issues:

  • Invalid or missing Object UUID/slug or Record UUID can 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:

  • "Operation Delete Record not found for resource Records": Indicates misconfiguration or unsupported operation selection.
  • API errors returned in the JSON response will include messages explaining the failure (e.g., "Record not found", "Unauthorized").

• Resolutions:

  • Verify the correctness of the Object and Record IDs.
  • Check that the API key used has delete permissions.
  • Confirm network access to the Attio API endpoint.
  • Enable "Continue On Fail" in the node settings to handle errors gracefully in workflows.

Links and References

• Attio API Documentation (for detailed API endpoints and authentication)
• n8n documentation on HTTP Request Node (conceptual similarity)
• General best practices for managing records in CRM systems