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 a specific attribute associated with either an object or a list within the Attio platform. It is useful when you want to fetch detailed metadata or custom fields (attributes) tied to particular entities identified by UUIDs or slugs.
Common scenarios:
- Fetching a custom attribute of a contact or company record stored as an object.
- Retrieving an attribute related to a mailing list or other list-type entity.
- Integrating Attio data into workflows that require dynamic access to attribute values for further processing or decision-making.
Example:
You have a list in Attio representing newsletter subscribers and want to get a specific attribute like "Subscription Status" for a given subscriber identified by their unique ID.
Properties
| Name | Meaning |
|---|---|
| Target | Specifies whether the attribute belongs to an "Objects" entity or a "Lists" entity. |
| Identifier | The UUID or slug identifying the specific object or list that owns the attribute. |
| Attribute | The UUID or slug identifying the exact attribute to retrieve from the specified target. |
Output
The node outputs JSON data representing the requested attribute's details as returned by the Attio API. This typically includes the attribute's value, metadata, and any relevant properties defined in Attio.
No binary data output is involved.
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 expired API token leading to authorization errors.
- Incorrect UUID or slug values for the target, identifier, or attribute causing "not found" errors.
- Network connectivity problems preventing API calls.
Error messages:
"Operation Get Attribute not found for resource Attributes": 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: Verify that the provided identifiers (target, identifier, attribute) are correct and exist in Attio.
Resolution tips:
- Double-check all input parameters for typos or incorrect values.
- Ensure the API key credential is correctly set up and active.
- Test connectivity to the Attio API outside n8n to isolate network issues.
Links and References
- Attio API Documentation (for detailed API endpoints and attribute structures)
- n8n Documentation on Credentials (for setting up API keys)