Actions118
- Item Actions
- Activity Actions
- Asset Actions
- Authentication Actions
- Collection Actions
- Extension Actions
- Field Actions
- File Actions
- Folder Actions
- Permission Actions
- Preset Actions
- Relation Actions
- Revision Actions
- Role Actions
- Server Actions
- Setting Actions
- User Actions
- Utility Actions
- Webhook Actions
Preset → List
AI-generatedOverview
This node operation lists presets from a data source, allowing users to retrieve multiple preset records with various filtering, sorting, and aggregation options. It is useful for scenarios where you need to fetch and process collections of preset data, such as displaying presets in a UI, exporting preset data, or performing analytics on preset collections.
Use Case Examples
- Fetch all presets without limit to process them in a workflow.
- Retrieve a limited number of presets with specific fields and sorting for display.
- Export preset data as CSV or JSON for reporting or backup.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all results or only up to a given limit. |
| Limit | Maximum number of results to return when not returning all. |
| Split Into Items | Whether to output each element of an array as its own item. |
| JSON/RAW Parameters | Whether the query and/or body parameters should be set via the value-key pair UI or JSON/RAW input. |
| Body Parameters | Body parameters as JSON or RAW input when JSON/RAW Parameters is enabled. |
| Additional Fields | Additional optional fields to customize the list operation, including aggregation functions, export options, filtering, sorting, grouping, and metadata. |
Output
JSON
presets- Array of preset objects returned from the list operation.exportData- Binary data of the exported file if export option is used.
Dependencies
- An API key credential or authentication token to access the data source.
Troubleshooting
- Ensure the API credentials are correctly configured to avoid authentication errors.
- If using JSON/RAW parameters, validate the JSON syntax to prevent parsing errors.
- When setting limits, ensure the value is within the allowed range (1-100) to avoid request errors.
- If export options are used, verify the file format and file name are correctly specified.