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
reactivateUser
AI-generatedOverview
This node provides an interface to interact with the Zitadel API, a platform for identity and access management. Specifically, the reactivateUser operation allows reactivating a previously deactivated user account within different Zitadel services.
Common scenarios where this node is beneficial include:
- Restoring access for users who were temporarily deactivated.
- Automating user lifecycle management workflows.
- Integrating user reactivation into broader organizational or authentication processes.
For example, an organization might use this node to automatically reactivate a user after verifying certain conditions in their internal system, without manual intervention.
Properties
| Name | Meaning |
|---|---|
| Service | The Zitadel service to target. Options: UserService, OrganizationService, AuthService, ManagementService, AdminService, ZITADELActions, UserSchemaService. Default is UserService. |
| userId | The unique identifier of the user to reactivate. Required when Service is UserService and Operation is reactivateUser. |
| id | The unique identifier used for reactivation in ManagementService. Required when Service is ManagementService and Operation is reactivateUser. |
Output
The node outputs a JSON object representing the response from the Zitadel API for the reactivateUser operation. This typically includes details about the reactivated user or confirmation of the action performed.
No binary data output is produced by this node.
Dependencies
- Requires an API authentication token (personal access token) for Zitadel, provided via node 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.
- Incorrect user ID or ID parameter: Verify that the correct identifier is provided depending on the selected service (
userIdfor UserService,idfor ManagementService). - Unsupported operation or service: If the selected operation is not available for the chosen service, the node returns an empty JSON object.
- JSON parsing errors: Input parameters are parsed as JSON if possible; malformed JSON strings may cause failures. Provide plain strings for simple IDs.