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, the addIDPLink operation under the "Default" resource (mapped here as part of the UserService) enables linking an external Identity Provider (IDP) account to a user in Zitadel. This is useful for scenarios where you want to associate a user's Zitadel account with an external authentication provider, facilitating single sign-on or federated identity management.
Practical examples include:
- Linking a Google or Microsoft account as an IDP link to a Zitadel user.
- Associating corporate identity providers with user accounts for seamless login experiences.
- Managing user authentication sources programmatically within n8n 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 to whom the IDP link will be added. Required when Service is UserService and Operation is addIDPLink. |
| idpLink | The identifier or details of the external Identity Provider link to add to the user. Required when Service is UserService and Operation is addIDPLink. |
Output
The node outputs a JSON object representing the response from the Zitadel API after performing the requested operation. For the addIDPLink operation, this typically includes confirmation details about the newly created IDP link associated with the user.
No binary data output is produced by this node.
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 clients generated from Zitadel protobuf definitions to communicate with the API.
Troubleshooting
- Invalid or missing API token: Ensure that the Zitadel API token credential is correctly set up in n8n; otherwise, authorization errors will occur.
- Incorrect userId or idpLink values: Verify that the user ID exists in Zitadel and that the IDP link string is valid and formatted as expected by Zitadel.
- Operation not found: If the selected operation does not exist in the chosen service, the node returns an empty JSON object. Double-check the service and operation names.
- JSON parsing errors: Input properties are parsed as JSON if possible; malformed JSON strings in inputs may cause errors. Provide valid JSON or plain strings accordingly.