Actions42
- getUserByID
- addHumanUser
- listUsers
- setEmail
- resendEmailCode
- verifyEmail
- setPhone
- removePhone
- resendPhoneCode
- verifyPhone
- updateHumanUser
- deactivateUser
- reactivateUser
- lockUser
- unlockUser
- deleteUser
- registerPasskey
- verifyPasskeyRegistration
- createPasskeyRegistrationLink
- listPasskeys
- removePasskey
- registerU2F
- verifyU2FRegistration
- removeU2F
- registerTOTP
- verifyTOTPRegistration
- removeTOTP
- addOTPSMS
- removeOTPSMS
- addOTPEmail
- removeOTPEmail
- startIdentityProviderIntent
- retrieveIdentityProviderIntent
- addIDPLink
- listIDPLinks
- removeIDPLink
- passwordReset
- setPassword
- listAuthenticationMethodTypes
- createInviteCode
- resendInviteCode
- verifyInviteCode
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 triggers the resending of an invitation code to a user. 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 code to onboard a new team member who missed the initial invite.
- Automating invite management workflows within an organization using Zitadel's user management services.
Properties
| Name | Meaning |
|---|---|
| Service | The Zitadel service to interact with. Options: UserService, OrganizationService, AuthService, ManagementService, AdminService, ZITADELActions, UserSchemaService. Default is UserService. |
| 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 node outputs a JSON object representing the response from the Zitadel API for the invoked operation. For resendInviteCode, this typically includes confirmation details about the resend action, such as status or metadata returned by the API.
No binary data output is produced by this node.
Example output structure (simplified):
{
"json": {
// Response fields from Zitadel API for resendInviteCode operation
}
}
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
Common issues:
- Invalid or missing API token: Ensure the Zitadel API key credential is correctly set up in n8n.
- Incorrect
userId: Verify that the user ID exists in Zitadel and is correctly formatted. - Network connectivity problems: Confirm that the n8n instance can reach the Zitadel API endpoint.
Error messages:
- Authorization errors usually indicate invalid or expired API tokens; refresh or reconfigure credentials.
- Validation errors may occur if required parameters like
userIdare missing or malformed. - API method not found errors suggest the selected operation does not exist for the chosen service; double-check the service-operation combination.