ZitadelInstall

Overview

This node provides an interface to interact with the Zitadel API, a platform for identity and access management. It supports multiple services within Zitadel, such as user management, organization management, authentication, administration, and custom actions.

The specific operation removeOTPEmail under the "Default" resource is designed to remove or disable the OTP (One-Time Password) email method for a user. This can be useful in scenarios where you want to revoke a user's ability to authenticate via OTP sent to their email, for example, when deprecating legacy authentication methods or enforcing stricter security policies.

Practical examples:

• Disabling OTP email for a user who has switched to using a different multi-factor authentication method.
• Cleaning up user authentication methods during account deactivation or migration.

Properties

Output

The output JSON contains the response from the Zitadel API corresponding to the invoked operation. For removeOTPEmail, this will typically be an object indicating the success or failure of the removal request, possibly including metadata about the updated user state.

No binary data output is produced by this node.

Example output structure (simplified):

{
  "result": {
    // details about the OTP email removal operation
  }
}

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

• Common issues:

  • Invalid or missing API token: Ensure the API key credential is correctly set up and has sufficient permissions.
  • Incorrect userId: Verify that the user ID exists in Zitadel and is correctly formatted.
  • Using the wrong service for the operation: removeOTPEmail must be called with the "UserService" selected.

• Error messages:

  • Authorization errors: Check API token validity and scopes.
  • Not found errors: Confirm the user ID exists.
  • Parsing errors: Input parameters must be valid JSON or strings as expected.

Links and References

• Zitadel Official Documentation
• Zitadel API Reference
• n8n Documentation on Custom Nodes