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 interacts with the Zitadel API to perform various operations across multiple services such as UserService, OrganizationService, AuthService, ManagementService, AdminService, ZITADELActions, and UserSchemaService. Specifically, for the resendPhoneCode operation under the UserService resource, it resends a phone verification code to a user.
Common scenarios where this node is beneficial include:
- Resending a phone verification code when a user did not receive or lost the original code.
- Automating user phone verification workflows in identity management systems.
- Integrating Zitadel's user management capabilities into custom automation pipelines.
Practical example:
- A workflow that triggers when a user requests a new phone verification code, using this node to resend the code automatically without manual intervention.
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 phone code should be resent. (Required for resendPhoneCode operation in UserService) |
| sendCode | The code or flag indicating sending behavior for the phone code resend request. (Required for resendPhoneCode operation in UserService) |
| returnCode | The code or flag indicating whether to return the code after resending. (Required for resendPhoneCode operation in UserService) |
Output
The node outputs a JSON object containing the response from the Zitadel API corresponding to the invoked operation. For resendPhoneCode, this will typically include confirmation details about the resend action, such as success status or any returned codes if requested.
No binary data output is produced by this node.
Example output structure (simplified):
{
"success": true,
"message": "Phone code resent successfully",
"code": "123456" // if returnCode was requested
}
Dependencies
- Requires an API authentication token credential for Zitadel (referred generically as an API key credential).
- The node uses gRPC clients generated from Zitadel's protobuf definitions to communicate with the Zitadel API endpoint at
https://zitadel.studentcouncil.dk. - No additional external dependencies beyond the bundled Zitadel client libraries.
Troubleshooting
- Common issues:
- Invalid or missing API authentication token will cause authorization failures.
- Incorrect
userIdmay result in errors indicating the user does not exist. - Malformed JSON input for parameters may cause parsing errors.
- Error messages:
- Authorization errors: Ensure the API token credential is correctly configured and has sufficient permissions.
- User not found: Verify the
userIdis correct and exists in the Zitadel system. - JSON parse errors: Check that all input parameters are valid JSON strings or plain strings as expected.
- To resolve issues, verify credentials, parameter correctness, and network connectivity to the Zitadel API endpoint.