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 order. It is useful in automation scenarios where you need to programmatically remove orders from your HostBill system, such as cleaning up test data, handling failed transactions, or integrating with other systems that require order deletion.
Example use cases:
- Automatically deleting orders that have been cancelled or marked as fraudulent.
- Integrating with external CRMs or ERPs to synchronize order deletions.
- Cleaning up old or test orders as part of a maintenance workflow.
Properties
| Name | Type | Meaning |
|---|---|---|
| Order ID | Number | The unique identifier of the order to be deleted. This field is required. |
Output
The output will be a JSON object (or array of objects) 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": "Order deleted successfully"
}
]
Or, in case of error (with "Continue On Fail"):
[
{
"error": "Order 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 orders.
- Order Not Found: If the specified Order ID does not exist, you may receive an error like
"Order not found". Double-check the Order 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 if you want the workflow to continue processing other items even when one fails.