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 interacts with the WibiClick API to manage suppliers within a website context. Specifically, the "Add or Update Supplier" operation allows users to either add a new supplier or update an existing one by providing supplier details associated with a particular website.
Common scenarios where this node is beneficial include:
- Automating supplier management workflows in business applications.
- Synchronizing supplier data from external systems into WibiClick-managed websites.
- Updating supplier information programmatically without manual intervention.
For example, a user can use this node to add a new supplier with contact details and address to their website's supplier list or update an existing supplier's phone number or email.
Properties
| Name | Meaning |
|---|---|
| Website ID | The unique identifier of the website to which the supplier belongs. |
| Supplier Data | A collection of fields describing the supplier. It includes: |
| - Address: Supplier's physical address. | |
| - City: City where the supplier is located. | |
| - Contact Person: Name of the supplier's contact person. | |
| - Country: Supplier's country. | |
| - Email: Supplier's email address. | |
| - ID: Identifier of the supplier (used when updating an existing supplier). | |
| - Name: Name of the supplier. | |
| - Phone: Supplier's phone number. | |
| - State: State or region of the supplier. | |
| - Zip: Postal code of the supplier. |
Output
The output JSON contains the response from the WibiClick API after attempting to add or update a supplier. This typically includes confirmation of success and the details of the supplier as stored in the system.
Example output structure:
{
"json": {
"success": true,
"supplier": {
"id": "string",
"name": "string",
"address": "string",
"city": "string",
"state": "string",
"zip": "string",
"country": "string",
"phone": "string",
"email": "string",
"contactPerson": "string"
}
}
}
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the WibiClick API.
- Needs an API key credential for authentication with the WibiClick service.
- The node expects the API URL and API key to be configured in the credentials section of n8n.
Troubleshooting
- Missing or invalid Website ID: Ensure that the Website ID provided is correct and corresponds to an existing website in WibiClick.
- Supplier ID for updates: When updating a supplier, the supplier's ID must be provided; otherwise, the API may create a new supplier instead of updating.
- API Authentication Errors: If the API key is missing or invalid, requests will fail. Verify the API key credential configuration.
- Network Issues: Connectivity problems to the WibiClick API endpoint will cause request failures.
- Invalid Field Values: Providing improperly formatted fields (e.g., invalid email format) might result in API errors.
Error messages thrown by the node generally reflect HTTP errors returned by the API and are surfaced as node execution errors. To resolve, check the error message details and verify input parameters and credentials.
Links and References
- WibiClick API Documentation (Assumed link, replace with actual if available)
- n8n Documentation on Creating Custom Nodes
- General REST API usage in n8n: HTTP Request Node