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
addHumanUser
AI-generatedOverview
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 the Zitadel system by calling the appropriate service method.
Common scenarios where this node is beneficial include:
- Automating user onboarding workflows by programmatically adding users.
- Integrating Zitadel user management into broader automation pipelines.
- Synchronizing user data from external systems into Zitadel.
For example, you could use this node to add a new user with specified username, email, phone, and password details directly from an n8n workflow triggered by a form submission or CRM event.
Properties
| Name | Meaning |
|---|---|
| Service | The Zitadel service to call. Options: UserService, OrganizationService, AuthService, ManagementService, AdminService, ZITADELActions, UserSchemaService. For this operation, select "UserService" or "ManagementService". |
| userId | (UserService only) The unique identifier for the user to be added. |
| username | (UserService only) The username of the new human user. |
| organization | (UserService only) The organization to which the user belongs. |
| profile | (UserService and ManagementService) Profile information for the user. |
| (UserService and ManagementService) Email address of the user. | |
| phone | (UserService and ManagementService) Phone number of the user. |
| metadata | (UserService only) Additional metadata associated with the user, typically as a JSON string. |
| password | (UserService only) The user's password in plain text. |
| hashedPassword | (UserService only) The user's password in hashed form. |
| idpLinks | (UserService only) Identity provider links related to the user, usually as a JSON string. |
| totpSecret | (UserService only) TOTP secret key for two-factor authentication setup. |
| userName | (ManagementService only) Username of the user to add. |
| initialPassword | (ManagementService only) Initial password for the user. |
Note: Some properties are required depending on the selected service (UserService or ManagementService) and operation (addHumanUser).
Output
The node outputs the raw JSON response returned by the Zitadel API for the addHumanUser operation. This typically includes details about the newly created user such as their ID, status, and any other relevant metadata provided by the API.
No binary data output is produced by this node.
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 API token: Ensure that the Zitadel API token credential is correctly set up and has sufficient permissions.
- Malformed JSON input: Some properties expect JSON strings (e.g.,
metadata,idpLinks). Invalid JSON will cause parsing errors. Validate JSON syntax before input. - Missing required fields: All required properties for the chosen service and operation must be provided; otherwise, the API will reject the request.
- Network issues: Verify network connectivity to the Zitadel API endpoint.
- Unsupported operation: If an operation name is incorrect or not supported by the selected service, the node returns empty output.