ZitadelInstall

Overview

This node integrates with the Zitadel API, allowing users to perform various operations on different Zitadel services. Specifically, the lockUser operation under the "Default" resource enables locking a user account in the Zitadel system. This is useful for administrators who want to temporarily or permanently disable user access for security or management reasons.

Common scenarios include:

• Locking a user after suspicious activity is detected.
• Temporarily disabling user accounts during maintenance or audits.
• Enforcing organizational policies by restricting user access.

Example: An admin wants to lock a user with ID 12345 using the UserService to prevent them from logging in until further notice.

Properties

Output

The node outputs a JSON object representing the response from the Zitadel API for the lockUser operation. This typically includes details about the locked user or confirmation of the lock action.

No binary data output is produced by this node.

Dependencies

• Requires an API authentication token (Personal Access Token) for Zitadel, configured as credentials in n8n.
• Connects to the Zitadel API endpoint at https://zitadel.studentcouncil.dk.
• Uses gRPC client libraries internally to communicate with Zitadel services.

Troubleshooting

• Invalid or missing API token: Ensure that the Zitadel API token credential is correctly set up and has sufficient permissions.
• Incorrect user ID: Verify that the userId or id provided matches an existing user in the Zitadel system.
• Operation not supported for selected service: Confirm that the lockUser operation is valid for the chosen service (UserService or ManagementService).
• JSON parsing errors: Input parameters are parsed as JSON if possible; ensure string inputs are valid JSON or plain strings as expected.

Links and References

• Zitadel Official Documentation
• Zitadel API Reference
• n8n Documentation