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 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 node is useful in scenarios where you want to automate or integrate Zitadel operations within your workflows, such as creating or managing users, organizations, or handling authentication tasks.
For example, you could use this node to:
- Create or update users in Zitadel.
- Manage organizational data.
- Perform authentication-related operations.
- Trigger or handle custom actions defined in Zitadel.
- Work with user schemas for custom attributes.
Properties
| Name | Meaning |
|---|---|
| Service | Select which Zitadel service to interact with. Options: UserService, OrganizationService, AuthService, ManagementService, AdminService, ZITADELActions, UserSchemaService. This determines the API endpoint group used. |
| Operation | Choose the specific operation (method) to execute on the selected service. The available operations depend on the chosen service and are dynamically populated based on the service's methods. |
| [Dynamic properties] | Depending on the selected service and operation, additional input fields appear corresponding to the parameters required by that operation. These can be JSON strings or simple strings representing request payloads or query parameters. |
Output
The node outputs the raw JSON response from the Zitadel API call under the json field of the output item. The structure of this JSON depends entirely on the selected service and operation, reflecting the API response format of Zitadel.
No binary data output is produced by this node.
Dependencies
- Requires an API authentication token credential for Zitadel (referred generically as "an API key credential").
- Uses the
nice-grpclibrary internally to communicate with Zitadel gRPC services. - The base URL for the Zitadel API is fixed as
https://zitadel.studentcouncil.dk. - No additional environment variables are explicitly required beyond the API credential.
Troubleshooting
- Invalid or missing credentials: If the API token is invalid or missing, calls will fail with authorization errors. Ensure the API key credential is correctly configured.
- Malformed JSON inputs: Input parameters for operations often expect JSON strings. Invalid JSON will cause parsing errors. Validate JSON syntax before running the node.
- Unsupported operation: Selecting an operation not supported by the chosen service will result in no action and an empty JSON output.
- Network issues: Connectivity problems to the Zitadel API endpoint will cause request failures. Verify network access and endpoint availability.
- Unexpected API responses: Since the node returns raw API responses, unexpected data structures may require checking Zitadel API documentation for correct usage.