Actions42
- getUserByID
- addHumanUser
- 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
Overview
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 link between a user and an Identity Provider (IDP). This is useful in scenarios where you want to unlink a user's account from an external authentication provider, such as when a user no longer wants to use that IDP for login or when cleaning up linked accounts.
Practical examples:
- Unlinking a Google or GitHub login from a user's Zitadel account.
- Removing an outdated or compromised external identity provider link.
- Managing user authentication methods programmatically within workflows.
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 IDP link will be removed. Required for removeIDPLink operation under UserService. |
| idpId | The identifier of the Identity Provider (IDP) to unlink from the user. Required for removeIDPLink operation under UserService. |
| linkedUserId | The identifier of the linked user account in the IDP system. Required for removeIDPLink operation under UserService. |
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 for this operation but generally includes confirmation of the unlinking action or error details if the operation failed.
No binary data output is produced by this node.
Example output JSON structure (simplified):
{
"details": {
"userId": "string",
"idpId": "string",
"linkedUserId": "string",
"status": "success"
}
}
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 in n8n.
- 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 API tokens; refresh or reconfigure 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 strings; ensure inputs are valid strings or JSON objects as expected.