Zitadel

Overview

This node interacts with the Zitadel API, a platform for identity and access management. It allows users to call various services provided by Zitadel, such as user management, organization management, authentication, administration, and more.

Specifically, the resendInviteCode operation under the "Default" resource (mapped here as part of the UserService) triggers the resending of an invitation code to a user identified by their user ID. This is useful in scenarios where a user did not receive or lost their original invite email and needs a new invitation sent.

Practical examples:

• Resend an invite code to a newly added user who never received the initial invitation.
• Automate re-inviting users who have not completed their registration process.

Properties

Output

The output is a JSON object containing the response from the Zitadel API for the invoked operation. For the resendInviteCode operation, this typically includes confirmation details about the resend action, such as status or any metadata returned by the API.

No binary data output is indicated by the source code.

Example output structure (simplified):

{
  "json": {
    // Response fields from Zitadel's resendInviteCode API call
  }
}

Dependencies

• Requires an API key credential (referred to generically as an API token) for authenticating requests to the Zitadel API.
• Uses gRPC clients generated from Zitadel's protobuf definitions to communicate with the API endpoints.
• The base URL for the API calls is https://zitadel.studentcouncil.dk.
• The node expects the API token to be available via n8n credentials named generically as Zitadel credentials.

Troubleshooting

• Common issues:

  • Invalid or missing API token: Ensure that the API key credential is correctly configured in n8n.
  • Incorrect userId: Verify that the userId provided exists in the Zitadel system.
  • Network or endpoint errors: Confirm network connectivity and that the Zitadel API endpoint is reachable.

• Error messages:

  • Authorization errors usually indicate invalid or expired API tokens; refresh or update the token.
  • Validation errors may occur if required parameters like userId are missing or malformed.
  • If the operation name or service is incorrect, the node will return an empty JSON object.

Links and References

• Zitadel Official Documentation
• Zitadel API Reference
• gRPC Protocol Buffers