Actions9
Overview
This node provides actions related to user accounts via the Pulse API. Specifically, for the "Account" resource and the "Activate/Deactivate Account" operation, it allows enabling or disabling a user account by updating its status. This is useful in scenarios where administrators need to control access to accounts, such as temporarily suspending users or reactivating previously disabled accounts.
Practical examples:
- Activating a newly created user account after verification.
- Deactivating an account due to suspicious activity or policy violations.
Properties
| Name | Meaning |
|---|---|
| Account ID * | The unique identifier of the account to update (required). |
| Status * | Whether the account should be enabled or disabled. Options: Activate (true), Deactivate (false) (required). |
Output
The node outputs a JSON object representing the result of the account status update operation. This typically includes details about the updated account, such as its ID and current status. No binary data output is involved.
Dependencies
- Requires an API key credential for authenticating with the Pulse API.
- The node depends on the Pulse API service being accessible and properly configured.
- No additional environment variables are explicitly required beyond the API authentication.
Troubleshooting
Common issues:
- Invalid or missing Account ID will cause the operation to fail.
- Insufficient permissions or invalid API credentials can lead to authorization errors.
- Network connectivity problems may prevent communication with the Pulse API.
Error messages:
"The operation "updateAccountStatus" is not supported for resource "account"!"— indicates a misconfiguration of the operation or resource selection.- Errors returned from the Pulse API (e.g., "Account not found", "Unauthorized") should be checked and resolved by verifying input parameters and credentials.
Links and References
- Pulse API Documentation (replace with actual URL if available)
- n8n documentation on Creating Custom Nodes