Actions56
- 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
- Records Actions
- Lists Actions
- Meta Actions
- Entries Actions
- Workspace Members Actions
- Notes Actions
- Tasks Actions
- Webhooks Actions
- Threads Actions
- Comments Actions
Entries → List Entries
AI-generatedOverview
This node operation retrieves a list of entries from a specified list in the Attio system. It allows users to filter, sort, limit, and paginate the entries returned from the list. This is useful for scenarios where you need to query and process subsets of data entries from a list, such as fetching contacts, records, or other entities stored in Attio for further automation or analysis.
Use Case Examples
- Retrieve all entries from a contact list filtered by name 'Ada Lovelace' and sorted by last name ascending.
- Fetch a limited number of entries from a list with pagination support to process in batches.
Properties
| Name | Meaning |
|---|---|
| List | A UUID or slug to identify the list to retrieve entries from. |
| Filter | An object used to filter results to a subset of entries based on specified criteria. |
| Sorts | An object used to sort the results by specified attributes and directions. |
| Limit | The maximum number of results to return, with a default of 500. |
| Offset | The number of results to skip before returning, used for pagination, defaulting to 0. |
Output
JSON
json- The JSON response containing the list of entries retrieved from the specified list.
Dependencies
- Requires an API key credential for Attio API authentication.
Troubleshooting
- Common issues include invalid list UUID or slug, resulting in errors fetching entries.
- Malformed JSON in the filter or sorts properties can cause request failures.
- Pagination parameters (limit and offset) must be used correctly to avoid missing or duplicate entries in paged results.
- Authorization errors if the API key is missing or invalid.
Links
- Filtering and Sorting Guide - Detailed guide on how to use filtering and sorting in Attio API queries.
- Pagination Guide - Guide on how to use pagination parameters in Attio API requests.