Actions39
- Client Actions
- Client Contact Actions
- Invoice Actions
- Order Actions
- Account Actions
- Service Actions
- Domain Actions
Overview
This node allows you to interact with the HostBill API, specifically to delete an Account resource. It is useful in automation scenarios where you need to programmatically remove accounts from your HostBill system, such as cleaning up test data, automating user offboarding, or integrating account deletion into larger workflows.
Example use cases:
- Automatically deleting customer accounts when a subscription is cancelled.
- Removing obsolete or duplicate accounts as part of a scheduled maintenance workflow.
- Integrating with other systems to synchronize account deletions.
Properties
| Name | Type | Meaning |
|---|---|---|
| Account ID | Number | The unique identifier of the account to be deleted. This is required. |
Output
The output will be a JSON object (or array of objects if multiple items are processed) representing the result of the delete operation for each input item. If an error occurs and "Continue On Fail" is enabled, the output will include an error field with the error message.
Example output:
[
{
"success": true,
"message": "Account deleted successfully"
}
]
Or, in case of error (with "Continue On Fail"):
[
{
"error": "Account not found"
}
]
Dependencies
- External Service: Requires access to a HostBill instance with API enabled.
- API Credentials: You must configure valid HostBill API credentials in n8n under the name
hostBillApi. - n8n Configuration: No special environment variables are needed beyond standard credential setup.
Troubleshooting
- Invalid Credentials: If the provided API credentials are incorrect or lack permissions, the node will throw an authentication error. Ensure your credentials are correct and have permission to delete accounts.
- Account Not Found: If the specified Account ID does not exist, you may receive an error like
"Account not found". Double-check the Account ID. - Network Issues: Connectivity problems between n8n and HostBill can cause timeouts or connection errors.
- Error Handling: If "Continue On Fail" is not enabled, any error will stop the workflow execution. Enable this option to process all items and collect errors in the output.