Zitadel

Overview

This node integrates with the Zitadel API, allowing users to perform various operations across multiple Zitadel services. Specifically, for the verifyInviteCode operation under the default resource, it verifies a user's invite code by sending the user ID and verification code to the Zitadel UserService.

Common scenarios where this node is beneficial include:

• Automating user onboarding workflows by verifying invite codes programmatically.
• Integrating Zitadel's identity management features into custom automation pipelines.
• Validating user invitations in bulk or as part of a larger user management process.

For example, you might use this node to verify that a newly invited user has a valid invite code before granting them access to your application.

Properties

Output

The node outputs a JSON object containing the response from the Zitadel API for the invoked operation. For verifyInviteCode, the output JSON will contain the result of the verification request, which typically includes status information about whether the invite code was successfully verified.

If the operation returns binary data (not applicable here), the node would provide it accordingly, but this operation deals only with JSON responses.

Example output structure (simplified):

{
  "verified": true,
  "userId": "string",
  "message": "Invite code verified successfully"
}

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

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 expired verification code: The API may return an error if the invite code is invalid or expired. Ensure the code is correct and still valid.
• Missing or incorrect userId: Verification requires a valid user ID. Confirm the userId parameter matches an existing user.
• Authentication errors: If the API token is missing or invalid, the node will fail to authenticate. Verify the API key credential is correctly set up.
• JSON parsing errors: Input parameters are parsed as JSON if possible; malformed JSON strings can cause errors. Provide plain strings for simple values like userId and verificationCode.
• Operation not found: Selecting an unsupported operation for the chosen service will result in no action. Ensure the operation name matches those supported by the selected service.

Links and References

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