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
setPhone
AI-generatedOverview
This node integrates with the Zitadel API, allowing users to perform various operations across multiple Zitadel services. Specifically, for the setPhone operation under the default resource, it updates a user's phone information in the UserService. This can be useful in scenarios where you need to programmatically update or verify user contact details within an identity management system.
Practical examples include:
- Updating a user's phone number after they provide a new one.
- Triggering verification codes to confirm the phone number's validity.
- Managing user contact information as part of onboarding or profile updates.
Properties
| Name | Meaning |
|---|---|
| Service | The Zitadel service to interact with. Options: UserService, OrganizationService, AuthService, ManagementService, AdminService, ZITADELActions, UserSchemaService. For setPhone, must be UserService. |
| userId | The unique identifier of the user whose phone number is being set. |
| phone | The phone number to assign to the user. |
| sendCode | A string indicating whether to send a verification code to the new phone number. |
| returnCode | A string indicating whether to return the verification code in the response. |
| isVerified | A string indicating whether the phone number should be marked as verified. |
All properties except "Service" are required when using the setPhone operation on the UserService.
Output
The node outputs a JSON object representing the response from the Zitadel API for the setPhone operation. This typically includes confirmation of the phone number update and may include verification code details depending on the input parameters (sendCode and returnCode). The exact structure depends on the Zitadel API response but generally reflects the updated user phone state.
No binary data output is produced by this operation.
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 internally to communicate with Zitadel services.
Troubleshooting
- Invalid or missing API token: Ensure that the Zitadel API token credential is correctly configured and has sufficient permissions.
- Incorrect property values: Make sure all required fields (
userId,phone,sendCode,returnCode,isVerified) are provided and formatted correctly. - Operation not found: If the selected operation does not exist for the chosen service, the node returns an empty JSON object.
- JSON parsing errors: Input properties are parsed as JSON if possible; invalid JSON strings will fallback to raw strings. Verify input formatting to avoid unexpected behavior.