Notifications & Webhooks
How project notification rules work, what events fire, and what fields are sent.
What it does
Project notification rules send outbound webhooks when important project events happen.
Current event types:
task.result_receiveddeployment.succeededruntime.error
Configure rules from the project Overview tab. Rules are project-scoped, not account-scoped.
Setup flow
- Open a project workspace.
- Go to Overview.
- Find the Notifications card.
- Create a rule with a webhook URL and one or more trigger events.
- Send a Test event before wiring production automation.
Webhook request shape
Each webhook is sent as JSON:
{
"event_id": "delivery_12",
"event_type": "task.result_received",
"occurred_at": "2026-05-23T12:34:56.000000",
"project": { "id": "proj_xxx", "name": "My Project" },
"rule": { "id": 3, "name": "Ops channel" },
"data": { ... }
}Headers:
Content-Type: application/jsonX-D1V-Event: <event_type>X-D1V-Delivery: <delivery_id>X-D1V-Signature: sha256=...when a signing secret is configured
Result event fields
task.result_received is sent once per saved result message.
Fields inside data:
session_id: backend opcode session idturn_id: turn id when availablesubtype: upstream result subtype when availablefull_result: the full saved result textprompt: the original execute prompt matched by turn id or session
Example:
{
"event_type": "task.result_received",
"data": {
"session_id": "session_123",
"turn_id": "turn_123",
"subtype": "success",
"full_result": "Implemented the booking flow and confirmation screen.",
"prompt": "Build a booking page for a therapy service"
}
}Other event fields
deployment.succeeded usually includes:
environmentdeployment_urlcommit_hashmessage
runtime.error usually includes:
environmentorsession_iddepending on the sourcemessageerror
Receiver guidance
- Verify
X-D1V-Signatureif you configure a signing secret. - Treat delivery as at-least-once; dedupe by
event_idorX-D1V-Delivery. - Store
full_resultcarefully. It may include user requirements, generated content, or sensitive text. - Use the rule-level delivery log in the Overview page to inspect failed attempts, status codes, and response bodies.