WibiClickInstall

Overview

The node interacts with the WibiClick API to manage various resources, including WhatsApp interactions. Specifically, for the WhatsApp resource and the Get Recent WhatsApp Interactions operation, the node retrieves a list of recent WhatsApp interactions associated with a specified website.

This operation is useful in scenarios where you want to monitor or analyze recent communication via WhatsApp linked to your website, such as customer support chats, sales inquiries, or engagement tracking.

Practical example:
You can use this node to fetch the latest WhatsApp conversations from your website visitors and then trigger follow-up workflows, like sending automated responses, logging interactions into a CRM, or generating reports on customer engagement.

Properties

Output

The output JSON contains the data returned by the WibiClick API endpoint /recent-whatsapp-interactions. This typically includes an array of recent WhatsApp interaction objects related to the specified website.

Each interaction object may contain details such as timestamps, contact information, message summaries, or other metadata representing individual WhatsApp conversations.

No binary data is output by this operation.

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 environment variables are needed beyond the API key credential configuration.

Troubleshooting

• Common issues:

  • Invalid or missing Website ID will cause the API request to fail.
  • Exceeding API rate limits or invalid API key credentials will result in authorization errors.
  • Network connectivity problems can prevent successful API calls.

• Error messages:

  • If the API returns an error, it will be thrown as a node error with the message from the API response.
  • If the limit parameter is set too high, the API might reject the request or truncate results.
  • If no recent interactions exist, the output may be an empty array or an empty object.

• Resolution tips:

  • Ensure the Website ID is correct and corresponds to an existing website in your WibiClick account.
  • Verify that the API key credential is valid and has necessary permissions.
  • Use reasonable values for the limit parameter to avoid overwhelming the API.
  • Check network connectivity and proxy settings if requests fail unexpectedly.

Links and References

• WibiClick API Documentation (Assumed URL; replace with actual if available)
• n8n Documentation on HTTP Request Node (for understanding underlying HTTP calls)