Actions42
- listUsers
- registerTOTP
- addHumanUser
- getUserByID
- setEmail
- resendEmailCode
- verifyEmail
- setPhone
- removePhone
- resendPhoneCode
- verifyPhone
- updateHumanUser
- deactivateUser
- reactivateUser
- lockUser
- unlockUser
- deleteUser
- registerPasskey
- verifyPasskeyRegistration
- createPasskeyRegistrationLink
- listPasskeys
- removePasskey
- registerU2F
- verifyU2FRegistration
- removeU2F
- 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 to perform various operations across multiple Zitadel services. Specifically, for the addHumanUser operation under the default resource, it allows creating a new human user in either the UserService or ManagementService of Zitadel. This is useful for automating user management tasks such as onboarding new users into an organization, setting up their profiles, and initializing credentials.
Practical examples include:
- Adding a new employee to your organization's identity management system.
- Automating user creation workflows during application sign-ups.
- Managing user accounts programmatically within an enterprise environment.
Properties
| Name | Meaning |
|---|---|
| Service | The Zitadel service to use. Options: UserService, OrganizationService, AuthService, ManagementService, AdminService, ZITADELActions, UserSchemaService. For this operation, typically UserService or ManagementService. |
| userId | (UserService only) Unique identifier for the user to be added. |
| username | (UserService only) Username for the new user. |
| organization | (UserService only) Organization to which the user belongs. |
| profile | (UserService and ManagementService) Profile information for the user, usually JSON string. |
| (UserService and ManagementService) Email address of the user. | |
| phone | (UserService and ManagementService) Phone number of the user. |
| metadata | (UserService only) Additional metadata about the user, typically a JSON string. |
| password | (UserService only) Password for the user account. |
| hashedPassword | (UserService only) Hashed version of the user's password. |
| idpLinks | (UserService only) Identity provider links associated with the user, usually JSON string. |
| totpSecret | (UserService only) Secret key for TOTP (Time-based One-Time Password) two-factor authentication. |
| userName | (ManagementService only) Username for the new user. |
| initialPassword | (ManagementService only) Initial password for the user account. |
Note: Many properties are required and must be provided as strings, often formatted as JSON strings where complex data structures are expected.
Output
The node outputs a JSON object representing the response from the Zitadel API after attempting to add the human user. This output contains details about the created user or any relevant status information returned by the API.
No binary data output is produced by this operation.
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 credentials: Ensure that a valid API token is configured in the node credentials; otherwise, authorization errors will occur.
- Malformed JSON input: Several properties expect JSON strings (e.g.,
profile,metadata,idpLinks). Invalid JSON will cause parsing errors. Validate JSON formatting before execution. - Missing required fields: All required properties must be provided; missing fields will result in API errors.
- Service-operation mismatch: Selecting a service that does not support the
addHumanUseroperation or providing parameters not applicable to the chosen service may cause failures. - Network issues: Connectivity problems to the Zitadel API endpoint will prevent successful execution.