ZitadelInstall

Overview

This node provides an interface to interact with the Zitadel API, a platform for identity and access management. Specifically, the reactivateUser operation under the "Default" resource allows reactivating a user account by calling the appropriate service method in Zitadel.

Common scenarios where this node is useful include:

• Reactivating a previously deactivated or suspended user account in an organization.
• Automating user lifecycle management workflows where users may need to be re-enabled after being disabled.
• Integrating Zitadel user management into broader automation pipelines within n8n.

For example, you could use this node to automatically reactivate a user when they complete a certain onboarding step or regain access rights after a temporary suspension.

Properties

Note: The property shown depends on the selected service:

• If UserService is selected, userId must be provided.
• If ManagementService is selected, id must be provided.

Output

The node outputs the raw JSON response from the Zitadel API corresponding to the reactivateUser operation. This typically includes details about the reactivated user or confirmation of the action.

The output structure is:

{
  "json": {
    // Response object returned by the Zitadel API's reactivateUser method
  }
}

No binary data output is produced by this node.

Dependencies

• Requires an API authentication token (Personal Access Token) for Zitadel, configured as credentials in n8n.
• Connects to the Zitadel API endpoint at https://zitadel.studentcouncil.dk.
• Uses gRPC client libraries internally to communicate with Zitadel services.

Troubleshooting

• Missing or invalid API token: Ensure that the Zitadel API token credential is correctly set up and has sufficient permissions to perform user reactivation.
• Incorrect user ID: Verify that the userId or id parameter matches an existing user in Zitadel; otherwise, the API will return an error.
• Service-operation mismatch: Make sure the selected service supports the reactivateUser operation and that the correct input property (userId or id) is provided accordingly.
• JSON parsing errors: Input parameters are parsed as JSON if possible; ensure that string inputs are valid JSON or plain strings as expected.

Links and References

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