WibiClickInstall

Overview

The node interacts with the WibiClick API to manage various resources, including jobs, notes, contacts, employees, estimates, invoices, line items, websites, WhatsApp messages, users, technicians, tasks, suppliers, and settings. Specifically for the Job resource with the Get Many operation, it retrieves multiple job records associated with a specified website.

This operation is useful when you want to fetch a list of jobs for a particular website, possibly for reporting, monitoring, or further automation workflows. For example, you might use this node to pull recent jobs from your system to analyze workload, track job statuses, or integrate job data into other systems.

Properties

These properties control which jobs are fetched and how many results are returned, enabling pagination through large datasets.

Output

The output is an array of JSON objects representing jobs retrieved from the WibiClick API. Each item in the output corresponds to a job record with all its associated fields as provided by the API response.

Example structure (simplified):

{
  "json": {
    "jobs": [
      {
        "id": "job-id-1",
        "name": "Job Name",
        "status": "Pending",
        "customerId": "customer-id",
        "employeeId": "employee-id",
        "slotStart": "2024-06-01T09:00:00Z",
        "slotEnd": "2024-06-01T11:00:00Z",
        ...
      },
      ...
    ]
  }
}

No binary data output is involved in this operation.

Dependencies

• Requires an active connection to the WibiClick API.
• Requires an API key credential configured in n8n for authentication.
• The node uses HTTP requests to communicate with the WibiClick API endpoints.

Troubleshooting

• Missing Website ID: The websiteId property is required. Omitting it will cause errors.
• Pagination parameters: Setting limit too high may lead to performance issues or API rate limits.
• API Errors: If the API returns an error (e.g., invalid credentials, network issues), the node will throw an error unless "Continue On Fail" is enabled.
• Empty Results: If no jobs exist for the given website or the offset exceeds available records, the output will be empty.
• Invalid API Key: Ensure the API key credential is valid and has permissions to access job data.

Links and References

• WibiClick API Documentation (hypothetical link, replace with actual if available)
• n8n documentation on HTTP Request Node for understanding underlying request mechanics.

This summary focuses on the Job resource's Get Many operation as requested, based solely on static analysis of the provided source code and input properties.