Attio icon

Attio

Interact with Attio API
Join our community

Actions52

Overview

This node operation retrieves the values of a specific attribute for a given entry within a list in Attio. It allows users to query either the current active values or historic values (if supported) of that attribute. This is useful when you want to track changes or get detailed information about an attribute associated with an entry, such as contact details, status updates, or custom fields.

Practical examples:

  • Fetching the current email addresses associated with a contact entry.
  • Retrieving all past phone numbers recorded for a client entry if the attribute supports historic data.
  • Paginating through attribute values when there are many entries or values.

Properties

Name Meaning
List A UUID or slug identifying the list the entry belongs to. Example: "enterprise_sales"
Entry Id A UUID identifying the specific entry within the list. Example: "2e6e29ea-c4e0-4f44-842d-78a891f8c156"
Attribute A UUID or slug identifying the attribute whose values you want to retrieve. Example: "41252299-f8c7-4b5e-99c9-4ff8321d2f96"
Show Historic Boolean flag indicating whether to return all historic values (true) or only currently active values (false). Defaults to false. Only valid for attributes supporting historic data.
Limit Number specifying the maximum number of results to return. Supports pagination. Default is 10.
Offset Number specifying how many results to skip before starting to return results. Supports pagination. Default is 5.

Output

The node outputs JSON data representing the attribute values retrieved from the API. The structure typically includes:

  • An array of attribute value objects, each containing details such as the value itself, timestamps, and possibly metadata about the value's history if historic data was requested.
  • Pagination-related information may be included depending on the API response.

If the attribute supports historic data and Show Historic is set to true, multiple historical values will be returned; otherwise, only the current active value(s) are provided.

No binary data output is produced by this node operation.

Dependencies

  • Requires an API key credential for authenticating with the Attio API.
  • The node makes HTTP requests to the Attio REST API endpoint at https://api.attio.com.
  • Proper configuration of the API key credential in n8n is necessary for successful execution.

Troubleshooting

  • Error: Operation configuration not found
    This error occurs if the specified operation or resource is invalid or misconfigured. Verify that the Resource is set to "Entries" and the Operation matches exactly GET lists/list/entries/entry_id/attributes/attribute/values.

  • Error: Endpoint throws when show_historic is true for non-historic attributes
    If you enable Show Historic for an attribute that does not support historic data, the API will reject the request. Ensure that the attribute supports historic data before enabling this option.

  • Pagination issues
    If you receive fewer results than expected, check the Limit and Offset parameters to ensure they are set correctly for your use case.

  • Authentication errors
    Make sure the API key credential is valid and has sufficient permissions to access the requested list, entry, and attribute.

Links and References

Discussion