WAMM PRO icon

WAMM PRO

Send direct WhatsApp messages using WAMM API
Join our community

Actions5

Overview

This node integrates with the WAMM PRO API to send WhatsApp messages and media files directly from n8n workflows. It supports sending plain text messages, media or file attachments, and scheduling messages for later delivery. This is useful for automating customer communication, marketing campaigns, notifications, or any scenario where WhatsApp messaging is required programmatically.

For example:

  • Sending a promotional message with an image attachment to a list of customers.
  • Scheduling reminders or alerts to be sent at specific times.
  • Sending templated messages with dynamic parameters.

Properties

Name Meaning
Instance ID Your WAMM instance identifier used to authenticate requests.
Phone Number Recipient's phone number in international format without the "+" sign (e.g., 40712345678).
Message Text content of the message to send. Used in "Send Message" and "Send Media & File" operations.
Schedule Time Optional time to schedule the message delivery. Format: "YYYY-MM-DD HH:mm" or "now+HH:mm".
Media URL URL of the media file to send. Required only for the "Send Media & File" operation.

Output

The node outputs an array of JSON objects, each representing the result of a single message or operation attempt. Each object contains:

  • success: Boolean indicating if the request was successful.
  • apiResponse: The full response returned by the WAMM API.
  • operation: The operation performed (e.g., "sendMedia").
  • phone: The recipient phone number.
  • instanceId: The WAMM instance ID used.
  • timestamp: ISO string timestamp when the request was made.

No binary data output is produced by this node.

Dependencies

  • Requires an API key credential for authenticating with the WAMM PRO API.
  • The node makes HTTP GET requests to the WAMM PRO API endpoint https://app.wamm.pro/api.
  • Proper configuration of the API key credential in n8n is necessary.

Troubleshooting

  • Invalid JSON format errors: When using template parameters or contact parameters, ensure the JSON strings are correctly formatted. Malformed JSON will cause the node to throw an error.
  • API failures: If the API response status is not "success" or the message is not "ok", the node logs a warning but continues. Check the API response details in the output for troubleshooting.
  • Phone number format: Ensure the phone number is in international format without the "+" prefix; otherwise, the API may reject the request.
  • Scheduling format: The schedule time must follow the specified formats ("YYYY-MM-DD HH:mm" or "now+HH:mm"). Invalid formats may cause scheduling to fail.

Links and References

Discussion