ZitadelInstall

Overview

This node interacts with the Zitadel API, a platform for identity and access management. It allows users to call various services provided by Zitadel, such as user management, organization management, authentication, administration, and more.

Specifically, the resendEmailCode operation under the UserService resource triggers the resending of an email verification or confirmation code to a user identified by their user ID. This is useful in scenarios where a user did not receive the original email or the code expired, enabling seamless re-verification without manual intervention.

Practical examples:

• Resend a verification email to a newly registered user who missed the first email.
• Trigger a resend of a password reset or multi-factor authentication code.
• Automate user onboarding flows that require email confirmation.

Properties

Output

The node outputs a JSON object containing the response from the Zitadel API corresponding to the invoked operation. For the resendEmailCode operation, this will typically include confirmation details about the resend action, such as success status or error messages.

No binary data output is indicated.

Example output structure (simplified):

{
  "json": {
    // Response fields from Zitadel API for resendEmailCode
  }
}

Dependencies

• Requires an API key credential for authenticating with the Zitadel API.
• The node uses gRPC clients generated from Zitadel's protobuf definitions.
• The base URL for the Zitadel API is fixed as https://zitadel.studentcouncil.dk.
• The node internally creates an access token interceptor using the provided API key to authorize requests.

Troubleshooting

• Common issues:

  • Invalid or missing API key credential will cause authorization failures.
  • Incorrect or missing userId, sendCode, or returnCode parameters may result in errors from the API.
  • Network connectivity issues to the Zitadel endpoint can cause request failures.

• Error messages:

  • Authorization errors usually indicate invalid or expired API tokens; ensure the API key is valid and has necessary permissions.
  • Validation errors from Zitadel API may indicate malformed or missing input parameters; verify all required inputs are correctly set.
  • Timeout or connection errors suggest network problems; check connectivity and endpoint availability.

Links and References

• Zitadel Official Website
• Zitadel API Documentation
• gRPC Node.js Library

If you need further details on other operations or resources, please provide their names.