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 retrieve detailed information about a specific object identified by a UUID or slug. The "Get Object" operation under the "Objects" resource fetches metadata and properties of an object within the Attio platform.
Common scenarios where this node is beneficial include:
- Retrieving configuration or schema details of a particular object in Attio for further processing.
- Using the object's data as part of an automation workflow, such as syncing object definitions or validating object existence before record operations.
- Integrating Attio objects into other systems by fetching their details dynamically.
For example, you might use this node to get the definition of a "people" object to understand its fields before creating or updating records related to contacts.
Properties
| Name | Meaning |
|---|---|
| Object | A UUID or slug string that uniquely identifies the object to retrieve. Example: "people" |
Output
The node outputs JSON data representing the retrieved object from Attio. This JSON typically includes all the metadata and attributes associated with the specified object, such as its ID, name, fields, and other configuration details.
The output structure is:
{
"json": {
// Object metadata and properties returned by the Attio API
}
}
No binary data output is produced by this operation.
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/v2/objects/{object}. - Proper configuration of the API authentication token in n8n credentials is necessary.
Troubleshooting
Common issues:
- Invalid or missing object identifier (UUID or slug) will cause the API request to fail.
- Expired or incorrect API authentication token will result in authorization errors.
- Network connectivity problems can prevent successful API calls.
Error messages:
"Operation Get Object not found for resource Objects": Indicates a misconfiguration or unsupported operation/resource combination.- HTTP 401 Unauthorized: Check that the API key credential is valid and has proper permissions.
- HTTP 404 Not Found: The specified object identifier does not exist; verify the UUID or slug.
Resolutions:
- Ensure the "Object" property is correctly set with a valid identifier.
- Verify and update the API key credential in n8n.
- Confirm network access to the Attio API endpoint.