Wapify icon

Wapify

Send WhatsApp messages using Wapify's modern API with automatic retry on failures
Join our community

Overview

This node allows sending WhatsApp text messages using the Wapify API. It is designed to reliably deliver messages by automatically retrying failed requests with configurable retry attempts, delay, and backoff strategy.

Common scenarios where this node is beneficial include:

  • Sending notifications or alerts via WhatsApp.
  • Automating customer support or marketing messages.
  • Integrating WhatsApp messaging into workflows for real-time communication.

For example, you can use this node to send appointment reminders to clients or notify a team about critical system events.

Properties

Name Meaning
From Phone Number Select one of your registered phone numbers to send the message from.
Recipient The recipient's WhatsApp number in international format (e.g., +1234567890).
Message The text content of the WhatsApp message to send.
Options Collection of optional settings:
- Max Retry Attempts Maximum number of retry attempts if sending fails (default 3, range 0–10).
- Retry Delay (seconds) Delay between retry attempts in seconds (default 2, range 1–60).
- Backoff Strategy Strategy to calculate delay between retries: "Fixed" (same delay each time) or "Exponential" (delay doubles after each retry).

Output

The node outputs an array of JSON objects, one per input item, each containing:

  • success (boolean): Whether the message was sent successfully.
  • messageId (string|null): The ID of the sent message returned by Wapify, or null if unavailable.
  • timestamp (string): ISO timestamp when the message was sent or the error occurred.
  • from (string): The sender phone number used.
  • to (string): The recipient phone number in international format.
  • message (string): The text message content sent.
  • mode (string): Mode of sending as reported by the API, or "unknown" if not provided.
  • retryAttempts (number): The configured maximum retry attempts.
  • response (object): Full raw response from the Wapify API on success.
  • error (string, present only on failure): Error message describing what went wrong.

If the node is set to continue on failure, it will output error details instead of stopping execution.

The node does not output binary data.

Dependencies

  • Requires an API key credential for authenticating with the Wapify API.
  • Needs network access to Wapify endpoints.
  • Uses internal helper methods to load available phone numbers linked to the account.
  • Configured retry logic depends on user-defined options for robustness.

Troubleshooting

Common Issues

  • Missing or invalid API key: The node requires a valid API key credential; otherwise, it throws an error.
  • Invalid phone numbers: Both sender and recipient numbers must be provided and correctly formatted (recipient must start with "+" and be in international format).
  • Network errors: Temporary connectivity issues may cause request failures but are retried automatically.
  • Unexpected API responses: If the API returns unexpected data formats, loading phone numbers or sending messages may fail.

Error Messages and Resolutions

  • "From phone number selection is required": Ensure you select a valid sender phone number.
  • "Recipient phone number is required": Provide a valid recipient number in international format.
  • "Message content is required": Enter non-empty message text.
  • "API Key is required in Wapify credentials": Configure the API key credential properly.
  • Retry-related logs indicate transient errors like timeouts or rate limits; these are handled internally but check your network and API usage limits if persistent.

Links and References

Discussion