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 perform various operations across multiple Zitadel services such as UserService, ManagementService, AuthService, and others. Specifically, for the getUserByID operation under the "Default" resource, it fetches detailed information about a user by their unique identifier.
Typical use cases include:
- Retrieving user profile details in identity management workflows.
- Fetching user data for administrative or organizational purposes.
- Integrating Zitadel user information into other systems or automations.
For example, you might use this node to get a user's full profile by providing their user ID, then use that data to update records in your CRM or trigger notifications.
Properties
| Name | Meaning |
|---|---|
| Service | The Zitadel service to interact with. Options: UserService, OrganizationService, AuthService, ManagementService, AdminService, ZITADELActions, UserSchemaService. Default is UserService. |
| userId | The unique identifier of the user to retrieve. Required when Service is UserService and Operation is getUserByID. |
| id | The unique identifier of the user to retrieve. Required when Service is ManagementService and Operation is getUserByID. |
Output
The node outputs a JSON object containing the response from the Zitadel API corresponding to the requested operation. For getUserByID, the output JSON includes detailed user information as returned by the Zitadel UserService or ManagementService, depending on the selected service.
The structure of the JSON depends on the Zitadel API's user schema but typically includes fields like user ID, email, display name, creation date, and other profile attributes.
No binary data output is produced by this node.
Dependencies
- Requires an API authentication token (Personal Access Token) for Zitadel, configured in the node credentials.
- Connects to the Zitadel API endpoint at
https://zitadel.studentcouncil.dk. - Uses gRPC clients generated from Zitadel protobuf definitions to communicate with the API.
Troubleshooting
- Invalid or missing API token: Ensure the Personal Access Token credential is correctly set up and has sufficient permissions.
- Incorrect user ID: Verify that the provided user ID (
userIdorid) exists in the Zitadel system. - JSON parsing errors: Input parameters are parsed as JSON if possible; ensure string inputs are valid JSON or plain strings as expected.
- Operation not found: Confirm that the selected operation matches one supported by the chosen service.
- Network issues: Check connectivity to the Zitadel API endpoint.