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
verifyPhone
AI-generatedOverview
This node integrates with the Zitadel API, allowing users to perform various operations across multiple Zitadel services such as user management, organization management, authentication, and administration. Specifically, for the verifyPhone operation under the UserService, it verifies a user's phone number by submitting a verification code.
Common scenarios include:
- Verifying a user's phone number during registration or profile update.
- Confirming phone ownership as part of multi-factor authentication setup.
- Validating phone numbers before enabling phone-based notifications or alerts.
Practical example:
- A workflow that triggers when a user submits a phone verification form, using this node to verify the submitted code against Zitadel's user service.
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 whose phone number is being verified. Required when Service is UserService and Operation is verifyPhone. |
| verificationCode | The verification code sent to the user's phone that needs to be validated. Required when Service is UserService and Operation is verifyPhone. |
Output
The node outputs a JSON object containing the response from the Zitadel API corresponding to the invoked operation. For verifyPhone, this typically includes confirmation details about the verification status.
No binary data output is produced by this node.
Example output structure (simplified):
{
"verified": true,
"userId": "string",
"message": "Phone number verified successfully"
}
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
- Invalid or expired verification code: The API may return an error if the verification code is incorrect or expired. Ensure the code is copied correctly and used promptly.
- Missing or invalid userId: Verification requires a valid user ID. Confirm that the userId parameter is correct and corresponds to an existing user.
- Authentication errors: If the API token is missing or invalid, the node will fail to authenticate. Verify that the API key credential is properly set up in n8n.
- Network issues: Connectivity problems to the Zitadel endpoint can cause failures. Check network access and endpoint availability.