Actions42
- listUsers
- registerTOTP
- addHumanUser
- getUserByID
- setEmail
- resendEmailCode
- verifyEmail
- setPhone
- removePhone
- resendPhoneCode
- verifyPhone
- updateHumanUser
- deactivateUser
- reactivateUser
- lockUser
- unlockUser
- deleteUser
- registerPasskey
- verifyPasskeyRegistration
- createPasskeyRegistrationLink
- listPasskeys
- removePasskey
- registerU2F
- verifyU2FRegistration
- removeU2F
- 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, it adds an Identity Provider (IDP) link to a user in the UserService. This is useful when you want to link external identity providers (like Google, Microsoft, or other OAuth/OpenID Connect providers) to a user's account in Zitadel, enabling single sign-on or federated authentication scenarios.
Practical examples include:
- Linking a new social login provider to an existing user account.
- Associating enterprise identity providers for corporate users.
- Managing user authentication methods programmatically within n8n workflows.
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 that represents the external identity provider connection to add. |
Output
The node outputs a JSON object representing the response from the Zitadel API after performing the addIDPLink operation. This typically includes confirmation details about the newly linked IDP or the updated user information.
No binary data output is produced by this node.
Example output structure (simplified):
{
"idpLink": "string",
"userId": "string",
"status": "linked"
}
Dependencies
- Requires an API authentication token (Personal Access Token) for Zitadel, configured in n8n credentials.
- Uses the Zitadel gRPC client libraries bundled with the node.
- Network access to the Zitadel API endpoint at
https://zitadel.studentcouncil.dk.
Troubleshooting
- Invalid Credentials: If the API token is missing or invalid, the node will fail to authenticate. Ensure the correct API key/token is set up in n8n credentials.
- Invalid userId or idpLink: Providing incorrect or malformed values may cause the API to reject the request. Verify that the user ID exists and the IDP link format matches Zitadel's requirements.
- Operation Not Found: Selecting an unsupported operation for the chosen service will result in no action. Confirm that
addIDPLinkis used only withUserService. - JSON Parsing Errors: Input properties are parsed as JSON if possible; malformed JSON strings will cause errors. Provide plain strings for simple fields like
userIdandidpLink.