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
Overview
This node integrates with the Zitadel API, allowing users to perform various operations on different Zitadel services. Specifically, for the addIDPLink operation under the "Default" resource (mapped here as the "UserService"), it adds an Identity Provider (IDP) link to a user account. This is useful in scenarios where you want to link external identity providers (like Google, Microsoft, or other OAuth/OpenID Connect providers) to a user's Zitadel profile, enabling single sign-on or federated authentication.
Practical examples include:
- Linking a new social login provider to an existing user.
- Managing user authentication methods by adding or removing IDP links.
- Automating user provisioning workflows that require associating external identities.
Properties
| Name | Meaning |
|---|---|
| Service | The Zitadel service to interact with. Options: UserService, OrganizationService, AuthService, ManagementService, AdminService, ZITADELActions, UserSchemaService. For this operation, use "UserService". |
| userId | The unique identifier of the user to whom the IDP link will be added. |
| idpLink | The IDP link string representing the external identity provider connection to add. |
Output
The node outputs a JSON object containing the response from the Zitadel API after attempting to add the IDP link. This typically includes details about the updated user or confirmation of the link addition. The exact structure depends on the Zitadel API response for the addIDPLink method.
No binary data output is produced by this node.
Dependencies
- Requires an API authentication token (Personal Access Token) for Zitadel, configured in n8n credentials.
- Depends on the Zitadel gRPC client libraries bundled within the node.
- Network access to the Zitadel API endpoint at
https://zitadel.studentcouncil.dk.
Troubleshooting
Common issues:
- Invalid or missing API token: Ensure the API key credential is correctly set up and has sufficient permissions.
- Incorrect
userIdoridpLink: Verify that the user exists and the IDP link format matches Zitadel's expected schema. - Network connectivity problems: Confirm that the n8n instance can reach the Zitadel API endpoint.
Error messages:
- Authorization errors usually indicate invalid or expired tokens; refresh or update credentials.
- Validation errors may occur if required parameters are missing or malformed; double-check input values.
- Unexpected API errors might require checking Zitadel service status or reviewing API usage limits.