WebhookReceiver is for customers using push mode: when your product is configured with a forward_url, the connector POSTs events to your endpoint as JSON. WebhookReceiver handles signature verification, JSON parsing, and dispatching to typed callbacks β giving you the same ActionsPayload / SummaryPayload interface that SSE users get from AsyncConnectorClient.
Use it when you want the connector to push events to your server rather than your server pulling from the SSE stream.
How push mode works
X-Connector-Signature header for verification:
Setup (FastAPI)
Setup (Flask / sync)
Constructor
string
default:"\"\""
HMAC-SHA256 signing secret configured on the connector (
integration_config.secret).
Pass an empty string to skip verification β useful in development but not recommended
in production.Callable[[ActionsPayload], None]
default:"None"
Sync or async callback called for every
actions event. Can also be registered
via .on_actions(fn) after construction.Callable[[SummaryPayload], None]
default:"None"
Sync or async callback called for every
summary event. Can also be registered
via .on_summary(fn) after construction.Builder interface
Both callback registration methods returnself for chaining:
Core methods
await .handle(body, signature_header) β async
Verify, parse, and dispatch. Use with FastAPI, Starlette, aiohttp, or any async framework.
ValueError if the signature is invalid. Returns the parsed ActionsPayload or SummaryPayload, or None if the event type is unrecognised.