ZitadelInstall

Overview

This node integrates with the Zitadel API, allowing users to perform various operations across multiple Zitadel services. Specifically, the removeOTPSMS operation under the "Default" resource (mapped here as a service-operation pair) enables removing or disabling OTP SMS settings for a user in the UserService.

Common scenarios where this node is beneficial include:

• Managing user authentication methods by programmatically disabling OTP via SMS.
• Automating user security settings updates within an identity management workflow.
• Integrating Zitadel user management into broader automation pipelines.

For example, you could use this node to remove OTP SMS for a user after they switch to a different multi-factor authentication method, ensuring their account security settings remain consistent.

Properties

Output

The node outputs a JSON object representing the response from the Zitadel API for the invoked operation. For removeOTPSMS, this typically includes confirmation details about the removal action or the updated user state related to OTP SMS.

The output structure is dynamic and directly reflects the API response shape of the called method. No binary data output is produced by this node.

Example output snippet (conceptual):

{
  "result": {
    "userId": "string",
    "otpSmsRemoved": true,
    "message": "OTP SMS removed successfully"
  }
}

Dependencies

• Requires an API authentication token credential for Zitadel (referred generically as an API key credential).
• The node uses gRPC clients generated from Zitadel's protobuf definitions to communicate with the Zitadel API endpoint at https://zitadel.studentcouncil.dk.
• Proper configuration of the Zitadel API credentials in n8n is necessary for successful execution.

Troubleshooting

• Authentication errors: If the node fails due to authorization issues, verify that the API token credential is valid and has sufficient permissions.
• Invalid userId: Ensure the userId provided exists in the Zitadel system; otherwise, the API will return an error indicating the user was not found.
• Operation not supported: Selecting a service-operation combination that does not exist or is misspelled will result in no action or an error.
• JSON parsing errors: Input parameters are parsed as JSON if possible; malformed JSON inputs can cause failures. Provide plain strings where appropriate.

Links and References

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