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 list identified by a UUID or slug. It is useful in scenarios where you want to fetch metadata or properties of a particular list within your Attio workspace, such as for reporting, synchronization, or further processing in an automation workflow.
Practical examples:
- Fetching a contact or customer list details before performing operations like filtering or exporting.
- Retrieving list metadata to dynamically adjust subsequent workflow steps based on list attributes.
- Integrating Attio lists with other systems by pulling list data into external databases or CRMs.
Properties
| Name | Meaning |
|---|---|
| List | A UUID or slug that uniquely identifies the list to retrieve from Attio. This is a required string input. |
Output
The node outputs JSON data representing the full details of the requested list as returned by the Attio API. This typically includes all properties and metadata associated with the list, such as its name, description, creation date, and any custom fields defined in Attio.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating with the Attio API.
- The node makes HTTP requests to the Attio API endpoint
https://api.attio.com/v2/lists/{list}, where{list}is replaced by the provided UUID or slug. - Proper configuration of the API authentication token in n8n credentials is necessary.
Troubleshooting
Common issues:
- Invalid or missing list identifier (UUID/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 List not found for resource Lists": Indicates a misconfiguration or unsupported operation selection.- HTTP 401 Unauthorized: Check that the API key credential is correctly set and has sufficient permissions.
- HTTP 404 Not Found: The specified list UUID or slug does not exist; verify the identifier.
Resolutions:
- Double-check the "List" property value for correctness.
- Ensure the API key credential is valid and properly configured.
- Confirm network access to the Attio API endpoint.
Links and References
- Attio API Documentation (for detailed API response structure and parameters)
- n8n Documentation on Credentials (for setting up API authentication)