Wawp Trigger icon

Wawp Trigger

Starts the workflow when Wawp sends a webhook

Wawp Trigger

AI-generated

Overview

This node acts as a webhook trigger for Wawp events. It listens for incoming HTTP POST requests sent by a configured Wawp instance and triggers workflows based on the received event data. The node supports multiple specific event types, allowing workflows to respond to particular Wawp activities such as message updates, group changes, call statuses, label modifications, and more.

Common scenarios include:

  • Automating responses or logging when a new message or reaction is received.
  • Tracking group membership changes or participant updates.
  • Handling call events like received, accepted, or rejected calls.
  • Managing labels added or removed from chats.
  • Reacting to presence updates or poll vote failures.

Practical example: A workflow could be triggered whenever a "message.edited" event occurs, enabling automatic moderation or notification systems to act on message edits in real-time.

Properties

Name Meaning
Webhook Path The final URL path segment appended to the base webhook URL where Wawp will send POST requests. For example, if set to "wawp", the full webhook URL will be <base>/webhook/wawp (or /webhook-test/wawp in test mode).
Respond with 200 Immediately If enabled, the node immediately acknowledges the webhook request with a 200 OK JSON response upon receipt, without waiting for workflow execution to complete.
Heads-Up Informational multiline string listing all supported Wawp event types that can trigger this node. It reminds users to configure their Wawp instance to post events to the specified webhook URL.

Output

The node outputs data in JSON format structured as follows:

  • The first output named any contains all received events regardless of type.
  • Subsequent outputs correspond to each specific Wawp event type listed below, each outputting only events matching that type:
    • session.status
    • message
    • message.reaction
    • message.any
    • message.ack
    • message.revoked
    • message.edited
    • group.v2.join
    • group.v2.leave
    • group.v2.update
    • group.v2.participants
    • presence.update
    • poll.vote.failed
    • chat.archive
    • call.received
    • call.accepted
    • call.rejected
    • label.upsert
    • label.deleted
    • label.chat.added
    • label.chat.deleted
    • event.response
    • event.response.failed
    • engine.event

Each output item contains a JSON object representing the event payload received from Wawp.

The node does not output binary data.

Dependencies

  • Requires a properly configured Wawp instance capable of sending HTTP POST requests to the webhook URL generated by this node.
  • No external API keys or credentials are required within the node itself.
  • The user must ensure network accessibility and correct webhook URL configuration in Wawp.

Troubleshooting

  • Issue: No workflows are triggered despite Wawp sending events.

    • Cause: The webhook path configured in the node may not match the path set in the Wawp instance.
    • Resolution: Verify that the "Webhook Path" property matches exactly the path configured in Wawp's webhook settings.

  • Issue: Workflow receives no data or empty events.

    • Cause: Wawp might be sending events in an unexpected format or the event type is not recognized.
    • Resolution: Confirm that Wawp sends valid JSON payloads and that the event field corresponds to one of the supported event types.

  • Issue: Node does not acknowledge webhook requests promptly.

    • Cause: The "Respond with 200 Immediately" option is disabled.
    • Resolution: Enable this option to have the node respond immediately with a 200 OK status, preventing potential timeouts on Wawp's side.

  • Error Messages: Since the node parses incoming JSON, malformed JSON payloads may cause errors.

    • Resolution: Ensure Wawp sends well-formed JSON in the request body.

Links and References

Discussion