Wazzap API icon

Wazzap API

Interact with Wazzap API

Overview

The node integrates with the Wazzap API to send WhatsApp messages programmatically. Specifically, the "Send Contact" operation under the "Message" resource allows users to send one or multiple contact cards to a specified recipient's phone number via WhatsApp.

This node is beneficial in scenarios where automated sharing of contact information is needed, such as:

  • Customer support systems sending agent contact details.
  • Marketing campaigns distributing sales representative contacts.
  • Event management apps sharing attendee or organizer contacts.

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

Properties

Name Meaning
📱 Recipient Phone Number (jid) The full phone number of the message recipient, including country code (e.g., 5217778881234). Required.
👥 Contact List (contacts) One or more contacts to send. Each contact requires:
- Full Name: The contact's complete name.
- Phone Number: The contact's phone number (digits only).
⚙️ Additional Options (options) Optional settings:
- 🔢 Priority Number: Select which sending number to use:
0 = Default
999 = Random
1–5 = Specific number slot.
- ⏱️ Delay Settings: Configure a random delay range before sending the message:
• Start (MS): Minimum delay in milliseconds.
• End (MS): Maximum delay in milliseconds.

Output

The node outputs a JSON array containing the response from the Wazzap API for the send contact operation. This typically includes status information about the message delivery attempt.

No binary data output is involved in this operation.

Dependencies

  • Requires an active connection to the Wazzap API service.
  • Needs an API authentication credential configured in n8n to authorize requests.
  • Internet access to reach https://doc.wazzap.mx/api-reference.

Troubleshooting

  • Unsupported operation error: If the node throws an error stating the operation is unsupported, verify that the Resource is set to "Message" and Operation to "Send Contact".
  • Invalid phone number format: Ensure the recipient phone number and contact phone numbers include the country code and contain digits only.
  • API authentication failures: Confirm that the API key or token credential is correctly configured and has not expired.
  • Delay settings misconfiguration: If delays cause unexpected behavior, check that the start delay is less than or equal to the end delay and both are positive integers.
  • Empty contact list: Sending without any contacts will likely fail; ensure at least one contact with valid details is provided.

Links and References

Discussion