Zitadel icon

Zitadel

Interact with the Zitadel API
Join our community

Actions42

Overview

This node integrates with the Zitadel API, allowing users to perform various operations across multiple Zitadel services. Specifically, the resendInviteCode operation under the "Default" resource enables resending 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 include:

  • Resending an invite to a newly added team member who hasn't activated their account.
  • Triggering a resend of an invite after correcting user details or permissions.

Properties

Name Meaning
Service The Zitadel service to interact with. Options: UserService, OrganizationService, AuthService, ManagementService, AdminService, ZITADELActions, UserSchemaService. For this operation, "UserService" is used.
userId The unique identifier of the user to whom the invite code should be resent. Required when Service is "UserService" and Operation is "resendInviteCode".

Output

The output JSON contains the raw response from the Zitadel API for the resendInviteCode operation. It typically includes confirmation or status information about the resend action. The exact structure depends on the Zitadel API response schema for this method.

No binary data output is produced by this node.

Example output snippet (conceptual):

{
  "status": "success",
  "message": "Invite code resent successfully",
  "userId": "abc123"
}

Dependencies

  • Requires an API authentication token credential for Zitadel (referred generically as an API key credential).
  • 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 user ID: Ensure the userId property is correctly set and corresponds to an existing user.
    • Authentication errors: Verify that the API token credential is valid and has sufficient permissions.
    • Network or connectivity problems: Confirm access to the Zitadel API endpoint.

  • Error messages:

    • Authorization failures usually indicate invalid or expired API tokens; refresh or update credentials.
    • "Method not found" errors may occur if the operation name is incorrect or unsupported by the selected service.
    • JSON parsing errors can happen if input parameters are malformed; ensure correct formatting.

Links and References

Discussion