ZitadelInstall

Overview

This node provides an interface to interact with the Zitadel API, a platform for identity and access management. It supports multiple services such as UserService, OrganizationService, AuthService, ManagementService, AdminService, ZITADELActions, and UserSchemaService. The node allows performing various operations on these services by calling their respective API methods.

Specifically, for the removeOTPEmail operation under the UserService resource, the node removes the OTP (One-Time Password) email associated with a user identified by userId. This can be useful in scenarios where you want to disable or reset multi-factor authentication via email for a user.

Practical examples:

• Removing a user's OTP email after they lose access to their email account.
• Resetting a user's two-factor authentication setup.
• Managing user security settings programmatically within an automated workflow.

Properties

Output

The output JSON contains the raw response from the Zitadel API method called for the selected operation. For removeOTPEmail, this will typically be an object indicating success or failure of the removal request. The exact structure depends on the Zitadel API response but generally includes status information.

No binary data output is produced by this node.

Example output JSON snippet:

{
  "result": "success"
}

(Note: Actual fields depend on Zitadel's 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

• Authentication errors: Ensure the API token credential is valid and has sufficient permissions.
• Invalid userId: If the user ID does not exist or is malformed, the API call will fail. Verify the userId input.
• Operation not found: Selecting an unsupported operation for a service will result in no action; ensure correct operation name.
• JSON parsing errors: Input parameters are parsed as JSON if applicable; invalid JSON strings will cause errors. Provide valid JSON or plain strings as required.
• Network issues: Connectivity problems to the Zitadel API endpoint will cause failures; check network and endpoint availability.

Links and References

• Zitadel Official Documentation
• Zitadel API Reference
• n8n Documentation