WasapBom icon

WasapBom

Send WhatsApp messages via WasapBom API

Actions8

Overview

This node integrates with the WasapBom API to interact with WhatsApp messaging services. Specifically, for the Chat - Get Messages operation, it retrieves messages from a specified WhatsApp chat identified by its JID (WhatsApp ID). This is useful for workflows that need to fetch recent conversation history or monitor chat activity programmatically.

Practical examples include:

  • Automatically fetching the last 20 messages from a customer support chat to analyze conversation context.
  • Archiving chat messages for compliance or record-keeping.
  • Triggering further automation based on specific message content retrieved from a chat.

Properties

Name Meaning
JID (Chat ID) The unique WhatsApp identifier of the chat to retrieve messages from (e.g., 60123456789@s.whatsapp.net). This is required.
Count Number of messages to retrieve from the chat. Defaults to 20 if not specified.

Output

The output is a JSON array where each item corresponds to a message retrieved from the specified chat. Each message object contains the data returned by the WasapBom API about individual WhatsApp messages, such as sender info, message content, timestamps, and message type.

No binary data output is produced by this operation.

Dependencies

  • Requires an active WasapBom API key credential configured in n8n.
  • The node makes HTTP requests to the WasapBom API endpoint at https://panel.wasapbom.com/api/whatsapp/messages.
  • Proper network connectivity to the WasapBom service is necessary.

Troubleshooting

Common Issues

  • Authentication failures: If the API key is invalid or missing, the node will return an authentication error.
  • Invalid JID format: Providing an incorrectly formatted WhatsApp JID may cause validation errors.
  • API rate limits or server errors: Temporary issues on the WasapBom side can result in 5xx errors.

Error Messages and Resolutions

  • Authentication failed: "Invalid API key. Please check your credentials."
    Resolution: Verify and update the API key credential in n8n.
  • Validation error: "The API could not process your request."
    Resolution: Check that the JID and count parameters are correctly formatted and valid.
  • Bad request: "The request was improperly formatted or contained invalid parameters."
    Resolution: Ensure all required parameters are provided and correctly typed.
  • Forbidden: "You do not have permission to access this resource."
    Resolution: Confirm that the API key has sufficient permissions.
  • Not found: "The requested resource does not exist."
    Resolution: Verify the JID exists and is accessible.
  • Server error: "The WasapBom server encountered an error."
    Resolution: Retry after some time or contact WasapBom support if persistent.

If the node is set to continue on failure, errors will be returned as JSON objects containing error details instead of stopping execution.

Links and References

Discussion