AttioInstall

Overview

This node interacts with the Attio API to retrieve a specific record from a given object. It is designed to fetch detailed information about a single record identified by its unique ID within a specified object type.

Common scenarios where this node is beneficial include:

• Retrieving contact details or profile information for a person stored in Attio.
• Accessing a particular record's data for further processing or integration in workflows.
• Fetching a record before updating or validating its contents.

For example, you might use this node to get a person's record by specifying the "people" object and the record's UUID, then use that data downstream in your automation.

Properties

Output

The node outputs JSON data representing the retrieved record from Attio. The structure corresponds directly to the record's attributes as returned by the Attio API, typically including fields such as identifiers, properties, metadata, and relationships relevant to the record.

No binary data output is produced by this operation.

Example output snippet (simplified):

{
  "id": "891dcbfc-9141-415d-9b2a-2238a6cc012d",
  "object": "people",
  "attributes": {
    "name": "John Doe",
    "email": "john.doe@example.com"
  },
  "created_at": "2023-01-01T12:00:00Z",
  "updated_at": "2023-06-01T08:30:00Z"
}

Dependencies

• Requires an API key credential for authenticating with the Attio API.
• The node makes HTTP requests to the Attio REST API endpoint https://api.attio.com.
• Proper configuration of the API authentication token in n8n credentials is necessary.

Troubleshooting

• Common issues:

  • Invalid or missing API key will cause authentication failures.
  • Incorrect Object or Record Id values may result in "not found" errors.
  • Network connectivity problems can prevent successful API calls.

• Error messages:

  • "Operation Get Record not found for resource Records": Indicates a misconfiguration or unsupported operation selection.
  • HTTP 401 Unauthorized: Check that the API key credential is correctly set and valid.
  • HTTP 404 Not Found: Verify that the Object and Record Id parameters are correct and exist in Attio.

• Resolutions:

  • Ensure the API key credential is properly configured and has sufficient permissions.
  • Double-check the Object slug/UUID and Record Id UUID for typos or outdated values.
  • Confirm network access to the Attio API endpoint.

Links and References

• Attio API Documentation
• Attio Official Website