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
removePhone
AI-generatedOverview
This node integrates with the Zitadel API, allowing users to perform various operations across multiple Zitadel services. Specifically, for the removePhone operation under the default resource, it interacts with the UserService to remove a phone number associated with a user.
Common scenarios where this node is beneficial include:
- Managing user contact information programmatically.
- Automating user profile updates in Zitadel.
- Integrating Zitadel user management into workflows that require dynamic modification of user data.
For example, an organization might use this node to automatically remove outdated or incorrect phone numbers from user profiles as part of a data cleanup process.
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 will be removed. Required when Service is UserService and Operation is removePhone. |
Output
The output JSON contains the response from the Zitadel API corresponding to the invoked operation. For the removePhone operation, the output JSON will reflect the result of the phone removal request, typically including confirmation details or status information about the update.
No binary data output is produced by this node.
Example output structure (simplified):
{
"json": {
// Response fields from Zitadel's removePhone 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
- Authentication errors: Ensure the API token credential is valid and has sufficient permissions.
- Invalid userId: Verify that the provided
userIdexists in Zitadel; otherwise, the operation may fail or return an error. - 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 parameters are parsed as JSON if possible; malformed JSON inputs can cause failures. Provide valid JSON strings or plain values accordingly.