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 operation retrieves the values of a specific attribute for a given record within an object in Attio. It allows users to query either the current active values or all historic values of that attribute on the record.
Common scenarios where this node is beneficial include:
- Fetching detailed attribute data (e.g., contact details, status updates) for a particular record identified by its UUID.
- Auditing changes over time by retrieving historic attribute values.
- Integrating attribute data into workflows for further processing or decision-making.
For example, you might use this node to get all email addresses associated with a person record or to track how a company’s status attribute has changed historically.
Properties
| Name | Meaning |
|---|---|
| Object | A UUID or slug identifying the object the record belongs to. Example: "people" |
| Record Id | A UUID identifying the specific record to query attribute values on. |
| Attribute | A UUID or slug identifying the attribute whose values you want to retrieve. |
| Show Historic | Boolean flag indicating whether to return all historic values (true) or only currently active value(s) (false). Defaults to true. Cannot be set to true for certain attribute types like COMINT or enriched attributes on people/company objects. |
| Limit | Maximum number of results to return. Supports pagination. |
| Offset | Number of results to skip before starting to return results. Supports pagination. |
Output
The output is a JSON array where each item corresponds to the response from the API call fetching attribute values for the specified record. The structure of each JSON object matches the API's response schema for attribute values, typically including fields such as the value itself, timestamps, and metadata about the attribute value.
If the API supports binary data for attribute values (not indicated here), it would be included accordingly, but this operation primarily returns JSON data representing attribute values.
Dependencies
- Requires an API key credential for authenticating with the Attio API.
- The node makes HTTP requests to the Attio REST API endpoint corresponding to
/v2/objects/{object}/records/{record_id}/attributes/{attribute}/values. - Pagination support via
limitandoffsetquery parameters. - No additional external dependencies beyond the configured API credentials.
Troubleshooting
- Invalid UUID or Slug: If the
Object,Record Id, orAttributeparameters are incorrect or do not exist, the API will likely return an error. Verify these identifiers carefully. - Unauthorized / Authentication Errors: Ensure the API key credential is valid and has sufficient permissions.
- Historic Values Not Allowed: Setting
Show Historictotruefor COMINT or enriched attributes on people/company objects will cause errors. Set it tofalsein those cases. - Pagination Issues: Using inappropriate
limitoroffsetvalues may result in empty responses or skipped data. Follow the API pagination guide linked in the property description. - Network or API Downtime: Standard network errors or API unavailability can cause request failures; retry or check service status.
Links and References
- Attio API Documentation
- Pagination Guide (linked in property descriptions)