WhatsApp Outreach by Boost.space icon

WhatsApp Outreach by Boost.space

Imported app WhatsApp Outreach by Boost.space.

Overview

This node integrates with the WhatsApp Outreach service by Boost.space, enabling users to interact programmatically with WhatsApp chats, messages, and user profiles. Specifically, the Chat - Get Many operation allows retrieving a list of WhatsApp chat conversations with optional filters on creation date and result count.

Common scenarios for this node include:

  • Fetching recent or historical WhatsApp chat conversations for analysis or reporting.
  • Synchronizing WhatsApp chat data into CRM or customer support systems.
  • Automating workflows based on chat activity within a specified time range.

For example, a user might configure the node to retrieve up to 50 chats created after a certain date to process new conversations daily.

Properties

Name Meaning
Limit Maximum number of chat results to return (minimum 1).
After Filter to include only chats created after this datetime (exclusive).
Before Filter to include only chats created before this datetime (exclusive).

Output

The output is a JSON array where each item represents a WhatsApp chat object retrieved from the service. The exact structure depends on the API response but typically includes chat metadata such as chat ID, participants, timestamps, and possibly last message details.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating requests to the WhatsApp Outreach service by Boost.space.
  • The node makes HTTP POST requests to a specific Supabase-hosted endpoint (https://rnmqfhwsqojadktbxnrf.supabase.co/functions/v1/ListChats) to fetch chat data.
  • Proper configuration of the API authentication credential in n8n is necessary.

Troubleshooting

  • Common issues:

    • Invalid or missing API credentials will cause authentication failures.
    • Providing invalid date formats for "After" or "Before" properties may lead to request errors.
    • Requesting a very high limit might be rejected or cause performance delays depending on API limits.
  • Error messages:

    • Authentication errors usually indicate problems with the API key setup; verify the credential configuration.
    • Validation errors related to date filters suggest checking the input format and ensuring dates are valid ISO strings.
    • Network or timeout errors may require checking connectivity or retrying later.

Links and References

Discussion