Wapify Trigger icon

Wapify Trigger

Receive WhatsApp messages via Wapify webhooks

Overview

The Wapify Trigger node is designed to receive WhatsApp messages via webhooks from the Wapify service. It listens for incoming WhatsApp messages and triggers workflows based on those messages. This node supports multiple message types including text, batch (grouped) messages, images, documents, audio, and video.

Common scenarios where this node is beneficial include:

  • Automating responses or processing of incoming WhatsApp messages.
  • Filtering messages by keywords to trigger specific workflows.
  • Handling both individual and batch messages in a standardized format.
  • Debugging webhook payloads by optionally including raw data.

Practical examples:

  • A customer support workflow that triggers when a user sends a WhatsApp message containing certain keywords like "help" or "start".
  • An automated media processing pipeline that activates when image or video messages are received.
  • Logging or analytics workflows that process batches of messages sent together.

Properties

Name Meaning
Message Types Types of messages to trigger on. Options include: Text Messages, Message Batches, Image Messages, Document Messages, Audio Messages, Video Messages. Default is Text and Batch messages.
Manual Webhook Setup Instructions Step-by-step instructions on how to set up the webhook URL in the Wapify dashboard to enable receiving WhatsApp messages.
Additional Options Collection of optional settings:
• Include Raw Payload: Whether to include the complete raw webhook payload in the output for debugging.
• Filter Keywords: Comma-separated list of keywords to filter incoming messages.

Output

The node outputs JSON data representing the received WhatsApp message(s) with a consistent structure:

  • Common fields:

    • type: The message type (e.g., "text", "batch").
    • from: Sender's phone number or ID.
    • to: Recipient's phone number or ID.
    • message: The main message content (string or object depending on type).
    • timestamp: ISO string timestamp of when the message was sent.
    • messageId: Unique identifier of the message.

  • For batch messages:

    • batchId: Identifier for the batch.
    • messageCount: Number of messages in the batch.
    • rawMessages: Array of raw messages in the batch.

  • For text messages:

    • rawMessage: The raw message object.

  • If Include Raw Payload option is enabled, the entire original webhook payload is included under rawPayload.

If the node receives unsupported message types or messages filtered out by keyword, it responds with appropriate HTTP status but does not emit workflow data.

Binary data (such as images, audio, video) is represented by metadata including URLs and mimetypes; actual binary content is not directly output by the node.

Dependencies

  • Requires a valid API authentication credential for Wapify to configure and enable the webhook.
  • The user must configure the webhook URL in their Wapify dashboard linked to their WhatsApp phone number.
  • No additional external dependencies beyond standard n8n webhook and credential management.

Troubleshooting

  • Invalid payload: If the webhook receives malformed or unexpected data, the node returns HTTP 400. Ensure the Wapify webhook is correctly configured and sending data in the expected format.
  • Message type filtered: If the incoming message type is not selected in the node’s "Message Types" property, the node will ignore it and respond with HTTP 200 without triggering the workflow.
  • Message filtered by keywords: When filtering by keywords, if none match the message content, the message is ignored with HTTP 200 response.
  • No valid message data found: Legacy or unrecognized payloads may not be processed if they lack required fields.
  • To debug issues, enable the "Include Raw Payload" option to inspect the full webhook data received.

Links and References

Discussion