ZitadelInstall

Overview

This node integrates with the Zitadel API to perform various operations on Zitadel services. Specifically, for the updateHumanUser operation under the default resource, it updates details of a human user in the UserService. This is useful in scenarios where you need to programmatically modify user information such as username, profile, email, phone number, and password within an identity management system.

Practical examples include:

• Updating user contact details after a profile change request.
• Resetting or changing a user's password securely.
• Synchronizing user data from another system into Zitadel.

Properties

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

Output

The node outputs a single JSON object representing the response from the Zitadel API after attempting to update the human user. This typically includes confirmation of the update or details about the updated user entity.

No binary data output is produced by this operation.

Example output structure (simplified):

{
  "id": "string",
  "username": "string",
  "email": "string",
  "phone": "string",
  "profile": "string",
  // other user-related fields returned by the API
}

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

• Invalid or missing API token: Ensure that the Zitadel API token credential is correctly set up and has sufficient permissions to update users.
• Malformed JSON in profile field: The profile property expects a JSON string; invalid JSON will cause parsing errors.
• User not found: If the provided userId does not exist, the API will return an error indicating the user cannot be found.
• Permission denied: The API token must have rights to update user information; otherwise, permission errors will occur.
• Parsing errors: Input fields are parsed as JSON if possible; ensure strings meant to be JSON are valid.

Links and References

• Zitadel API Documentation
• Zitadel User Management Concepts
• n8n Documentation - Creating Custom Nodes