Webhooks

Organization webhooks require the Webhooks feature (Elite). See Billing if the page is locked.

Organization webhooks vs Flow “Call webhook”

	Webhooks page	Flow action Call webhook
When it fires	Every matching organization event	Only when that Flow runs
Setup	Endpoint + event subscriptions	URL (and optional secret) on one Then step
Best for	Always-on integrations	Conditional / one-off POSTs

Use the Webhooks page for standing integrations. Use Call webhook in Flows when the POST should only happen under Flow conditions.

Set up an endpoint

Open Integrations → Webhooks under Tools in the dashboard.

Add an endpoint: name, HTTPS URL, and the events you care about (presets help).

Copy the signing secret immediately — SquadVault only shows the full value once.

Send a test event, then open the delivery in the explorer to inspect headers and payload.

Pause an endpoint to stop deliveries without deleting it. Regenerating the secret invalidates the old one immediately.

Envelope and headers

Each delivery is a JSON POST with body:

{
  "id": "evt_…",
  "type": "player.joined_team",
  "createdAt": "2026-08-04T07:00:00.000Z",
  "organization": { "id": "…", "slug": "…" },
  "data": { }
}

Headers:

Header	Meaning
`X-SquadVault-Signature`	`sha256=` + HMAC-SHA256 hex of the raw body using your signing secret
`X-SquadVault-Event`	Event type (same as `type` in the body)
`X-SquadVault-Delivery`	Delivery id
`X-SquadVault-Timestamp`	Unix timestamp (seconds)

Verify the signature before you trust the payload. Failed deliveries retry with backoff (up to 5 attempts).

Start here

Your workspace

Help

Organization webhooks vs Flow “Call webhook”

Set up an endpoint

Envelope and headers

Next

​Organization webhooks vs Flow “Call webhook”

​Set up an endpoint

​Envelope and headers

​Next

Organization webhooks vs Flow “Call webhook”

Set up an endpoint

Envelope and headers

Next