OpenWA Trigger
AI-generatedSummary
Register a webhook for a selected OpenWA session and start the workflow when one or more chosen events occur. The trigger can filter message events at the gateway, verify signed deliveries, and optionally suppress repeated event deliveries.
Inputs
- Session Name or ID (required) — Select or enter the OpenWA session to receive events from.
- Events (required) — Choose one or more events to subscribe to, such as message received, group changes, calls, or session status. Defaults to Message Received. Event availability and reliability can depend on the server version or WhatsApp client; for example, call outcome events require Baileys, and presence updates require a prior presence subscription.
- Webhook Secret — Optional shared signing secret, 16–255 characters. OpenWA signs deliveries with HMAC-SHA256; the trigger rejects deliveries whose signature cannot be verified.
- Filters — Optional JSON conditions applied server-side to message events. Conditions are ANDed, with up to 20 supported. Available fields include sender, recipient, body, type, isGroup, kind, chatId, fromMe, hasMedia, and mentions. Filters do not narrow session, group, or call events, and conditions on fields an event lacks can suppress it.
- Deduplicate Deliveries — When enabled, drops deliveries whose idempotencyKey has already been seen (falling back to deliveryId for older gateways). Best-effort: simultaneous deliveries can both pass.
Output shape
A single JSON item for each accepted delivery, containing the event envelope: event, timestamp, sessionId, idempotencyKey, deliveryId, and event-specific payload under data.
Message fields are nested under data. OpenWA uses at-least-once delivery, so retries or crash replays may run the workflow more than once unless deduplication is enabled; idempotencyKey is also available for downstream deduplication. Gateway-filtered and duplicate deliveries do not start workflow executions.