N8N Tools - WhatsApp Enhanced icon

N8N Tools - WhatsApp Enhanced

Comprehensive WhatsApp Business API integration for N8N workflows

Overview

This node provides enhanced integration with the WhatsApp Business API via the N8N Tools platform. Specifically, for the Analytics resource and the Get Phone Number Analytics operation, it retrieves detailed analytics data related to phone numbers associated with a WhatsApp Business account.

The node allows users to specify a date range and granularity (hourly, daily, or monthly) to fetch aggregated analytics metrics about phone number activity. This is useful for businesses wanting to monitor usage patterns, message volumes, or engagement trends over time on their WhatsApp phone numbers.

Practical examples:

  • A marketing team analyzing daily message traffic on their WhatsApp number to optimize campaign timing.
  • Customer support monitoring hourly conversation volumes to allocate resources efficiently.
  • Business analysts tracking monthly growth in WhatsApp interactions for reporting purposes.

Properties

Name Meaning
Start Date The start date for the analytics data query, formatted as YYYY-MM-DD.
End Date The end date for the analytics data query, formatted as YYYY-MM-DD.
Granularity The time interval for aggregating analytics data. Options: Hour, Day, Month.

Output

The node outputs JSON data containing the requested phone number analytics aggregated according to the specified granularity and date range. The exact structure depends on the WhatsApp Business API response but typically includes metrics such as message counts, delivery statuses, and engagement statistics over time.

No binary data output is indicated for this operation.

Dependencies

  • Requires an active subscription and valid API key credential for the N8N Tools API service.
  • Uses the WhatsApp Business API accessed through the N8N Tools platform.
  • Proper configuration of credentials within n8n for the API key and OAuth2 authentication is necessary.

Troubleshooting

  • Invalid subscription or API key error: 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 or connectivity problems: Network issues or exceeding API quotas can cause failures; check network connectivity and API usage limits.

Links and References

Discussion