Zitadel

Overview

This node integrates with the Zitadel API to perform various operations across multiple services such as UserService, OrganizationService, AuthService, ManagementService, AdminService, ZITADELActions, and UserSchemaService. Specifically, for the updateHumanUser operation under the UserService resource, it updates the details of a human user in the Zitadel system.

Typical use cases include:

• Updating user profile information like username, email, phone number, and password.
• Managing user accounts programmatically within an organization's identity management system.
• Automating user data synchronization between external systems and Zitadel.

For example, you might use this node to update a user's contact details or reset their password as part of an automated workflow triggered by an HR system or a customer support tool.

Properties

All properties except "Service" are required when performing the updateHumanUser operation.

Output

The node outputs a JSON object representing the response from the Zitadel API after attempting to update the human user. This typically includes confirmation of the updated user data or any relevant metadata returned by the API.

No binary data output is produced by this node.

Example output structure (simplified):

{
  "userId": "string",
  "username": "string",
  "profile": "string",
  "email": "string",
  "phone": "string",
  "updatedAt": "timestamp"
}

Dependencies

• Requires an API authentication token (Personal Access Token) configured in the node credentials to authorize requests to the Zitadel API.
• The node uses gRPC clients generated from Zitadel's protobuf definitions to communicate with the API endpoint at https://zitadel.studentcouncil.dk.
• No additional external dependencies beyond the Zitadel API and its authentication are needed.

Troubleshooting

• Invalid Credentials: If the API token is missing or invalid, the node will fail to authenticate. Ensure that a valid API key credential is configured.
• Missing Required Parameters: All required fields (userId, username, profile, email, phone, password) must be provided for the updateHumanUser operation. Omitting any will cause errors.
• JSON Parsing Errors: Input parameters are parsed as JSON if possible. Malformed JSON strings in inputs may cause parsing failures. Provide plain strings where appropriate.
• API Errors: The Zitadel API may return errors if the user ID does not exist or if the update violates validation rules (e.g., invalid email format). Review error messages and verify input correctness.
• Network Issues: Connectivity problems to the Zitadel API endpoint can cause timeouts or failures. Verify network access and endpoint availability.

Links and References

• Zitadel Official Documentation
• Zitadel API Reference
• n8n Documentation on Creating Custom Nodes