BizwaChat Trigger icon

BizwaChat Trigger

Receive BizwaChat webhook events from the tenant Webhook Management screen.

BizwaChat Trigger

AI-generated

Overview

This node acts as a webhook trigger for BizwaChat events. It listens for incoming webhook POST requests from BizwaChat, allowing users to receive various event notifications such as message received, contact updates, WhatsApp message events, and more. Users can filter which event types to accept, include HTTP headers in the output, and optionally verify the webhook signature for security. This node is useful for automating workflows based on real-time BizwaChat events, such as processing incoming messages, updating contact information, or handling WhatsApp-specific events.

Use Case Examples

  1. Automate customer support by triggering workflows when a new message is received in BizwaChat.
  2. Update CRM records automatically when contact information is created or updated in BizwaChat.
  3. Monitor WhatsApp message delivery and status updates to trigger follow-up actions.

Properties

Name Meaning
Setup Instructions to copy the webhook URL into BizwaChat's Webhook Management and enable desired events.
Event Types Select which BizwaChat event types to accept and trigger the workflow on. Leave empty to accept all events.
Include Headers Whether to include the incoming webhook HTTP headers in the output item.
Verify Signature Enable validation of the X-Webhook-Signature header to verify webhook authenticity.
Signing Secret The webhook signing secret configured in BizwaChat, required if signature verification is enabled.

Output

JSON

  • webhookResponse
    • eventType - The type of BizwaChat event received.
    • received - Indicates the webhook event was received successfully.
    • filtered - Indicates if the event was filtered out due to event type selection.
  • workflowData
    • 0
      * 0
      * json - The full JSON payload of the webhook event, optionally including HTTP headers if enabled.

Dependencies

  • An API signing secret credential for webhook signature verification if enabled.

Troubleshooting

  • If signature verification is enabled but the signing secret is missing or empty, the node throws an error indicating the secret is required.
  • If the X-Webhook-Signature header is missing or invalid, the node throws an error indicating the webhook signature is missing or invalid.
  • If event types are selected and the incoming event type does not match any selected, the event is filtered and the workflow does not continue.
  • Ensure the webhook URL is correctly copied into BizwaChat's Webhook Management and the desired events are enabled there.

Discussion