Zitadel icon

Zitadel

Interact with the Zitadel API

unlockUser

AI-generated

Overview

This node integrates with the Zitadel API to perform various operations on different services such as UserService, ManagementService, AuthService, and others. Specifically, for the unlockUser operation under the "Default" resource, it unlocks a user account by calling the appropriate service method with the provided user identifier.

Common scenarios where this node is beneficial include:

  • Unlocking user accounts that have been locked due to multiple failed login attempts.
  • Managing user access in an automated workflow after administrative review.
  • Integrating user management tasks into broader automation pipelines.

For example, an administrator could use this node to automatically unlock users after verifying their identity or resolving issues, without manually accessing the Zitadel admin console.

Properties

Name Meaning
Service The Zitadel service to call. Options: UserService, OrganizationService, AuthService, ManagementService, AdminService, ZITADELActions, UserSchemaService. Default is UserService.
userId The unique identifier of the user to unlock. Required when Service is UserService and Operation is unlockUser.
id The unique identifier used to unlock a user in the ManagementService context. Required when Service is ManagementService and Operation is unlockUser.

Output

The node outputs a JSON object containing the response from the Zitadel API for the unlockUser operation. This typically includes details about the unlocked user or confirmation of the unlock action.

No binary data output is produced by this node.

Example output structure (simplified):

{
  "userId": "string",
  "status": "unlocked",
  "message": "User has been successfully unlocked"
}

Dependencies

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

Troubleshooting

  • Missing or invalid API token: Ensure the Zitadel API token credential is correctly set up and has sufficient permissions.
  • Invalid user ID: Verify that the userId or id property corresponds to an existing user in the Zitadel system.
  • Operation not supported: If the selected service does not support the unlockUser operation, the node will return an empty JSON object.
  • JSON parsing errors: Input properties are parsed as JSON if possible; ensure string inputs are valid JSON or plain strings as expected.

Links and References

Discussion