Directus (denkhaus) icon

Directus (denkhaus)

Consume Directus API
Join our community

Actions111

Overview

This n8n node is designed to interact with an "Extension" resource, specifically performing the "List" operation. It allows users to retrieve a list of extensions filtered by type (such as Displays, Interfaces, Layouts, or Modules). The node can also output each extension as a separate item if desired. This functionality is useful for automating workflows that need to process or analyze different types of extensions in a system, such as inventorying available modules or dynamically configuring interfaces.

Practical examples:

  • Fetch all available display extensions and process them individually.
  • List all interface extensions and send their details to another service.
  • Retrieve layouts or modules for reporting or further automation steps.

Properties

Name Type Meaning
Type options Specifies the category of extensions to list. Options include Displays, Interfaces, Layouts, and Modules.
Split Into Items boolean If enabled, outputs each element of the returned array as its own item in the workflow.

Output

The node outputs a JSON field containing the list of extensions matching the selected type. If "Split Into Items" is enabled, each extension will be output as a separate item; otherwise, all extensions are grouped in a single array under the json property.

Example output (when not split):

{
  "json": {
    "extensions": [
      { /* extension object 1 */ },
      { /* extension object 2 */ }
    ]
  }
}

Example output (when split):

{
  "json": { /* extension object 1 */ }
}

(and so on for each extension)

Dependencies

  • May require access to an external service or API providing the extensions data (e.g., Directus).
  • No explicit API keys or environment variables are mentioned in the provided code, but authentication may be required depending on the backend configuration.

Troubleshooting

  • No Data Returned: Ensure the selected "Type" matches available extension categories in your system.
  • Authentication Errors: If the node fails due to authentication, check your credentials or API key configuration in n8n.
  • Unexpected Output Structure: If "Split Into Items" is not set as intended, verify the boolean value in the node settings.

Links and References

Discussion