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 node retrieves a specific permission rule from a Directus instance by its primary key (ID). It is useful in scenarios where you need to fetch detailed information about a particular permission, such as for auditing, validation, or integration with other systems. For example, you might use this node to check the access rights assigned to a user role before performing sensitive operations.
Properties
| Name | Meaning |
|---|---|
| ID | Primary key of the permission rule. This is required and should be provided as a string (e.g., "34"). |
Output
The output will be a JSON object containing the details of the requested permission rule. The structure typically includes fields such as the permission's ID, role, collection, action, permissions, and any conditions or fields associated with it. The exact structure depends on the Directus API response for a permission rule.
Dependencies
- Requires access to a Directus instance.
- May require an API key or authentication credentials configured in n8n to connect to Directus.
Troubleshooting
- Missing or Invalid ID: If the "ID" property is missing or incorrect, the node may return an error indicating that the permission rule could not be found.
- Authentication Errors: If the Directus credentials are not set up correctly, you may encounter authentication or authorization errors.
- Network Issues: Connectivity problems between n8n and the Directus server can result in timeout or connection errors.