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
This node integrates with the WibiClick API to manage various resources related to business operations, including suppliers. Specifically, for the Supplier resource and the Get Suppliers operation, it retrieves a list of suppliers associated with a specified website. This is useful in scenarios where you want to automate fetching supplier data for inventory management, procurement workflows, or reporting purposes.
For example, you can use this node to:
- Automatically pull updated supplier lists from your system into your workflow.
- Sync supplier data with other systems like CRMs or ERPs.
- Trigger notifications or further processing based on supplier information.
Properties
| Name | Meaning |
|---|---|
| Website ID | The unique identifier of the website for which to retrieve suppliers. |
| Limit | Maximum number of supplier records to return in one request (pagination limit). |
| Offset | Number of supplier records to skip before starting to collect the result set (pagination). |
Output
The output is a JSON object containing the list of suppliers retrieved from the API. The structure typically includes an array of supplier objects with their details such as name, contact info, address, and other metadata as provided by the API response.
Example output structure (simplified):
{
"suppliers": [
{
"id": "supplier-id-1",
"name": "Supplier One",
"address": "123 Supplier St.",
"city": "Supplier City",
"country": "Country",
"phone": "1234567890",
"email": "contact@supplierone.com"
// ... other supplier fields
},
{
"id": "supplier-id-2",
"name": "Supplier Two",
// ...
}
],
"total": 100,
"limit": 50,
"offset": 0
}
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating requests to the WibiClick API.
- The node expects the API URL and key to be configured in the credentials.
- Pagination parameters (
limitandoffset) are supported to control the volume of data returned.
Troubleshooting
- Missing or invalid Website ID: The API call requires a valid website ID; ensure this is correctly provided.
- API authentication errors: If the API key is missing or invalid, requests will fail with authorization errors.
- Pagination issues: Setting very high limits may cause performance issues or API rate limiting.
- Network or API downtime: Connectivity problems or API service interruptions will cause request failures.
- Error handling: If the API returns an error, the node throws an error unless "Continue On Fail" is enabled, in which case it outputs an error message in the JSON.
Links and References
- WibiClick API Documentation (hypothetical link, replace with actual if available)
- n8n documentation on HTTP Request Node for understanding underlying HTTP calls.
- General n8n Custom Node Development Guide for extending or debugging nodes.
This summary focuses exclusively on the Supplier resource and the Get Suppliers operation as requested.