Zitadel icon

Zitadel

Interact with the Zitadel API

verifyEmail

AI-generated

Overview

This node integrates with the Zitadel API, allowing users to perform various operations across multiple Zitadel services. Specifically, for the verifyEmail operation under the default resource, it verifies a user's email address by submitting a user ID and a verification code. This is useful in workflows where email verification status needs to be confirmed programmatically, such as during user onboarding or account recovery processes.

Practical examples:

  • Automatically verify a user's email after they submit a verification code received via email.
  • Integrate email verification into a larger identity management workflow.
  • Trigger subsequent actions only if the email verification succeeds.

Properties

Name Meaning
Service The Zitadel service to interact with. Options: UserService, OrganizationService, AuthService, ManagementService, AdminService, ZITADELActions, UserSchemaService. For this operation, must be "UserService".
userId The unique identifier of the user whose email is being verified.
verificationCode The verification code sent to the user's email that confirms ownership of the email address.

Output

The node outputs a JSON object representing the response from the Zitadel API's verifyEmail method. This typically includes confirmation details about the verification status. The exact structure depends on the Zitadel API response but generally contains fields indicating success or failure of the verification.

No binary data output is produced by this node.

Example output JSON (simplified):

{
  "result": "success",
  "userId": "string",
  "verified": true
}

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 verification code: If the verification code is incorrect or expired, the API will return an error. Ensure the code is copied correctly and still valid.
  • Incorrect userId: Providing a wrong or non-existent userId will cause the verification to fail.
  • Authentication errors: Missing or invalid API tokens will prevent the node from connecting to Zitadel. Verify that the API key credential is properly set up.
  • JSON parsing errors: Input properties are parsed as JSON if possible; malformed JSON input will cause errors. Provide plain strings for simple fields like userId and verificationCode.
  • Operation not supported: Selecting an operation not available in the chosen service will result in no action. Confirm that verifyEmail is used with UserService.

Links and References

Discussion