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
Presets → Delete
AI-generatedOverview
The Directus (DrWade) n8n node for the resource Presets with the operation Delete allows users to delete a specific preset from their Directus instance by providing its unique ID. This is useful in scenarios where you need to programmatically remove saved views, filters, or configurations (presets) that are no longer needed or should be cleaned up as part of an automated workflow.
Practical examples:
- Automatically removing outdated or temporary presets after a project phase is completed.
- Cleaning up user-generated presets as part of account deletion or data hygiene processes.
- Integrating with other systems to ensure only relevant presets remain in Directus.
Properties
| Name | Type | Meaning |
|---|---|---|
| ID | String | Primary key of the preset to be deleted. This uniquely identifies which preset will be removed from Directus. |
Output
- The output is a single object under the
jsonfield. - If the deletion is successful, the response typically contains either an empty object
{}or confirmation data as returned by the Directus API. - If an error occurs and "Continue On Fail" is enabled, the output will be:
{ "error": "<error message>" }
Dependencies
- Directus API: Requires access to a running Directus instance.
- API Credentials: The node requires valid Directus API credentials configured in n8n under the name
directusApi.
Troubleshooting
Common issues:
- Invalid or missing ID: If the provided ID does not correspond to an existing preset, the API will return an error.
- Insufficient permissions: The API credentials used must have permission to delete presets; otherwise, a permission error will occur.
- Network/API errors: Connectivity issues or incorrect API base URLs can cause failures.
Error messages and resolutions:
"Not Found"or similar: Ensure the ID is correct and the preset exists."Forbidden"or"Unauthorized": Check your API credentials and permissions."Request failed with status code ...": Review network connectivity and Directus server status.