Skip to main content
September 29, 2026New
Two optional additions to Webhook Received automations with a Review Meeting action. The default setup, with the API key header and a public or pre-signed recording link, doesn’t change.

​
Review recordings that aren’t public

Your recordings no longer need a public or pre-signed link. In the Review Meeting action, open Recording source authentication and enter a Basic, Bearer or API key credential, plus the one host it may be sent to. Triple Session downloads each recording you notify it about with that credential. The credential is encrypted when you save it, is never shown again, and is only ever sent over HTTPS to the pinned host. Replace it at any time without downtime.

​
Signed webhook requests

Notifications can now be signed instead of carrying the API key. The secret never travels with the request, and a captured request stops working after 5 minutes. Select Signed requests only on the trigger to reject anything unsigned. Existing integrations keep working unchanged: the API key header, JSON and form-encoded bodies are all still accepted. See Signed requests and Recordings behind authentication for setup, the Recording source contract, security details and Node.js, PowerShell and curl samples.