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
startIdentityProviderIntent
AI-generatedOverview
This node provides an interface to interact with the Zitadel API, a platform for identity and access management. It allows users to call various services offered by Zitadel, such as user management, organization management, authentication, administration, actions, and user schema services.
The specific operation startIdentityProviderIntent under the UserService resource initiates an identity provider intent, which is typically used in scenarios where you want to start or trigger an identity provider flow (e.g., SSO login or linking an external identity provider) within Zitadel.
Practical examples:
- Starting an identity provider intent to link a new external identity provider for a user.
- Initiating a login flow via an external identity provider.
- Managing identity providers programmatically as part of an automated workflow.
Properties
| Name | Meaning |
|---|---|
| Service | The Zitadel service to interact with. Options: UserService, OrganizationService, AuthService, ManagementService, AdminService, ZITADELActions, UserSchemaService. Default is UserService. |
| idpId | The identifier of the identity provider to start the intent for. Required when using UserService and the startIdentityProviderIntent operation. |
| urls | URLs related to the identity provider intent, likely callback or redirect URLs. Required for the startIdentityProviderIntent operation. |
| ldap | LDAP configuration or identifier related to the identity provider intent. Required for the startIdentityProviderIntent operation. |
Output
The node outputs a JSON object containing the response from the Zitadel API corresponding to the invoked operation. For startIdentityProviderIntent, this will include details about the initiated identity provider intent, such as tokens, URLs, or status information returned by the Zitadel service.
If the operation returns binary data, it would be included in the output accordingly, but based on the static code analysis, this node primarily outputs JSON responses.
Dependencies
- Requires an API authentication token (Personal Access Token) for Zitadel, provided via node credentials.
- Connects to the Zitadel API endpoint at
https://zitadel.studentcouncil.dk. - Uses gRPC client libraries (
nice-grpc) to communicate with Zitadel services. - The node depends on generated Zitadel service definitions bundled with the node.
Troubleshooting
- Invalid or missing API token: Ensure that the Zitadel API token credential is correctly configured and has sufficient permissions.
- Incorrect property values: The properties
idpId,urls, andldapmust be valid strings and properly formatted. Invalid JSON or empty required fields may cause errors. - Operation not found: If an unsupported operation is selected, the node returns an empty JSON object.
- Parsing errors: The node attempts to parse input parameters as JSON; malformed JSON strings will fallback to raw string usage but may cause unexpected behavior if the API expects structured data.