WasapBom icon

WasapBom

Send WhatsApp messages via WasapBom API

Actions8

Overview

This node integrates with the WasapBom API to send WhatsApp messages and manage contacts, chats, groups, and instances. Specifically, the Send Contact operation under the Message resource allows users to send a contact card via WhatsApp to a specified phone number.

Typical use cases include:

  • Sharing contact information quickly during customer support or sales conversations.
  • Automating sending of business cards or team member contacts in workflows.
  • Integrating WhatsApp contact sharing into CRM or marketing automation pipelines.

For example, you can configure the node to send a contact card containing a full name and phone number to a client’s WhatsApp number automatically after a form submission.

Properties

Name Meaning
Phone Number The recipient's phone number to which the contact card will be sent. Format without "+"; e.g., "60123456789".
Contact Name Full name of the contact being shared in the contact card.
Contact Phone Number Phone number of the contact being shared. Format without "+"; e.g., "60123456789".

Note: There are notices reminding users to set country codes without the "+" prefix for both the recipient's phone number and the contact's phone number.

Output

The node outputs JSON data representing the response from the WasapBom API after attempting to send the contact message. This typically includes status information about the message delivery.

If an error occurs, and the node is configured to continue on failure, the output will contain an error object with fields such as error (message), statusCode, and timestamp.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for WasapBom API authentication.
  • The node makes HTTP requests to the WasapBom API endpoint at https://panel.wasapbom.com/api/whatsapp.
  • Proper configuration of the API key credential within n8n is necessary.

Troubleshooting

Common Issues

  • Authentication failures: Occur if the API key is invalid or missing.
  • Validation errors: May happen if required parameters are missing or incorrectly formatted (e.g., phone numbers without country code).
  • Bad requests: Improperly formatted requests or invalid parameter values.
  • Permission errors: If the API key does not have access rights to the requested resource.
  • Not found errors: When trying to access non-existent resources.
  • Server errors: Temporary issues on the WasapBom server side.

Error Messages and Resolutions

  • Authentication failed: Check that the API key credential is correctly set and valid.
  • Validation error: Verify all required fields are provided and correctly formatted.
  • Bad request: Review the input parameters for correctness.
  • Forbidden: Ensure your API key has the necessary permissions.
  • Not found: Confirm the resource or endpoint exists and is accessible.
  • Server error: Retry later or contact WasapBom support if persistent.

Links and References

Discussion