Actions39
- Client Actions
- Client Contact Actions
- Invoice Actions
- Order Actions
- Account Actions
- Service Actions
- Domain Actions
Overview
The HostBill node for n8n allows users to interact with the HostBill API, specifically to retrieve a list of accounts using the "Account" resource and the "Get All" operation. This node is useful in scenarios where you need to automate the extraction of account data from your HostBill instance, such as synchronizing account information with other systems, generating reports, or monitoring account statuses.
Practical examples:
- Fetching all active accounts for billing reconciliation.
- Listing all suspended accounts for compliance checks.
- Paginating through large sets of account records for data migration.
Properties
| Name | Type | Meaning |
|---|---|---|
| Additional Fields | Collection | A group of optional parameters to refine the query. |
| └ Page | Number | Which page of results to return (for pagination). |
| └ Status to List | Options | Filter accounts by status (All, Active, Pending, Suspended, Terminated, Fraud, Cancelled). |
Output
The node outputs an array of JSON objects, each representing an account retrieved from HostBill. The exact structure of each account object depends on the HostBill API response, but typically includes fields such as account ID, status, and other relevant account details.
If an error occurs and "Continue On Fail" is enabled, the output will include an object with an error field containing the error message.
Dependencies
- External Service: Requires access to a HostBill instance with API enabled.
- Credentials: Needs a configured "hostBillApi" credential in n8n.
- Environment Variables/Configuration: None specified beyond standard n8n credential setup.
Troubleshooting
Common Issues:
- Invalid Credentials: If the provided HostBill API credentials are incorrect, the node will throw an authentication error.
- API Connectivity: Network issues or incorrect HostBill API URL can cause connection failures.
- Parameter Errors: Supplying invalid values for "Page" or "Status to List" may result in API errors.
Error Handling:
- If an error occurs during execution and "Continue On Fail" is enabled, the node will output an object with an
errorproperty describing the issue. - If "Continue On Fail" is not enabled, the workflow will stop and display the error message.