Actions9
Overview
This node interacts with the Pulse API to perform various account-related actions, specifically for managing user accounts. For the "Account" resource, it supports operations such as retrieving current user info, fetching an account by ID, creating accounts, updating account details, and activating or deactivating accounts.
The "Activate/Deactivate Account" operation allows users to enable or disable a specific account by setting its status. This is useful in scenarios where you want to temporarily suspend access without deleting the account, or reactivate previously disabled accounts.
Practical examples:
- Automatically deactivate user accounts after a period of inactivity.
- Reactivate accounts when users regain access privileges.
- Manage account statuses in bulk workflows based on external triggers.
Properties
| Name | Meaning |
|---|---|
| Account ID * | The unique identifier of the account to be updated or retrieved. |
| Status * | Whether the account should be activated (enabled) or deactivated (disabled). Options: Activate, Deactivate |
Output
The node outputs JSON data representing the result of the performed account action. For the "updateAccountStatus" operation (Activate/Deactivate Account), the output JSON typically contains the updated account information reflecting the new status.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating with the Pulse API.
- The node depends on the Pulse API service being accessible.
- No additional environment variables are explicitly required beyond the API authentication setup.
Troubleshooting
Common issues:
- Invalid or missing Account ID will cause errors when attempting to update or retrieve account data.
- Insufficient permissions or invalid API credentials can lead to authentication failures.
- 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 name."The resource \"account\" is not supported!"suggests an incorrect resource selection.- API errors returned from Pulse (e.g., unauthorized, not found) will be passed through; ensure the account ID exists and credentials are valid.
To resolve these:
- Verify that the Account ID is correct and exists in the system.
- Confirm that the API key credential is properly configured and has necessary permissions.
- Check network connectivity and Pulse API service status.
Links and References
- Pulse API Documentation (replace with actual URL)
- n8n documentation on Creating Custom Nodes