Directus (denkhaus) icon

Directus (denkhaus)

Consume Directus API
Join our community

Actions111

Overview

The Preset - List operation in this custom n8n node retrieves a list of "presets" from an external service, with flexible options for filtering, aggregation, export, and output formatting. This node is useful when you need to fetch, filter, aggregate, or export preset data—such as configurations, templates, or saved settings—from a connected system.

Common scenarios:

  • Fetching all available presets for reporting or further automation.
  • Exporting presets as CSV, JSON, or XML files for backup or sharing.
  • Filtering presets based on specific criteria (e.g., by author, date, or other fields).
  • Aggregating preset data (e.g., counting, summing, averaging values).
  • Integrating preset data into downstream workflow steps in n8n.

Practical examples:

  • Downloading all presets as a CSV file for analysis.
  • Listing only the first 10 presets that match a search query.
  • Grouping presets by category and calculating the average value per group.

Properties

Name Meaning
Return All Whether to return all results or only up to a given limit. If disabled, the "Limit" property determines how many results are returned.
Limit Max number of results to return. Only shown if "Return All" is false. Accepts values between 1 and 100.
Split Into Items Whether to output each element of an array as its own item in the n8n workflow. Useful for processing each preset individually.
JSON/RAW Parameters Whether the query and/or body parameters should be set via the value-key pair UI or as raw JSON. If enabled, use "Body Parameters" to provide parameters as JSON.
Body Parameters Body parameters as JSON or RAW. Used to specify advanced or custom request bodies when "JSON/RAW Parameters" is enabled.
Additional Fields A collection of optional parameters to refine the query:
• Aggregate: Apply aggregation functions (Average, Count, Sum, etc.) to fields.
• Binary Property for Export Data: Name of the binary property to store exported file data.
• Deep (JSON): Set nested query parameters for relational datasets.
• Export: Save API response as a file (csv, json, xml).
• File Name for Export Data: Name for the exported file (without extension).
• Fields: Specify which fields to return.
• Filter (JSON): Filter items using conditions in JSON format.
• Group By: Group results by specified field(s).
• Meta: Specify metadata to include in the response.
• Offset: Number of items to skip.
• Search: Filter by search query.
• Sort: Sorting order for results.
Aggregate Aggregate functions to perform calculations on fields. Options: Average, Average Distinct, Count, Count Distinct, Maximum, Minimum, SUM, SUM Distinct. Each function can be applied to a selected field.
Binary Property for Export Data Name of the binary property where exported file data will be stored (default: "data").
Deep (JSON) Allows setting nested query parameters for related datasets as JSON.
Export Saves the API response to a file. Options: csv, json, xml.
File Name for Export Data File name for the exported data (without extension).
Fields Specifies which fields to include in the returned objects.
Filter (JSON) Filters items in the collection according to provided JSON conditions.
Group By Groups results by one or more fields (e.g., "author,year(publish_date)").
Meta Specifies what metadata to include in the response.
Offset Number of items to skip when fetching data.
Search Filters items containing the search query in any field.
Sort Specifies sorting order. Use CSV of fields; prefix with "-" for descending, or "?" for random sort.

Output

  • The node outputs a list of presets matching the specified filters and options.
  • If "Split Into Items" is enabled, each preset is output as a separate item.
  • If "Export" is used, the response is saved as a binary file (CSV, JSON, or XML) under the specified binary property name.
  • The structure of the json output field reflects the fields requested and any applied aggregations, filters, or groupings.
  • When exporting, the binary output contains the file data, and the file name is set as specified.

Dependencies

  • Requires access to the external service providing the "presets" resource (details depend on the actual backend/API).
  • May require API credentials or authentication configured in n8n.
  • No additional npm dependencies beyond those bundled with the node.

Troubleshooting

Common issues:

  • Missing or invalid API credentials: Ensure that authentication is correctly configured in n8n.
  • Invalid filter or aggregation syntax: Double-check JSON structures for "Filter (JSON)", "Deep (JSON)", or "Body Parameters".
  • Export errors: If the export fails, verify that the "Binary Property for Export Data" and "File Name for Export Data" are valid and not conflicting with other nodes.
  • Limit exceeded: If "Limit" is set above the allowed maximum (100), reduce the value.

Error messages:

  • "Invalid JSON in filter/body/deep parameter": Check your JSON input for syntax errors.
  • "Unauthorized" or "Forbidden": Review your API credentials and permissions.
  • "Resource not found": Confirm the resource name ("presets") is correct and available in the backend.

Links and References

Discussion