WhatsApp Outreach by Boost.space icon

WhatsApp Outreach by Boost.space

Imported app WhatsApp Outreach by Boost.space.

Actions5

Overview

This node, "WhatsApp Outreach by Boost.space," enables sending and managing WhatsApp messages programmatically via an external API. Specifically, the Create One Message operation allows users to start a new conversation by sending a message to one or more recipients identified by their internal IDs within the provider system.

Common scenarios for this node include:

  • Automating outreach campaigns where personalized WhatsApp messages are sent to multiple contacts.
  • Initiating conversations with customers or team members directly from workflow automation.
  • Integrating WhatsApp messaging into CRM or support systems to streamline communication.

For example, a marketing team could use this node to send promotional messages to a list of attendees, or a support team could initiate follow-up conversations with clients.

Properties

Name Meaning
Attendees IDs One or more internal IDs of users to whom the message will be sent.
Text The content of the message that will start the new conversation.
Subject ID An optional subject line for the conversation (can be left empty if not needed).
  • Attendees IDs is a collection allowing multiple user IDs to be specified.
  • Text is a string representing the actual message body.
  • Subject ID is an optional string to set the conversation's subject.

Output

The node outputs JSON data representing the response from the external WhatsApp API after attempting to create/send the message. This typically includes details about the message status, any identifiers assigned by the service, and confirmation of delivery initiation.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating requests to the external WhatsApp Outreach service by Boost.space.
  • The node communicates with a specific API endpoint hosted at https://rnmqfhwsqojadktbxnrf.supabase.co/functions/v1.
  • Proper configuration of the API authentication credential in n8n is necessary for successful execution.

Troubleshooting

  • Common issues:

    • Missing or invalid API credentials will cause authentication failures.
    • Providing invalid or empty attendee IDs may result in errors or no messages being sent.
    • Network connectivity problems can prevent reaching the external API endpoint.

  • Error messages:

    • Authentication errors usually indicate misconfigured or expired API keys; verify and update credentials.
    • Validation errors from the API might mention missing required fields like attendees or text; ensure all mandatory properties are correctly filled.
    • Rate limiting or quota exceeded errors require checking the usage limits of the external service.

Links and References

Discussion