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
Overview
This node provides an interface to interact with the Zitadel API, specifically allowing users to call various services and operations exposed by Zitadel. The reactivateUser operation under the "Default" resource reactivates a user account in Zitadel. This is useful in scenarios where a user was previously deactivated or suspended and needs to regain access without creating a new account.
Practical examples include:
- Reactivating a user who left an organization but has now returned.
- Restoring access for a user whose account was temporarily disabled due to inactivity or policy violations.
Properties
| Name | Meaning |
|---|---|
| Service | The Zitadel service to use. 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 of the user to reactivate. Required when Service is ManagementService and Operation is reactivateUser. |
Output
The output JSON contains the response from the Zitadel API corresponding to the reactivateUser operation. It typically includes details about the reactivated user or confirmation of the action. The exact structure depends on the Zitadel API response schema for that operation.
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 API token: Ensure the Zitadel API token credential is correctly configured and valid.
- Incorrect user ID: Verify that the
userIdoridproperty matches an existing user in Zitadel. - Operation not found: Confirm that the selected service supports the
reactivateUseroperation. - JSON parsing errors: Input properties are parsed as JSON if possible; ensure string inputs are valid JSON or plain strings as expected.
- Network issues: Check connectivity to the Zitadel API endpoint.