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 list records for a specified object. It allows users to filter, sort, and paginate the records returned from the API. This is useful for scenarios where you need to retrieve a subset of data from a database or CRM system based on specific criteria, such as listing people records filtered by name and sorted by last name.
Use Case Examples
- Retrieve a list of people records where the name is 'Ada Lovelace', sorted by last name in ascending order, with a limit of 500 records.
- Fetch records from a custom object with specific filters and pagination to process or analyze data in workflows.
Properties
| Name | Meaning |
|---|---|
| Object | A UUID or slug to identify the object to list records for. |
| Filter | An object used to filter results to a subset of results, allowing precise querying of records. |
| Sorts | An object used to sort results, specifying the direction and attribute to order the records by. |
| Limit | The maximum number of results to return, controlling the size of the response. |
| Offset | The number of results to skip before returning, used for pagination. |
Output
JSON
json- The JSON response from the Attio API containing the list of records matching the query.
Dependencies
- Attio API with an access token credential
Troubleshooting
- Ensure the provided object UUID or slug is correct and exists in the Attio system to avoid 'Operation not found' errors.
- Verify that the filter and sorts JSON are correctly formatted to prevent JSON parsing errors.
- Check API access token validity and permissions if authentication errors occur.
- If pagination parameters (limit and offset) are set incorrectly, the response might be empty or incomplete.
Links
- Attio Filtering and Sorting Guide - Guide on how to use filtering and sorting in Attio API queries.
- Attio Pagination Guide - Guide on how to use pagination parameters in Attio API queries.