Outbound webhooks let external systems react to run outcomes — post a Slack message, update a dashboard, trigger a downstream pipeline. Forge sends a signed HTTP POST to your URL every time a run completes, fails, is blocked, or is cancelled.

Step 1: Register a webhook

Go to Settings → Integrations → Webhooks. Click Add webhook. Enter the HTTPS URL of your server endpoint and an optional description. Forge generates a 32-byte signing secret automatically.

Step 2: Handle the payload

Your endpoint will receive a POST request with a JSON body. Forge expects an HTTP 2xx response within 10 seconds.

{
  "event":            "run.completed",
  "run_id":           "uuid",
  "run_title":        "Market Entry Analysis",
  "status":           "completed",
  "completed_agents": 8,
  "failed_agents":    0,
  "timestamp":        "2026-05-15T10:00:00Z"
}

Step 3: Verify the signature

Every request includes an X-Forge-Signature: sha256=... header. Always verify it before processing. See the Verify webhook signatures guide for full code examples.

Step 4: Check the delivery log

In Settings → Integrations → Webhooks, click Delivery log on any webhook to see the last 20 deliveries. Each row shows the event type, HTTP status, response time, and any error. Click Replay to resend a delivery — useful for debugging or recovering from a temporary server outage.

Tip:You can register up to 10 webhooks per account and toggle each independently. Use different webhooks for different destinations (Zapier, custom server, n8n) so you can disable one without affecting the others.

Set up outbound webhooks

Step 1: Register a webhook

Step 2: Handle the payload

Step 3: Verify the signature

Step 4: Check the delivery log

Next steps