Waapify icon

Waapify

Send WhatsApp messages via Waapify API

Actions11

Overview

This node integrates with the Waapify API to manage WhatsApp messaging and instance settings. Specifically, for the Instance - Set Webhook operation, it allows users to configure a webhook URL on their WhatsApp instance to receive event notifications such as incoming messages or status updates.

Typical use cases include:

  • Setting up real-time event notifications from a WhatsApp instance to an external system.
  • Enabling or disabling webhook callbacks dynamically based on workflow logic.
  • Automating WhatsApp integration by programmatically managing webhook URLs without manual configuration.

For example, a user can set a webhook URL to forward all incoming WhatsApp messages to a CRM system or trigger other workflows when certain events occur.

Properties

Name Meaning
Webhook URL The URL endpoint where the WhatsApp instance will send webhook notifications.
Enable Boolean flag to enable (true) or disable (false) the webhook on the WhatsApp instance.

Output

The node outputs a JSON array containing the response from the Waapify API after setting the webhook. The structure typically includes confirmation of the webhook URL being set or disabled, along with any relevant status information returned by the API.

Example output JSON (simplified):

[
  {
    "status": "success",
    "webhook_url": "https://example.com/webhook",
    "enabled": true
  }
]

No binary data is produced by this operation.

Dependencies

  • Requires an active connection to the Waapify API via an API key credential.
  • The node uses the base URL, instance ID, and access token from the configured credentials to authenticate requests.
  • Network access to the specified webhook URL must be available for the WhatsApp instance to send events successfully.

Troubleshooting

  • Common issues:

    • Invalid or unreachable webhook URL: Ensure the URL is publicly accessible and correctly formatted.
    • Authentication errors: Verify that the API key credential is valid and has the necessary permissions.
    • API rate limits or downtime: Check Waapify service status if requests fail unexpectedly.

  • Error messages:

    • Waapify API Error: <message> — Indicates an error response from the Waapify API. Review the message for details such as invalid parameters or authentication failure.
    • HTTP status codes like 400 or 401 suggest bad request or unauthorized access respectively; verify input parameters and credentials.

  • Resolution tips:

    • Double-check the webhook URL format and availability.
    • Confirm that the "Enable" property is set according to your intent.
    • Use the node's "Continue On Fail" option to handle errors gracefully in workflows.

Links and References

Discussion