ZitadelInstall

Overview

This node provides an interface to interact with the Zitadel API, a platform for identity and access management. It supports multiple services such as UserService, OrganizationService, AuthService, ManagementService, AdminService, ZITADELActions, and UserSchemaService. The node allows performing various operations on these services by calling their respective API methods.

The lockUser operation under the "Default" resource is designed to lock a user account, preventing that user from accessing the system. This can be useful in scenarios such as security enforcement, compliance, or administrative control when a user's access needs to be temporarily or permanently disabled.

Practical examples:

• Locking a user after detecting suspicious activity.
• Temporarily disabling a user during an investigation.
• Enforcing organizational policies by locking users who violate terms.

Properties

Note: The property shown depends on the selected service. For example, if you select UserService, you must provide userId. If you select ManagementService, you must provide id.

Output

The node outputs a JSON object representing the response from the Zitadel API for the invoked operation. For the lockUser operation, this typically includes confirmation or status details about the locking action performed on the user.

The output structure is dynamic and directly reflects the API response from the specific service method called. There is no binary data output.

Example output JSON snippet (conceptual):

{
  "userId": "12345",
  "locked": true,
  "message": "User has been successfully locked."
}

Dependencies

• Requires an API authentication token (Personal Access Token) for Zitadel, configured in n8n credentials.
• Depends on the Zitadel gRPC client libraries bundled within the node.
• Network access to the Zitadel API endpoint at https://zitadel.studentcouncil.dk.

Troubleshooting

• Invalid or missing credentials: Ensure the API token is correctly set up in n8n credentials; otherwise, authorization will fail.
• Incorrect user ID: Providing an invalid or non-existent user ID will cause the API call to fail. Verify the user ID before running the node.
• Unsupported operation or service: Selecting a service-operation combination not supported by the node will result in no action or empty output.
• JSON parsing errors: Input parameters are parsed as JSON where applicable. Malformed JSON input will cause errors. Provide valid JSON strings or plain strings as required.

Links and References

• Zitadel Official Documentation
• Zitadel API Reference
• n8n Documentation