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 a given record within an object. It supports querying current or historic attribute values, with pagination options to limit and offset the results. This is useful for workflows that need to fetch detailed attribute data from records, such as retrieving contact information or historical changes in data attributes for people or companies.
Use Case Examples
- Fetch the current email addresses (attribute values) for a specific person record identified by UUID.
- Retrieve all historic values of a custom attribute for a company record to analyze changes over time.
Properties
| Name | Meaning |
|---|---|
| Object | A UUID or slug to identify the object the record belongs to. |
| Record Id | A UUID to identify the record you want to query values on. |
| Attribute | A UUID or slug to identify the attribute you want to query values on. |
| Show Historic | Boolean flag to indicate if all historic values for the attribute should be returned (true) or only the currently active values (false). Defaults to false. Cannot be true for certain attribute types. |
| 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 record.
Dependencies
- Requires an API key credential for Attio API authentication.
Troubleshooting
- Common issues include invalid UUIDs or slugs for object, record, or attribute parameters, resulting in API errors.
- Setting 'Show Historic' to true for COMINT or enriched attributes on people/company objects will cause the API to reject the request.
- Pagination parameters 'Limit' and 'Offset' must be valid numbers; otherwise, the API may return errors or unexpected results.
- Authorization errors if the API key credential is missing or invalid.
Links
- Attio API Pagination Guide - Guide on how to use pagination parameters 'limit' and 'offset' in Attio API requests.