WasapBom icon

WasapBom

Send WhatsApp messages via WasapBom API

Actions8

Overview

This node integrates with the WasapBom API to manage WhatsApp contacts and send WhatsApp messages. Specifically, the Add Contact operation under the Contact resource allows users to add a new contact to their WhatsApp account via the WasapBom service.

Typical use cases include:

  • Automating the addition of new contacts collected from forms or CRM systems into WhatsApp.
  • Enriching contact information with additional details such as titles, notes, and custom fields.
  • Streamlining customer communication by ensuring contacts are pre-registered before sending messages.

For example, a user can automatically add a new client’s phone number and name to their WhatsApp contacts list, along with custom tags or notes for better organization.

Properties

Name Meaning
Contact Name The full name of the contact to add.
Phone Number The phone number of the contact to add. Must include country code without the "+" sign (e.g., 60123456789).
Additional Fields Optional extra information about the contact:
- Title The contact's title (e.g., Mr., Mrs., Dr.).
- Notes Any notes related to the contact.
- Custom Fields Up to 10 custom label-value pairs to store additional data about the contact.

Output

The node outputs an array of JSON objects representing the response from the WasapBom API after attempting to add the contact. Each output item corresponds to one input item processed.

The JSON structure typically includes confirmation of the added contact or error details if the operation failed.

No binary data 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.
  • Proper network access to the WasapBom API is necessary.

Troubleshooting

Common Issues

  • Authentication failures: Occur if the API key is missing, invalid, or expired.
  • Validation errors: Happen when required fields like contact name or phone number are missing or incorrectly formatted.
  • API rate limits or server errors: Temporary issues on the WasapBom side may cause failures.

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: Ensure all required fields are correctly filled and formatted, especially the phone number without the "+" prefix.

  • Bad request: "The request was improperly formatted or contained invalid parameters."
    Resolution: Double-check the input parameters and their types.

  • 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: This usually indicates an incorrect API endpoint or resource; verify the node configuration.

  • Server error: "The WasapBom server encountered an error."
    Resolution: Retry later or contact WasapBom support if persistent.

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

Links and References

Discussion