Attio icon

Attio

Interact with Attio API
Join our community

Actions52

Overview

This node operation "List Record Entries" under the "Records" resource allows users to retrieve a paginated list of entries associated with a specific record in an object. It is useful when you want to fetch related data entries or logs tied to a particular record identified by its UUID or slug.

Common scenarios:

  • Fetching all activity entries or changes linked to a customer record.
  • Retrieving transaction or event entries related to a specific entity.
  • Paginating through large sets of record entries for reporting or synchronization purposes.

Practical example:
You have a "people" object representing contacts, and you want to list all interaction entries (e.g., emails, calls) recorded for a contact with a given record ID. This operation lets you specify how many entries to return and from which offset, enabling efficient data retrieval.

Properties

Name Meaning
Object A UUID or slug identifying the object that the record belongs to. Example: "people"
Record Id A UUID identifying the specific record within the object. Example: "891dcbfc-9141-415d-9b2a-2238a6cc012d"
Limit The maximum number of results to return. Default is 10, max is 1000. Controls page size for pagination.
Offset The number of results to skip before starting to return entries. Default is 5. Used for pagination to skip initial records.

Output

The output is a JSON array where each item corresponds to a record entry retrieved from the API. Each entry contains the data fields as returned by the external service's API for record entries.

  • json: Contains the full response object for each entry.
  • pairedItem.item: Indicates the index of the input item this output corresponds to.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating requests to the external Attio API.
  • The node sends HTTP requests to the Attio REST API endpoint https://api.attio.com/v2/objects/{object}/records/{record_id}/entries.
  • Pagination parameters (limit and offset) are sent as query parameters.
  • Proper configuration of the API authentication token in n8n credentials is necessary.

Troubleshooting

  • Common issues:

    • Invalid or missing Object or Record Id values will cause the API to return errors or empty results.
    • Exceeding the maximum allowed limit (1000) may result in request failures.
    • Incorrect API credentials or expired tokens will lead to authorization errors.

  • Error messages:

    • "Operation ... not found for resource ...": Indicates a misconfiguration or unsupported operation/resource combination.
    • Authorization errors typically mention invalid or missing bearer tokens; ensure the API key credential is correctly set.
    • Network or timeout errors may occur if the API endpoint is unreachable; verify network connectivity.

  • Resolutions:

    • Double-check UUIDs and slugs for correctness.
    • Use valid API credentials and refresh tokens if needed.
    • Adjust pagination parameters within allowed limits.
    • Enable "Continue on Fail" in the node settings to handle partial failures gracefully.

Links and References

Discussion