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
This n8n node is designed to update an existing permission rule in a Directus instance. It allows users to specify the ID of the permission they wish to update and provide new data for that permission in JSON format. This node is useful in scenarios where you need to programmatically modify access control rules, such as automating role changes or updating permissions based on workflow events.
Practical examples:
- Automatically adjusting user permissions after onboarding.
- Updating access rights when a project status changes.
- Bulk-modifying permission rules as part of a migration or audit process.
Properties
| Name | Meaning |
|---|---|
| ID | Primary key of the permission rule. This identifies which permission entry will be updated. |
| Data (JSON) | A partial permissions object. The fields provided here will overwrite the corresponding fields in the specified permission rule. |
Output
The output will contain the updated permission rule in JSON format, reflecting the changes made by the operation. The structure will match the Directus permissions object, including any fields that were updated.
Dependencies
- Directus API: Requires access to a running Directus instance.
- Authentication: Typically requires an API token or credentials with sufficient privileges to update permissions.
- n8n Configuration: Ensure that the node is configured with the correct Directus endpoint and authentication details.
Troubleshooting
- Invalid ID: If the provided ID does not correspond to an existing permission rule, the node may return an error indicating that the resource was not found.
- Malformed JSON: If the "Data (JSON)" property contains invalid JSON, the node will fail to execute. Double-check your JSON syntax.
- Insufficient Permissions: If the API credentials do not have rights to update permissions, you may receive an authorization error.