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 a user ID.

Common scenarios where this node is beneficial include:

• Verifying a user's phone number during onboarding or authentication flows.
• Automating phone verification steps in user management workflows.
• Integrating phone verification as part of multi-factor authentication processes.

For example, you might use this node to verify a phone number after a user receives a verification code via SMS, ensuring that the phone number is valid and linked to the correct user account.

Properties

Output

The node outputs a JSON object containing the response from the Zitadel API's verifyPhone method. This typically includes confirmation of whether the phone verification was successful or details about the verification status.

No binary data output is produced by this operation.

Example output structure (simplified):

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

(Note: Actual fields depend on Zitadel API response.)

Dependencies

• Requires an API authentication token (Personal Access Token) for Zitadel, configured in the node 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: Verify that the user ID exists and the verification code matches what was sent to the user.
• Network issues: Confirm network connectivity to the Zitadel API endpoint.
• Parsing errors: Input properties like userId and verificationCode must be strings; ensure no invalid JSON formatting is used.

Common error messages may include authorization failures or validation errors from Zitadel. Resolving these usually involves checking credentials, input correctness, and API permissions.

Links and References

• Zitadel Official Documentation
• Zitadel API Reference
• n8n Documentation on Credentials