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
Overview
This node integrates with the Directus API, allowing users to perform various operations on different Directus resources. Specifically, for the Presets resource and the Delete operation, the node deletes a preset identified by its primary key (ID) from the Directus system.
This functionality is useful in scenarios where you need to programmatically remove saved presets from your Directus instance, such as cleaning up unused presets, automating maintenance tasks, or integrating preset management into larger workflows.
Example use case:
You have an automation that periodically removes outdated or invalid presets from your Directus project. By providing the ID of the preset to delete, this node will call the Directus API to delete it.
Properties
| Name | Meaning |
|---|---|
| ID | The primary key of the preset to delete. This is a required string input identifying which preset to remove. |
Output
The output of the node after deleting a preset is a JSON object representing the response from the Directus API. Typically, this will include confirmation details about the deletion or any relevant metadata returned by the API.
The structure generally looks like:
{
"json": {
// Response data from Directus API about the deleted preset
}
}
No binary data output is produced by this operation.
Dependencies
- Requires a valid connection to a Directus instance via an API key credential configured in n8n.
- The node uses the Directus REST API endpoints to perform actions.
- Proper permissions are needed on the Directus side to delete presets.
Troubleshooting
Common issues:
- Invalid or missing preset ID: Ensure the ID provided corresponds to an existing preset.
- Insufficient permissions: The API key used must have rights to delete presets.
- Network or authentication errors: Verify the Directus API credentials and connectivity.
Error messages:
- Errors returned by the Directus API will be passed through. For example, "Preset not found" if the ID does not exist.
- Authentication failures will indicate invalid or expired credentials.
- To handle errors gracefully, enable the node's "Continue On Fail" option to prevent workflow interruption.