Zitadel

Overview

This node integrates with the Zitadel API, allowing users to perform various operations across multiple Zitadel services. Specifically, for the verifyPhone operation under the default resource, it verifies a user's phone number by submitting a verification code associated with that user.

Common scenarios include:

• Confirming a user's phone number during registration or profile updates.
• Validating phone ownership as part of multi-factor authentication flows.
• Automating phone verification steps in user management workflows.

Practical example:

• A workflow where after creating a user, this node is used to verify their phone by providing the user ID and the received verification code, ensuring the phone number is confirmed before proceeding.

Properties

Output

The node outputs a JSON object representing the response from the Zitadel API for the invoked operation. For verifyPhone, this typically includes confirmation details about the verification status of the phone number.

The output structure is dynamic and directly reflects the API's response schema for the called method. No binary data output is produced by this node.

Example output snippet (conceptual):

{
  "verified": true,
  "userId": "string",
  "phoneNumber": "string",
  "message": "Phone number successfully verified"
}

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 the API key credential is correctly set up in n8n and has sufficient permissions.
• Incorrect userId or verificationCode: Double-check that the user ID exists and the verification code matches what was sent to the user.
• Network issues or endpoint unreachable: Verify network connectivity to the Zitadel API URL.
• Parsing errors on input parameters: Inputs are parsed as JSON if possible; ensure string inputs like verificationCode are valid strings and not malformed JSON.

Common error messages:

• Authorization errors indicating invalid or expired tokens.
• Validation errors if required parameters are missing or incorrect.
• gRPC communication errors if the service definitions or endpoints are misconfigured.

Links and References

• Zitadel Official Documentation
• Zitadel API Reference
• n8n Custom Node Development Guide