Actions42
- addHumanUser
- getUserByID
- 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
resendPhoneCode
AI-generatedOverview
This node interacts with the Zitadel API, a platform for identity and access management. Specifically, the resendPhoneCode operation under the "Default" resource (mapped to the "UserService") allows resending a phone verification code to a user. This is useful in scenarios where a user did not receive or lost their original phone verification code and needs it resent to complete authentication or verification processes.
Practical examples include:
- Resending a two-factor authentication (2FA) SMS code.
- Resending a phone number verification code during user registration or profile update.
- Triggering a resend of a phone-based login code in passwordless authentication flows.
Properties
| Name | Meaning |
|---|---|
| Service | The Zitadel service to use. Options: UserService, OrganizationService, AuthService, ManagementService, AdminService, ZITADELActions, UserSchemaService. For this operation, "UserService" is used. |
| userId | The unique identifier of the user to whom the phone code should be resent. |
| sendCode | The code or token that triggers sending the phone code. |
| returnCode | A code indicating whether the resend operation should return the sent code or confirmation. |
Output
The output JSON contains the response from the Zitadel API corresponding to the resendPhoneCode request. It reflects the result of the resend operation, which may include status information or confirmation details about the phone code being resent.
No binary data output is indicated by the source code.
Dependencies
- Requires an API authentication token (Personal Access Token) for Zitadel, provided via node credentials.
- Connects to the Zitadel API endpoint at
https://zitadel.studentcouncil.dk. - Uses gRPC client libraries (
nice-grpc) to communicate with Zitadel services. - The node depends on the Zitadel protobuf-generated service definitions bundled within the node.
Troubleshooting
- Common issues:
- Invalid or missing API token: Ensure the Zitadel API key credential is correctly configured.
- Incorrect
userId: Verify the user ID exists in the Zitadel system. - Malformed input parameters: The node attempts to parse JSON inputs; ensure string inputs are valid JSON if applicable.
- Error messages:
- Authorization errors typically indicate invalid or expired API tokens.
- Validation errors may occur if required parameters like
userId,sendCode, orreturnCodeare missing or malformed.
- To resolve errors, verify credentials, parameter correctness, and network connectivity to the Zitadel API endpoint.