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 business operations, including notes, jobs, contacts, employees, estimates, invoices, line items, websites, WhatsApp messages, users, technicians, tasks, suppliers, and settings.
Specifically for the Line Item resource with the Get Line Item operation, the node retrieves detailed information about a single line item identified by its ID within a specified website context. This is useful in scenarios where you need to fetch details of a particular product or service line item associated with invoices or estimates for further processing, reporting, or integration with other systems.
Practical example:
You have an invoice system integrated with WibiClick, and you want to retrieve detailed information about a specific line item (e.g., a product or service) to display it in a custom dashboard or to use it in automated workflows such as sending notifications or updating inventory.
Properties
| Name | Meaning |
|---|---|
| Website ID | The unique identifier of the website under which the line item exists. |
| Line Item ID | The unique identifier of the line item to retrieve. |
These properties are required to specify exactly which line item to fetch from the WibiClick system.
Output
The output is a JSON object containing the details of the requested line item. The structure corresponds to the data returned by the WibiClick API's endpoint for fetching a single line item. It typically includes fields such as:
id: The line item ID.name: Name of the line item.description: Description of the line item.amount: Monetary amount for the line item.quantity: Quantity of the item.- Possibly other metadata related to the line item.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the WibiClick API.
- Requires an API key credential for authentication with the WibiClick API.
- The node uses HTTP requests to communicate with the API endpoints.
- No additional external dependencies beyond the WibiClick API and n8n's HTTP request helper.
Troubleshooting
Invalid or missing Website ID or Line Item ID:
Ensure that both IDs are correctly provided and correspond to existing entities in the WibiClick system.Authentication errors:
Verify that the API key credential is valid and has sufficient permissions to access line item data.API response errors:
If the API returns an error (e.g., line item not found), the node will throw an error. Check the line item ID and website ID for correctness.Network issues:
Ensure that the n8n instance can reach the WibiClick API endpoint without network restrictions.
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/
Summary of Relevant Code Snippet for Get Line Item Operation
if (resource === "lineItem" && operation === "getLineItem") {
const websiteId = this.getNodeParameter("websiteId", i);
const lineItemId = this.getNodeParameter("lineItemId", i);
const response = await this.helpers.request({
method: "GET",
url: `${credentials.apiUrl}/lineitem?id=${websiteId}&lid=${lineItemId}`,
headers: { Authorization: `Bearer ${credentials.apiKey}` },
json: true,
});
returnData.push({ json: response });
}
This shows the node performs a GET request to the /lineitem endpoint with query parameters for website ID and line item ID, authenticating via Bearer token.
If you need summaries for other resources or operations, please provide their names.