ZitadelInstall

Overview

This node integrates with the Zitadel API, allowing users to perform various operations across multiple Zitadel services. Specifically, the getUserByID operation fetches user details by their unique identifier from a selected service such as UserService or ManagementService.

Common scenarios include:

• Retrieving detailed user information for identity management.
• Integrating user data into workflows for access control or auditing.
• Automating user-related administrative tasks within an organization.

For example, you might use this node to get a user's profile by their ID from the UserService to sync user data with another system or to verify user attributes before granting access.

Properties

Output

The output JSON contains the full response object returned by the Zitadel API for the getUserByID request. This typically includes detailed user information such as identifiers, profile data, metadata, and status fields depending on the service queried.

No binary data output is produced by this node.

Example output structure (simplified):

{
  "id": "user-id",
  "profile": {
    "firstName": "John",
    "lastName": "Doe",
    "email": "john.doe@example.com"
  },
  "metadata": { ... },
  "status": "active"
}

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 missing API token: Ensure the API key credential is correctly set up and has sufficient permissions.
• Incorrect user ID: Verify that the provided user ID matches the expected format and exists in the selected service.
• Service-operation mismatch: Make sure the userId or id property is provided according to the selected service (UserService uses userId, ManagementService uses id).
• JSON parsing errors: Input parameters are parsed as JSON if possible; ensure string inputs are valid JSON or plain strings as required.
• Network issues: Confirm network connectivity to the Zitadel API endpoint.

Links and References

• Zitadel API Documentation
• Zitadel GitHub Repository
• n8n Documentation