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
removeIDPLink
AI-generatedOverview
This node integrates with the Zitadel API, allowing users to perform various operations on different Zitadel services. Specifically, for the removeIDPLink operation under the UserService resource, it removes a linked Identity Provider (IDP) connection from a user account. This is useful in scenarios where an administrator or system needs to unlink external authentication providers (like Google, Microsoft, etc.) from a user's profile.
Practical examples include:
- Removing a social login link from a user who no longer wants to authenticate via that provider.
- Cleaning up linked IDPs when deactivating or migrating user accounts.
- Managing user identity connections programmatically as part of user lifecycle management.
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 from whom the IDP link will be removed. |
| idpId | The identifier of the Identity Provider (IDP) to unlink from the user. |
| linkedUserId | The identifier of the linked user account within the IDP to remove. |
Output
The node outputs a JSON object representing the response from the Zitadel API after attempting to remove the IDP link. The exact structure depends on the Zitadel API's response schema for this operation but generally includes confirmation of success or details about the unlinked IDP.
No binary data output is produced by this 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
Common issues:
- Invalid or missing API token: Ensure the Zitadel API key credential is correctly set up and has sufficient permissions.
- Incorrect
userId,idpId, orlinkedUserId: Verify these identifiers are accurate and correspond to existing entities in Zitadel. - Network connectivity problems: Confirm that the n8n instance can reach the Zitadel API endpoint.
Error messages:
- Authorization errors typically indicate invalid or expired tokens; refresh or update credentials.
- Not found errors suggest the specified user or IDP link does not exist; double-check input values.
- Parsing errors may occur if input parameters are malformed JSON; ensure inputs are valid strings or JSON objects as expected.