Actions92
- Contact Actions
- Employee Actions
- Estimate Actions
- Invoice Actions
- Job Actions
- Line Item Actions
- Note Actions
- Setting Actions
- Supplier Actions
- Task Actions
- Technician Actions
- User Actions
- Website Actions
- WhatsApp Actions
Overview
The node interacts with the WibiClick API to manage various resources related to websites, customers, jobs, invoices, estimates, employees, line items, and more. Specifically for the Line Item resource with the Get Line Items operation, it retrieves multiple line items associated with a specified website.
This operation is useful when you want to fetch a list of line items (such as products or services) linked to a particular website, possibly for reporting, synchronization, or further processing in your workflow.
Practical example:
You have an e-commerce or service website and want to retrieve all line items (e.g., product details or service entries) to update your inventory system or generate reports on sales items.
Properties
| Name | Meaning |
|---|---|
| Website ID | The unique identifier of the website from which to retrieve line items. |
| Limit | Maximum number of line items to return in one request (pagination limit). |
| Offset | Number of line items to skip before starting to collect the result set (pagination offset). |
Output
The output is a JSON object containing the retrieved line items data from the WibiClick API. The structure depends on the API response but generally includes an array or collection of line item objects with their details such as name, description, amount, quantity, IDs, and associations to invoices or estimates.
No binary data output is involved in this operation.
Example output snippet (conceptual):
{
"lineItems": [
{
"id": "lineitem-123",
"name": "Product A",
"description": "Description of Product A",
"amount": 100,
"quantity": 2,
"invoiceId": "invoice-456",
"estimateId": "estimate-789"
},
...
]
}
Dependencies
- Requires an active connection to the WibiClick API.
- Needs an API key credential configured in n8n for authentication.
- The node uses HTTP requests to communicate with the API endpoints.
Troubleshooting
- Invalid Website ID: If the website ID is incorrect or missing, the API will likely return an error or empty results. Ensure the website ID is valid and accessible.
- Pagination issues: Setting very high limits may cause performance issues or API rate limiting. Use reasonable
limitandoffsetvalues. - Authentication errors: If the API key is invalid or expired, requests will fail with authorization errors. Verify the API key credential configuration.
- Network errors: Connectivity problems can cause request failures. Check network access and API availability.
Links and References
- WibiClick API Documentation (Assumed URL, replace with actual if available)
- n8n HTTP Request Node documentation: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/