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 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 Zitadel user management into broader automation pipelines.
For example, you might use this node in an automation that monitors user status and automatically reactivates users upon certain triggers, such as payment confirmation or administrative approval.
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 the ManagementService context. 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, 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 various Zitadel services.
Troubleshooting
- Invalid or missing authentication token: Ensure the API key credential is correctly set up and has sufficient permissions.
- Incorrect user ID or ID parameter: Verify that the provided user identifiers correspond to existing users in the targeted service.
- Unsupported service-operation combination: The node only supports
userIdfor UserService andidfor ManagementService in thereactivateUseroperation. Using other combinations may result in empty or error responses. - JSON parsing errors: Input parameters are parsed as JSON if possible; ensure string inputs are valid JSON or plain strings as expected.