WhatGHL Trigger
AI-generatedSummary
Receive and handle webhook event relays from the WhatGHL n8n webhook integration, optionally validating the incoming request's signature and routing output data by event type.
Inputs
- Validate Signature — Optionally verify the x-whatghl-signature header using the provided HMAC key configured on the subaccount to ensure webhook authenticity.
- HMAC Key — The secret key for HMAC signature verification, used only if 'Validate Signature' is enabled.
- Route by event — Determines whether the node routes incoming events to specific outputs based on the normalized payload event type (true by default). If false, all events output via the default output.
Output shape
Multiple outputs corresponding to specific event types or a single default output if routing is disabled.
When 'Route by event' is enabled, the node emits data to one of 26 distinct outputs, each corresponding to a normalized WhatGHL event (e.g., message.received, session.status, group.participant.add). When disabled, all events output via the single default output. The emitted data JSON contains normalized and compacted event payloads with relevant metadata and event-specific details. Incoming webhook requests trigger the node asynchronously, responding with HTTP 401 on signature validation failure if enabled.