Actions39
- Client Actions
- Client Contact Actions
- Invoice Actions
- Order Actions
- Account Actions
- Service Actions
- Domain Actions
Overview
This n8n node allows you to interact with the HostBill API, specifically to set an order as active. The "Set Active" operation for the "Order" resource is useful in automation scenarios where you need to programmatically activate orders within your HostBill system, such as after payment confirmation or other workflow steps.
Example use cases:
- Automatically activating a new order after successful payment processing.
- Integrating HostBill order activation into a larger customer onboarding workflow.
- Bulk-activating orders based on external triggers or conditions.
Properties
| Name | Type | Meaning |
|---|---|---|
| Order ID | Number | The unique identifier of the order to be set as active. (Required) |
Output
The output will be a JSON object (or array of objects if multiple items are processed). The structure of the output depends on the response from the HostBill API for the "Set Active" operation. Typically, it may include fields such as:
- Confirmation of the order being set as active.
- Any relevant status messages or error information.
If an error occurs and "Continue On Fail" is enabled, the output will include an error field with the error message.
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 additional environment variables are required beyond standard credential setup.
Troubleshooting
Common Issues:
- Invalid Credentials: If the provided HostBill API credentials are incorrect, the node will throw an authentication error.
- Missing or Invalid Order ID: If the "Order ID" is missing or does not correspond to an existing order, the API may return an error.
- API Connectivity Issues: Network problems or incorrect HostBill API endpoint configuration can cause connection errors.
Error Handling:
- If "Continue On Fail" is enabled, errors for individual items will be included in the output as
{ "error": "Error message" }. - Otherwise, the node will stop execution and throw the encountered error.