WasenderAPI Trigger icon

WasenderAPI Trigger

Start workflows from WasenderAPI webhook events

WasenderAPI Trigger

AI-generated

Overview

This node acts as a trigger for workflows based on webhook events from a WasenderAPI WhatsApp session. It listens for specified WhatsApp session events such as message received, chat updates, group updates, and more, and starts workflows when these events occur. This is useful for automating responses, logging, or processing WhatsApp session activities in real-time.

Use Case Examples

  1. Trigger a workflow when a new WhatsApp message is received to automatically respond or log the message.
  2. Start a workflow when a group participant updates to manage group membership or notify users.
  3. Trigger actions on session status changes to monitor WhatsApp session health.

Properties

Name Meaning
Session The WhatsApp session to listen for events from, selectable by list or by ID.
Events The specific WhatsApp session events that will trigger the workflow. Multiple events can be selected from options like message received, chat update, group update, etc.
Options Additional request options for the WasenderAPI requests, including retry behavior on failure and maximum retry attempts.

Output

Binary

Outputs binary data for QR code images when the 'qrcode.updated' event is triggered, allowing workflows to handle QR code images directly.

JSON

  • json - The JSON payload of the webhook event, including event data, selected session details, headers, parameters, and query data.
  • binary
    • data - Binary data containing the QR code image when the 'qrcode.updated' event occurs.

Dependencies

  • Requires WasenderAPI credentials for authentication to access WhatsApp session data and manage webhook registration.

Troubleshooting

  • Webhook URL must be correctly set and match the registered webhook URL in the WasenderAPI session to avoid webhook registration errors.
  • Invalid webhook signature errors occur if the webhook secret is set and the incoming request signature does not match, resulting in a 401 response.
  • Ensure the selected session ID is valid and accessible; otherwise, API requests to fetch session data will fail.
  • If no events are selected or the incoming event is not in the selected list, the webhook will ignore the event and not trigger the workflow.

Links

Discussion