Zitadel icon

Zitadel

Interact with the Zitadel API

Overview

This node interacts with the Zitadel API, a platform for identity and access management. Specifically, the verifyEmail operation under the default resource (service) allows verifying a user's email by providing their user ID and a verification code. This is useful in workflows where you need to confirm that a user's email address has been validated, such as during user registration or account recovery processes.

Practical examples:

  • Automatically verify a user's email after they submit a verification code received via email.
  • Integrate email verification status checks into onboarding workflows.
  • Trigger subsequent actions only if the email verification succeeds.

Properties

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

Output

The output JSON contains the response from the Zitadel API's verifyEmail method. It typically includes details about the verification result, such as success status or error information. The exact structure depends on the Zitadel API response schema for this operation.

No binary data output is produced by this node.

Example output JSON snippet:

{
  "result": {
    "verified": true,
    "userId": "example-user-id"
  }
}

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 bundled within the node for communication.

Troubleshooting

  • Invalid or missing verification code: Ensure the verification code provided matches the one sent to the user's email.
  • Incorrect userId: Verify that the user ID exists and is correct.
  • Authentication errors: Confirm that the API token credential is valid and has sufficient permissions.
  • Network issues: Check connectivity to the Zitadel API endpoint.
  • Parsing errors: Input parameters are parsed as JSON if possible; ensure string inputs are correctly formatted.

Common error messages may include authorization failures, invalid parameters, or network timeouts. Resolving these usually involves checking credentials, input values, and network status.

Links and References

Discussion