Add a webhook
In Desktop, open Settings → Webhooks and choose Add a webhook. Enter the Address, choose which events to Send and which project it’s For, then choose Add webhook. Copy the signing secret right away. Hoista shows it only once. From the CLI:deploy.succeeded, or a family such as deploy.*. Leave out --events to get every event. A webhook receives events from the moment you add it.
The address must be public HTTPS. Hoista won’t send to this computer, a private network or a link-local address, and it doesn’t follow redirects. It looks up the address again before every delivery.
Verify each delivery
Each delivery is aPOST with a JSON body and these headers:
In your receiver:
- Split
Hoista-Signatureintotandv1. - Compute the HMAC-SHA256 of
t, a dot and the raw request body, using the secret, as hex. Compare it withv1in constant time. - Reject the delivery if
tis more than five minutes from now. - Skip it if you’ve already handled that
Hoista-Event-Id. - Return a 2xx status within 10 seconds.
Retries and failures
If a delivery doesn’t get a 2xx response, Hoista tries again after 30 seconds, 2 minutes, 10 minutes, 1 hour and 6 hours. After that it marks the delivery as failed. In Desktop, choose Deliveries on a webhook to see each attempt.What an event allows
An event only tells your receiver that something happened. To act on it, the agent connects through the MCP server with its own access, and the normal approvals apply. Only you can add, rotate or remove webhooks. Agents can’t.Related
Connect an agent
Every tool, and how each connects.
Approvals
What Hoista asks you before an agent acts.
Data protection
What Hoista stores and where.