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 "Activity". Specifically, for the Activity - Delete operation, it allows users to delete an activity comment by its unique identifier. This is useful in scenarios where you want to programmatically remove specific activity comments from your Directus instance, such as cleaning up outdated or irrelevant comments.
Practical example:
- Automatically deleting user activity comments that are flagged as inappropriate.
- Removing test or placeholder comments after a workflow completes.
Properties
| Name | Meaning |
|---|---|
| ID | Unique identifier (number) of the activity comment to delete. Must be at least 1. |
Output
The output JSON contains the response from the Directus API after attempting to delete the specified activity comment. Typically, this will include confirmation of deletion or relevant status information returned by the API.
Example output structure:
{
"json": {
// API response data confirming deletion or status
}
}
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to a Directus instance via an API key credential configured in n8n.
- The node uses the Directus REST API endpoints and expects proper authentication.
- No additional external dependencies beyond the Directus API and n8n's HTTP request capabilities.
Troubleshooting
Common issues:
- Providing an invalid or non-existent ID will result in an error from the Directus API.
- Network or authentication failures can prevent successful deletion.
- Insufficient permissions on the API key may cause authorization errors.
Error messages and resolutions:
- "Not Found" or similar: Verify the ID exists and is correct.
- "Unauthorized" or "Forbidden": Check API credentials and permissions.
- "Invalid ID" or validation errors: Ensure the ID is a positive integer (minimum 1).
- If the node throws an error, enabling "Continue On Fail" can allow workflows to proceed while capturing error details in the output.