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 websites, customers, jobs, employees, invoices, estimates, tasks, WhatsApp messages, and settings. Specifically for the Setting resource with the Get Settings operation, it retrieves the configuration settings associated with a specified website.
Common scenarios where this node is beneficial include:
- Automating retrieval of website-specific settings for use in workflows.
- Synchronizing or auditing configuration data across multiple websites.
- Using settings data to conditionally control workflow logic or trigger other actions.
Practical example:
- A user wants to fetch the current settings of a particular website (identified by its Website ID) to check contact information, branding options, or integration keys before performing further automated updates or notifications.
Properties
| Name | Meaning |
|---|---|
| Website ID | The unique identifier of the website whose settings are to be retrieved. |
Output
The output JSON contains the settings data for the specified website as returned by the WibiClick API. This typically includes various configuration fields such as company information, contact details, branding preferences, default messages, logos, and other customizable settings relevant to the website.
Example output structure (simplified):
{
"id": "website-id",
"company_name": "Company Name",
"email": "contact@company.com",
"phone_show": true,
"branding_show": true,
"estimate_number": 112,
"invoice_number": 1710,
"address1": "123 Main St",
"city": "CityName",
"country": "CountryName",
"currency_symbol": "$",
// ... other setting fields ...
}
No binary data output is involved in this operation.
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 WibiClick API endpoints.
Troubleshooting
- Invalid or missing Website ID: Ensure the Website ID parameter is provided and correctly formatted; otherwise, the API call will fail.
- Authentication errors: Verify that the API key credential is valid and has sufficient permissions.
- API connectivity issues: Network problems or incorrect API URL configuration can cause request failures.
- Unexpected API responses: If the API returns errors or unexpected data, check the WibiClick service status and review API documentation for changes.
Links and References
- WibiClick API Documentation (hypothetical link, replace with actual if available)
- n8n HTTP Request Node documentation: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/