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 integrates with the WibiClick API to perform various operations across multiple 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 Filtered Website Views operation, the node retrieves filtered website view data within a specified date range.
This operation is useful for analyzing website traffic over a custom period, enabling users to monitor visitor engagement, track trends, or generate reports based on filtered views. For example, a marketing team could use this to evaluate the effectiveness of campaigns by comparing website views before and after campaign launches.
Properties
| Name | Meaning |
|---|---|
| Website ID | The unique identifier of the website for which filtered views are requested. |
| Start Date | The start date of the period for filtering website views (inclusive). |
| End Date | The end date of the period for filtering website views (inclusive). |
These properties must be provided to specify the website and the date range for which the filtered views are retrieved.
Output
The output JSON object contains a views field, which is an array of objects. Each object represents website views data for a specific date within the requested range. Each entry includes:
date: The date of the recorded views.total: The total number of views on that date (as an integer).
If no views are found, the views array will be empty.
Example output snippet:
{
"views": [
{
"date": "2024-04-01",
"total": 123
},
{
"date": "2024-04-02",
"total": 98
}
]
}
Dependencies
- Requires an active connection to the WibiClick API.
- Requires an API key credential for authentication with the WibiClick service.
- The node uses HTTP requests to communicate with the WibiClick API endpoints.
- No additional external dependencies beyond the WibiClick API and n8n's HTTP request helper.
Troubleshooting
Invalid date format error: If the start or end date is not in a valid date format (expected YYYY-MM-DD or ISO 8601), the node throws an error:
"Invalid date format. Use YYYY-MM-DD."
Resolution: Ensure dates are correctly formatted.Start date after end date error: If the start date is later than the end date, the node throws:
"Start date must be before end date."
Resolution: Verify that the start date precedes or equals the end date.API authentication errors: If the API key is missing, invalid, or expired, the node will fail to authenticate.
Resolution: Check and update the API key credential in n8n.Empty or unexpected response: If the API returns no views or an unexpected structure, the output
viewsarray will be empty. This might indicate no data available for the given date range or website ID.
Links and References
- WibiClick API Documentation (Assumed URL; replace with actual if known)
- n8n HTTP Request Node documentation: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/
- Date formatting guidelines: https://en.wikipedia.org/wiki/ISO_8601
This summary focuses exclusively on the Website resource and the Get Filtered Website Views operation as requested.