Actions57
- Objects Actions
- Attributes Actions
- List Attributes
- Get Attribute
- Update Attribute
- GET target/identifier/attributes/attribute/options
- POST target/identifier/attributes/attribute/options
- PATCH target/identifier/attributes/attribute/options/option
- POST target/identifier/attributes/attribute/statuses
- Create Attribute
- GET target/identifier/attributes/attribute/statuses
- PATCH target/identifier/attributes/attribute/statuses/status
- Entries Actions
- Records Actions
- Lists Actions
- Meta Actions
- Workspace Members Actions
- Notes Actions
- Tasks Actions
- Webhooks Actions
- Threads Actions
- Comments Actions
Overview
This node interacts with the Attio API to retrieve values of a specific attribute for an entry within a list. It is useful for scenarios where you need to fetch detailed attribute data, including historic values, for entries in a list managed in Attio. For example, it can be used to get all current or historic values of a contact's attribute in a sales list.
Use Case Examples
- Retrieve all current values of a contact's email attribute in the 'enterprise_sales' list.
- Fetch historic values of a custom attribute for a specific entry in a list to analyze changes over time.
Properties
| Name | Meaning |
|---|---|
| List | A UUID or slug identifying the list the entry is in. |
| Entry Id | A UUID identifying the entry. |
| Attribute | A UUID or slug to identify the attribute you want to query values on. |
| Show Historic | If true, returns all historic values for the attribute; if false, returns only currently active values. Defaults to false. Can only be true for attributes supporting historic data. |
| Limit | The maximum number of results to return, used for pagination. |
| Offset | The number of results to skip before returning, used for pagination. |
Output
JSON
json- The JSON response from the Attio API containing the attribute values for the specified entry.
Dependencies
- Requires an API key credential for Attio API authentication.
Troubleshooting
- Common issues include invalid UUIDs or slugs for list, entry, or attribute parameters, which will cause the API to return errors.
- Setting 'Show Historic' to true for attributes that do not support historic data will cause the endpoint to throw an error.
- Pagination parameters 'Limit' and 'Offset' must be used correctly to avoid missing or duplicated data in results.
Links
- Attio API Pagination Guide - Guide on how to use pagination parameters 'limit' and 'offset' effectively.