Actions109
- Activity Actions
- Assets Actions
- Authentication Actions
- Collections Actions
- Extensions Actions
- Fields Actions
- Files Actions
- Folders Actions
- Items Actions
- Permissions Actions
- Presets Actions
- Relations Actions
- Revisions Actions
- Roles Actions
- Settings Actions
- Users Actions
- Utilities Actions
- Webhooks Actions
Extensions → List
AI-generatedOverview
The Directus (DrWade) n8n node for the resource Extensions with the operation List allows you to retrieve a list of installed extensions from your Directus instance. Extensions in Directus can include Displays, Interfaces, Layouts, and Modules, which are used to extend or customize the platform's functionality.
Common scenarios:
- Auditing which custom or core extensions are available in your Directus environment.
- Building automations that depend on the presence or configuration of certain extension types.
- Monitoring or reporting on the state of Directus extensions for compliance or documentation purposes.
Practical example:
You might use this node to fetch all "Displays" extensions and then filter or process them further in your workflow, or to check if a specific module is installed before proceeding with other automation steps.
Properties
| Name | Type | Meaning |
|---|---|---|
| Type | options | The type of extension to list. Options: Displays, Interfaces, Layouts, Modules. |
| Split Into Items | boolean | If enabled, outputs each extension as its own item; otherwise, returns an array. |
Output
- json:
- If Split Into Items is
false, the output will be a single item with ajsonproperty containing an array of extension objects. - If Split Into Items is
true, each extension object will be output as a separate item, each under thejsonproperty.
- If Split Into Items is
Structure of each extension object:
The exact structure depends on the extension type and Directus version, but typically includes fields such as:
{
"id": "string",
"name": "string",
"type": "string",
// ...other extension-specific properties
}
If the API response is not an object, the node will return { "response": <raw_response> }.
Dependencies
- Directus API: Requires access to a running Directus instance.
- API Credentials: You must configure the
directusApicredentials in n8n for authentication.
Troubleshooting
Common issues:
- Invalid Credentials: If the Directus API credentials are missing or incorrect, the node will throw an authentication error.
- Network/Connection Errors: If n8n cannot reach the Directus server, you'll receive connection errors.
- Invalid Extension Type: Supplying an invalid value for the "Type" property may result in an error or empty results.
Error handling:
- If an error occurs and "Continue On Fail" is enabled, the node will output an item with
{ "error": "<error message>" }in thejsonfield.