Configure the mechanism that matches your use case; they do not share one universal payload or delivery guarantee.
Verify your receiver
Use a temporary receiver under your control. Send synthetic data, verify the observed method and payload, and test how your receiver handles repeated deliveries and non-success responses.Workflow webhook contract
The workflow webhook renders your configuredpayload_template once. For object payloads, it adds call_disposition if your template did not already supply it.
The current wire headers retain their existing names:
These are correlation headers, not cryptographic signatures. Use the configured credential and authentication mechanism expected by your receiver.
Network failures and HTTP 408, 425, 429, 500, 502, 503, and 504 are eligible for retry. The delivery is stored and retried with backoff; exhausted attempts and permanent failures become dead-letter deliveries. Limits depend on deployment configuration.
Both an HTTP-tool request and a post-call workflow webhook have been observed at a controlled receiver. The post-call test matched a unique marker in the configured payload and included
call_disposition after the controlled SIP run completed. Retry and dead-letter behavior is covered by local tests; a live delivery-failure drill has not been performed.