Zitadel

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 resendPhoneCode operation under the "Default" resource (mapped here as part of the UserService) is designed to resend a phone verification code to a user. This can be useful in scenarios where a user did not receive the original SMS code or the code expired, and you want to trigger sending a new one.

Practical examples:

• Resending a phone verification code during user signup or login flows.
• Triggering a new phone code if the user requests it from a frontend application.
• Automating phone verification retries in workflows that require strong user authentication.

Properties

Note: The last three properties (userId, sendCode, returnCode) are only shown when the selected Service is UserService and the Operation is resendPhoneCode.

Output

The node outputs the raw JSON response returned by the Zitadel API for the invoked operation. This JSON contains the result of the resendPhoneCode request, which typically includes confirmation of the code being resent or any error details.

No binary data output is produced by this node.

Dependencies

• Requires an API key credential for Zitadel (referred generically as an API token).
• The node uses gRPC clients generated from Zitadel's protobuf definitions to communicate with the Zitadel backend.
• The base URL for the Zitadel API is hardcoded as https://zitadel.studentcouncil.dk.
• The node expects the user to provide valid credentials with appropriate permissions to perform the requested operations.

Troubleshooting

• Common issues:

  • Invalid or missing API token will cause authorization failures.
  • Incorrect userId or parameters may lead to errors from the Zitadel API.
  • Network connectivity issues to the Zitadel endpoint will prevent successful calls.

• Error messages:

  • Authorization errors usually indicate invalid or expired API tokens; refresh or reconfigure credentials.
  • Validation errors from Zitadel indicate incorrect input parameters; verify userId, sendCode, and returnCode values.
  • Timeout or connection errors suggest network problems or incorrect endpoint configuration.

Links and References

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