Actions111
- Item Actions
- Webhook Actions
- Collection Actions
- File Actions
- Activity Actions
- Asset Actions
- Authentication Actions
- Extension Actions
- Field Actions
- Folder Actions
- Permission Actions
- Preset Actions
- Relation Actions
- Revision Actions
- Role Actions
- Setting Actions
- User Actions
- Utility Actions
Overview
The "User - Delete Multiple" operation in this custom n8n node allows you to delete several user records at once by providing their primary keys. This is useful for bulk user management tasks, such as cleaning up test accounts, removing users who no longer need access, or performing administrative batch deletions.
Practical examples:
- Deleting multiple inactive users from a system.
- Removing a set of users identified as duplicates.
- Bulk cleanup after importing erroneous data.
Properties
| Name | Meaning |
|---|---|
| Keys (JSON) | An array of user primary keys. Example: ["653925a9-970e-487a-bfc0-ab6c96affcdc", "c86c2761-65d3-43c3-897f-6f74ad6a5bd7"]This property is required. |
Output
The output will be a JSON object reflecting the result of the deletion operation. Typically, it may include:
- A list of successfully deleted user IDs.
- Information about any failures (such as invalid or non-existent keys).
Example output:
{
"deleted": [
"653925a9-970e-487a-bfc0-ab6c96affcdc",
"c86c2761-65d3-43c3-897f-6f74ad6a5bd7"
],
"failed": []
}
Note: The exact structure may vary depending on the backend implementation.
Dependencies
- Requires connection to a Directus API instance.
- May require an API key or authentication credentials configured in n8n.
- Ensure that the user account used has permission to delete users.
Troubleshooting
Common issues:
- Invalid or missing primary keys: If the provided keys are incorrect or do not exist, the node may return errors or partial success.
- Insufficient permissions: If the API credentials lack delete permissions, the operation will fail.
- Malformed JSON input: If the "Keys (JSON)" property is not a valid JSON array, the node will throw a parsing error.
Error messages and resolutions:
"Invalid JSON": Ensure the "Keys (JSON)" field contains a properly formatted JSON array."Permission denied": Check your API credentials and user permissions in Directus."User not found": Verify that all provided keys correspond to existing users.