WhatsApp Outreach by Boost.space icon

WhatsApp Outreach by Boost.space

Imported app WhatsApp Outreach by Boost.space.
Join our community

Actions10

Overview

This node interacts with WhatsApp outreach functionality provided by Boost.space, specifically focusing on retrieving messages from a chat. The "Get Message List From a Chat" operation fetches a list of messages from a specified chat, optionally filtered by sender and date range, and limited to a maximum number of results.

Common scenarios where this node is beneficial include:

  • Monitoring conversations in a specific WhatsApp chat for customer support or sales follow-up.
  • Extracting message history for analytics or reporting purposes.
  • Filtering messages sent by a particular user within a chat over a certain time period.

For example, you could use this node to retrieve the last 50 messages from a customer support group chat, filtering only those sent after a certain date, to analyze recent interactions.

Properties

Name Meaning
Chat ID The unique identifier of the chat from which to retrieve messages.
Limit Maximum number of messages to return (minimum 1).
Sender ID Optional filter to return only messages sent by a specific sender (user) within the chat.
After Optional datetime filter to include only messages sent after this timestamp (exclusive).
Before Optional datetime filter to include only messages sent before this timestamp (exclusive).

Output

The output is a JSON array containing the retrieved messages matching the specified filters. Each item in the array represents a message object with details as returned by the external WhatsApp Outreach API. The exact structure depends on the API response but typically includes message content, sender information, timestamps, and message IDs.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating requests to the Boost.space WhatsApp Outreach API.
  • The node makes HTTP POST requests to the Boost.space Supabase function endpoint (https://rnmqfhwsqojadktbxnrf.supabase.co/functions/v1/getMessagesListFromAChat).
  • Proper configuration of the API authentication credential in n8n is necessary for successful execution.

Troubleshooting

  • Common issues:

    • Invalid or missing Chat ID will cause the API request to fail or return no messages.
    • Incorrect API credentials or expired tokens will result in authentication errors.
    • Date filters ("After" and "Before") must be valid ISO datetime strings; invalid formats may cause errors or unexpected results.
    • Requesting a very high limit might lead to performance issues or API rate limiting.

  • Error messages:

    • Authentication failures usually indicate problems with the API key credential setup.
    • "Chat not found" or similar errors suggest the provided Chat ID does not exist or is inaccessible.
    • Validation errors related to parameters (e.g., limit below 1) require correcting input values.

To resolve these, verify the Chat ID, ensure the API key credential is correctly configured and active, and check that all input parameters conform to expected formats and constraints.

Links and References

Discussion