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 provides integration with the WibiClick API, enabling interaction with various resources such as websites, notes, jobs, contacts, employees, estimates, invoices, line items, WhatsApp messages, users, technicians, tasks, suppliers, and settings. Specifically for the Website resource and the Get Website operation, the node retrieves detailed information about a single website by its unique ID.
This node is beneficial in scenarios where you need to programmatically fetch website details from WibiClick within an automation workflow. For example, you might want to retrieve website metadata or status before performing further actions like analytics, visitor tracking, or updating related records.
Properties
| Name | Meaning |
|---|---|
| Website ID | The unique identifier (ID) of the website to retrieve. This is a required string input. |
Output
- The output JSON contains the data returned by the WibiClick API for the requested website.
- The structure corresponds to the website object as defined by the WibiClick API's
/get-websiteendpoint. - The output includes all available fields describing the website, such as URL, name, performance metrics, settings, or other metadata.
- No binary data output is involved in this operation.
Example output snippet (conceptual):
{
"id": "d0cfa1ac-fd6f-48e8-b9e6-fac599a0430b",
"url": "https://example.com",
"name": "Example Website",
"createdAt": "2023-01-01T00:00:00Z",
"status": "active",
...
}
Dependencies
- Requires an API key credential for authenticating requests to the WibiClick API.
- The node uses HTTP requests to communicate with the WibiClick API endpoints.
- Ensure that the WibiClick API base URL and API key are correctly configured in the node credentials.
- No additional external dependencies beyond the WibiClick API and n8n's HTTP request helper.
Troubleshooting
- Invalid Website ID: If the provided Website ID does not exist or is malformed, the API may return an error or empty response. Verify the Website ID is correct.
- Authentication Errors: Missing or invalid API key will cause authentication failures. Confirm the API key credential is set up properly.
- Network Issues: Connectivity problems can cause request failures. Check network access to the WibiClick API endpoint.
- Unexpected API Response: If the API changes or returns unexpected data, the node may fail. Review API documentation or contact support if issues persist.
- Error Handling: If the node is set to continue on failure, errors will be returned in the output JSON with
success: falseand an error message.
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/
- n8n Credentials Setup Guide: https://docs.n8n.io/credentials/overview/
This summary focuses exclusively on the Website resource and the Get Website operation as requested.