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
listIDPLinks
AI-generatedOverview
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 part of the UserService) retrieves a list of Identity Provider (IDP) links associated with a given user. This is useful in scenarios where you want to manage or audit external identity providers linked to user accounts within Zitadel.
Practical examples include:
- Fetching all external login providers linked to a user for auditing purposes.
- Displaying linked IDPs in a user management dashboard.
- Automating workflows that depend on the user's linked identity providers.
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. |
| query | JSON object specifying query parameters for listing IDP links. Includes: |
- limit: Number of results to return (e.g., 10). |
|
- offset: Pagination offset (e.g., 0). |
|
- order: Sorting order, e.g., "ASC" or "DESC". |
Output
The node outputs a JSON object containing the response from the Zitadel API's listIDPLinks method. This typically includes an array of IDP link objects related to the specified user, along with metadata such as pagination info.
The output structure looks like:
{
// Response fields depend on Zitadel's API schema for listIDPLinks
"links": [
{
"idpId": "string",
"userId": "string",
"linkedAt": "timestamp",
// other relevant IDP link details
}
],
"totalResult": number,
"limit": number,
"offset": number
}
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 client libraries internally to communicate with Zitadel services.
Troubleshooting
- Invalid or missing API token: Ensure the Zitadel API token credential is correctly set up and has sufficient permissions.
- Malformed JSON in
queryproperty: Thequeryparameter must be valid JSON. Errors parsing this will cause failures. Use proper JSON formatting. - User ID not found: If the provided
userIddoes not exist, the API may return an error or empty result. - Network issues: Verify connectivity to the Zitadel API endpoint.
- Operation not supported: Selecting an operation not available in the chosen service will result in no action.