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 permissions among other resources. Specifically, for the "Permissions" resource and the "Delete Multiple" operation, it allows users to delete multiple permission entries at once by specifying their primary keys. This is useful in scenarios where bulk removal of permissions is needed, such as cleaning up outdated or incorrect access rights in a Directus-managed project.
Practical example: If an administrator wants to revoke several permissions simultaneously, they can provide an array of permission IDs to this node, which will then send a single request to delete all specified permissions efficiently.
Properties
| Name | Meaning |
|---|---|
| Keys (JSON) | An array of permission primary keys to be deleted. Example: [34, 64] |
Output
The output of this operation is a JSON object representing the response from the Directus API after attempting to delete the specified permissions. Typically, this includes confirmation of deletion or details about any errors encountered.
No binary data is produced by this operation.
Dependencies
- Requires an active connection to a Directus instance via an API key credential.
- The node uses the Directus REST API endpoint for permissions.
- Proper API credentials must be configured in n8n to authenticate requests.
Troubleshooting
- Invalid Keys Format: Ensure that the "Keys (JSON)" property is a valid JSON array of numeric or string IDs. Malformed JSON or incorrect types will cause errors.
- Permission Denied: The API user must have sufficient rights to delete permissions; otherwise, the API will return authorization errors.
- Non-existent Keys: Attempting to delete keys that do not exist may result in partial success or error messages.
- API Connectivity Issues: Network problems or incorrect API URL/credentials will prevent successful execution.
Common error messages:
"Unauthorized"or"Forbidden": Check API credentials and user permissions."Bad Request": Verify the format and content of the keys array."Not Found": Some keys might not correspond to existing permissions.
Links and References
If you need information on other operations or resources, please let me know!