WibiClickInstall

Overview

This node interacts with the WibiClick API to manage various resources, including contacts. Specifically, for the Contact resource with the Get Many operation, it retrieves multiple customer records associated with a specified website. This is useful when you want to fetch a list of customers for reporting, analysis, or further processing in your workflow.

Typical use cases include:

• Retrieving all customers linked to a particular website.
• Paginating through large sets of customer data using limit and offset parameters.
• Integrating customer data retrieval into automated workflows for CRM updates or marketing campaigns.

Properties

Output

The output is a JSON object containing the retrieved customers. The structure corresponds to the response from the WibiClick API's /customers endpoint and typically includes an array of customer objects with their details such as name, contact information, and other metadata.

Example output structure (simplified):

{
  "customers": [
    {
      "id": "string",
      "name": "string",
      "email": "string",
      "phone": "string",
      "address": "string",
      ...
    },
    ...
  ],
  "total": 123,
  "limit": 50,
  "offset": 0
}

No binary data is output by 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 Website ID: If the provided Website ID is incorrect or does not exist, the API may return an error or empty results. Verify the Website ID is correct.
• Limit and Offset Issues: Providing invalid values (e.g., negative numbers) for limit or offset may cause errors or unexpected behavior. Ensure limit is at least 1 and offset is zero or positive.
• API Authentication Errors: If the API key is missing, expired, or invalid, requests will fail with authorization errors. Check that the API key credential is correctly set up.
• Network or API Downtime: Temporary network issues or API service downtime can cause request failures. Retry after some time or check the API status.
• Large Result Sets: Requesting very large limits may lead to performance issues or timeouts. Use pagination with reasonable limits.

Links and References

• WibiClick API Documentation (Assumed URL; replace with actual if known)
• n8n Documentation on HTTP Request Node
• General guidance on Pagination in APIs