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
Overview
This node integrates with the Zitadel API, allowing users to interact with various Zitadel services programmatically. Specifically, for the startIdentityProviderIntent operation under the default resource, it initiates an identity provider intent within the UserService. This is useful in scenarios where you want to start or trigger authentication or identity provider workflows, such as linking external identity providers or starting login flows.
Practical examples include:
- Starting a Single Sign-On (SSO) process with an external identity provider.
- Initiating identity federation setups.
- Automating user authentication intents in custom workflows.
Properties
| Name | Meaning |
|---|---|
| Service | The Zitadel service to use. Options: UserService, OrganizationService, AuthService, ManagementService, AdminService, ZITADELActions, UserSchemaService. For this operation, select "UserService". |
| idpId | The identifier of the identity provider to start the intent for. |
| urls | URLs related to the identity provider intent, likely callback or redirect URLs. |
| ldap | LDAP configuration or identifier related to the identity provider intent. |
Output
The output is a JSON object representing the response from the Zitadel API for the invoked operation. It contains the data returned by the startIdentityProviderIntent method of the UserService, which typically includes details about the initiated identity provider intent, such as status, tokens, or URLs needed to continue the authentication flow.
No binary data output is indicated.
Dependencies
- Requires an API authentication token credential for Zitadel (referred generically as an API key credential).
- Uses the Zitadel gRPC client libraries bundled with the node.
- Connects to the Zitadel API endpoint at
https://zitadel.studentcouncil.dk. - The node uses an access token interceptor to attach the bearer token to requests.
Troubleshooting
- Common issues:
- Invalid or missing API authentication token will cause authorization failures.
- Incorrect or malformed JSON input for properties like
urlsorldapmay cause parsing errors. - Using an unsupported service or operation combination will result in no action or empty output.
- Error messages:
- Authorization errors: Ensure the API token credential is correctly configured and valid.
- JSON parse errors: Verify that inputs for complex fields are valid JSON strings or simple strings as expected.
- Method not found: Confirm that the selected service and operation exist and are supported.