N8N Tools - WhatsApp Enhanced icon

N8N Tools - WhatsApp Enhanced

Comprehensive WhatsApp Business API integration for N8N workflows
Join our community

Actions28

Overview

The node provides integration with the WhatsApp Business API via the N8N Tools platform, enabling users to retrieve detailed conversation analytics data. Specifically, the "Get Conversation Analytics" operation fetches metrics about conversations over a specified date range and granularity. This is useful for businesses wanting to analyze customer interactions on WhatsApp, track engagement trends, and optimize communication strategies.

Practical examples include:

  • Monitoring daily or monthly conversation volumes to assess customer support load.
  • Analyzing conversation patterns by hour to optimize staffing.
  • Comparing conversation metrics across different time periods for performance evaluation.

Properties

Name Meaning
Start Date The start date for the analytics query in YYYY-MM-DD format.
End Date The end date for the analytics query in YYYY-MM-DD format.
Granularity The time granularity of the analytics data. Options: Hour, Day, Month.

Output

The node outputs JSON data containing the conversation analytics retrieved from the WhatsApp Business API. The structure typically includes metrics aggregated according to the specified granularity and date range, such as counts of conversations, message volumes, or other relevant statistics.

No binary data output is produced by this operation.

Dependencies

  • Requires an active subscription and valid API key credential for the N8N Tools API service.
  • The node uses the WhatsApp Business API accessed through the N8N Tools platform.
  • Proper configuration of credentials within n8n is necessary to authenticate requests.

Troubleshooting

  • Invalid Subscription or API Key: If the node throws an error indicating invalid subscription or API key, verify that the API key credential is correctly configured and active.
  • Date Format Issues: Ensure that the Start Date and End Date are provided in the correct YYYY-MM-DD format; otherwise, the API may reject the request.
  • Granularity Mismatch: Using unsupported granularity values may cause errors; use only the provided options (Hour, Day, Month).
  • API Rate Limits: Excessive requests might lead to throttling; consider adding delays or batching requests.
  • Network or Connectivity Errors: Check network connectivity and endpoint accessibility if requests fail unexpectedly.

Links and References

Discussion