Actions100
- Activity Actions
- Asset Actions
- Authentication Actions
- Collection Actions
- Extension Actions
- Field Actions
- File Actions
- Folder Actions
- Item Actions
- Permission Actions
- Preset Actions
- Relation Actions
- Revision Actions
- Role Actions
- Setting Actions
- User Actions
- Utility Actions
Overview
This node is designed to manage permissions within a system, specifically allowing the deletion of permission rules. It is useful in scenarios where you need to revoke or remove access rights or restrictions that were previously set up. For example, if a user role no longer requires certain permissions, this node can delete those specific permission entries by their unique identifier.
Properties
| Name | Meaning |
|---|---|
| ID | The primary key of the permission rule to be deleted. This is a required string value identifying which permission entry should be removed. |
Output
The output will typically contain JSON data indicating the result of the delete operation. This may include confirmation of successful deletion or details about the deleted permission rule. There is no indication that binary data is involved in this operation.
Dependencies
- Requires an API authentication token or similar credential to authorize permission management actions.
- Depends on an external service or API endpoint that handles permission rules.
- The node uses internal routing and method loading mechanisms to perform the delete action.
Troubleshooting
- Missing or invalid ID: If the ID property is not provided or incorrect, the node will likely fail to find the permission rule to delete. Ensure the ID is correct and corresponds to an existing permission.
- Authentication errors: Failure to provide valid credentials or tokens will prevent the node from executing the delete operation.
- Permission denied: The authenticated user or token might lack sufficient rights to delete permission rules.
- API errors: Network issues or API downtime could cause failures; check connectivity and API status.
Links and References
- Refer to your system's API documentation for managing permissions.
- Consult n8n documentation on how to configure API credentials and handle node errors.