Directus (flagbit)

Overview

This node is designed to delete multiple roles in a system that manages user roles and permissions. It allows users to specify an array of role identifiers (primary keys) to be deleted in one operation. This is useful for bulk management of roles, such as cleaning up unused or obsolete roles efficiently.

Practical examples include:

• Removing several outdated roles after a reorganization of user permissions.
• Bulk deleting test or temporary roles created during development or testing phases.

Properties

Output

The output will contain JSON data representing the result of the deletion operation. Typically, this might include confirmation of which roles were successfully deleted or any errors encountered for specific keys. The exact structure depends on the underlying API response but generally confirms the bulk deletion status.

No binary data output is expected from this operation.

Dependencies

• Requires access to the roles management API endpoint capable of handling bulk deletions.
• Needs appropriate API authentication credentials configured in n8n to authorize the deletion requests.

Troubleshooting

• Common issues:

  • Providing invalid or non-existent role keys may cause partial or complete failure of the deletion operation.
  • Insufficient permissions or missing API credentials can lead to authorization errors.
  • Malformed JSON input for the keys property can cause parsing errors.

• Error messages and resolutions:

  • "Invalid keys format": Ensure the keys are provided as a valid JSON array of strings.
  • "Unauthorized" or "Forbidden": Verify that the API credentials have sufficient permissions to delete roles.
  • "Role not found": Confirm that all specified role IDs exist before attempting deletion.

Links and References

• Refer to the official API documentation of the roles management system for details on bulk deletion endpoints.
• JSON formatting guides for correctly structuring the keys input.