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 to manage various resources, including webhooks. Specifically, for the Webhooks resource and the Delete operation, the node deletes a webhook identified by its unique ID from the Directus system.
This operation is useful when you want to programmatically remove webhook configurations that are no longer needed or valid, helping maintain a clean and efficient webhook setup in your Directus instance.
Practical example:
If you have a webhook set up to trigger on certain data changes but want to disable it permanently or replace it with a new one, you can use this node's Delete operation to remove the old webhook by specifying its ID.
Properties
| Name | Meaning |
|---|---|
| ID | The primary key (unique identifier) of the webhook to delete. This is a required string input. |
Output
The output of the Delete operation for Webhooks is a JSON object representing the response from the Directus API after attempting to delete the specified webhook. Typically, this will include confirmation details or status information about the deletion.
The structure generally looks like:
{
"result": <boolean or object>
}
- If the deletion is successful, the
resultfield may betrueor contain relevant metadata. - If an error occurs, the node may output an error message instead (depending on error handling settings).
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 operations.
- Proper permissions in Directus are necessary to delete webhooks.
Troubleshooting
Common issues:
- Invalid or missing webhook ID: Ensure the ID provided corresponds to an existing webhook.
- Insufficient permissions: The API key used must have rights to delete webhooks.
- Network or authentication errors: Verify the Directus API credentials and connectivity.
Error messages:
"Webhook not found": The specified ID does not exist; verify the ID."Unauthorized"or"Forbidden": Check API credentials and permissions.- Other HTTP errors: Review the Directus API documentation for specific error codes.
To handle errors gracefully, enable the node’s "Continue On Fail" option to capture error messages in the output JSON.