WibiClick

Interact with WibiClick API

Actions92

Overview

This node integrates with the WibiClick API to manage various resources related to websites, users, jobs, contacts, employees, estimates, invoices, line items, notes, WhatsApp messages, suppliers, settings, tasks, technicians, and more. Specifically for the Website resource and the Get Websites for User operation, it retrieves all websites associated with a specified user ID.

Common scenarios where this node is beneficial include:

Fetching all websites linked to a particular user for reporting or management purposes.
Automating workflows that require website data filtered by user ownership.
Integrating website data retrieval into larger automation pipelines involving user-specific website information.

Practical example:

A marketing team wants to pull all websites managed by a specific user to analyze traffic or performance metrics.
An admin system needs to list all websites a user has access to for permission auditing.

Properties

Name	Meaning
User ID	The unique identifier of the user whose websites you want to retrieve.
Limit	Maximum number of website results to return (pagination limit).
Offset	Number of website records to skip before starting to collect the result set (pagination offset).

Output

The output JSON contains the response from the WibiClick API endpoint that returns websites for the specified user. It typically includes an array or collection of website objects with their details such as IDs, URLs, names, and other metadata relevant to each website.

Example structure (simplified):

{
  "websites": [
    {
      "id": "website-id-1",
      "url": "https://example.com",
      "name": "Example Website",
      ...
    },
    {
      "id": "website-id-2",
      "url": "https://another.com",
      "name": "Another Website",
      ...
    }
  ],
  "total": 2,
  "limit": 50,
  "offset": 0
}

No binary data output is involved in this operation.

Dependencies

Requires an active connection to the WibiClick API via an API key credential.
The node expects the API URL and API key to be configured in the credentials.
Network connectivity to the WibiClick API endpoint is necessary.

Troubleshooting

Invalid or missing User ID: The operation requires a valid user ID; ensure it is provided and correctly formatted.
API authentication errors: If the API key is invalid or expired, requests will fail. Verify the API key credential configuration.
Pagination parameters: Using very high limits or offsets may cause slow responses or empty results if out of range.
Network issues: Connectivity problems to the WibiClick API will cause request failures.
Unexpected API responses: If the API changes or returns unexpected data, the node might throw errors or produce incomplete outputs.

Error messages thrown by the node generally come from HTTP request failures or validation checks, e.g., "Failed to create note" (not relevant here), or generic API error messages returned by the WibiClick service.

Links and References

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

Note: This summary focuses exclusively on the "Website" resource and the "Get Websites for User" operation as requested.

WibiClickInstall