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 interact with various Zitadel services programmatically. Specifically, the listIDPLinks operation under the "Default" resource (mapped here as the "UserService") fetches a list of Identity Provider (IDP) links associated with a given user. This is useful in scenarios where you want to retrieve external authentication links or federated identity connections tied to a user account.
Practical examples include:
- Auditing which external IDPs a user has linked to their Zitadel account.
- Displaying linked social login providers in a user management dashboard.
- Automating synchronization or cleanup of linked IDP accounts.
Properties
| Name | Meaning |
|---|---|
| Service | The Zitadel service to use. Options: UserService, OrganizationService, AuthService, ManagementService, AdminService, ZITADELActions, UserSchemaService. For this operation, select UserService. |
| userId | The unique identifier of the user whose IDP links you want to list. Required when using UserService and the listIDPLinks operation. |
| query | A JSON object specifying query parameters for listing IDP links. It supports: - limit: Number of results to return (default 10).- offset: Pagination offset (default 0).- order: Sorting order, e.g., "ASC". |
Output
The node outputs a JSON object containing the response from the Zitadel API's listIDPLinks method. This typically includes an array or collection of IDP link objects related to the specified user, along with metadata such as pagination info.
The exact structure depends on the Zitadel API response but generally includes fields like:
- IDP link identifiers
- Associated provider details
- Link status or timestamps
No binary data output is produced by this operation.
Dependencies
- Requires an API authentication token credential for Zitadel (referred generically as an API key credential).
- The node uses the Zitadel gRPC client libraries bundled within its dependencies.
- The base URL for the Zitadel API is set to
https://zitadel.studentcouncil.dk. - Proper configuration of the Zitadel API credentials in n8n is necessary for successful requests.
Troubleshooting
- Invalid or missing credentials: Ensure that the Zitadel API token is correctly configured and has sufficient permissions to access user IDP links.
- Malformed JSON in
queryproperty: Thequeryparameter must be valid JSON. Invalid JSON will cause parsing errors. Use proper JSON formatting. - User ID not found or invalid: Verify that the
userIdprovided exists in the Zitadel system. - Operation not supported: If selecting a service-operation combination not implemented, the node returns empty JSON.
- Network or connectivity issues: Confirm network access to
https://zitadel.studentcouncil.dkand that no firewall blocks the request.