Complete catalog of all 33 webhook events covering the work order lifecycle, status changes, and activity events.
Events are organized into three main categories. Select a category to explore available events.
Lifecycle Events
13 events - Core work order actions like creation, routing, assignment, and completion.
Status Changes
19 events - Work order status transitions (draft, published, assigned, approved, paid, etc.)
Activity Events
Overlaps with lifecycle - Messages, uploads, task updates, schedule changes, and tags.
These events track the primary actions in a work order's journey.
These events fire when a work order transitions between statuses.
When creating a webhook, you can subscribe to specific events to reduce noise.
Subscribe to everything for full synchronization.
{
"events": [
"workorder.created",
"workorder.routed",
// ... all 33 events
]
}Focus on the operational flow.
{
"events": [
"workorder.created",
"workorder.routed",
"workorder.requested",
"workorder.declined",
"workorder.task_completed"
]
}Perfect for minimal status updates.
{
"events": [
"workorder.status.published",
"workorder.status.assigned",
"workorder.status.checked_in",
"workorder.status.work_done",
"workorder.status.approved",
"workorder.status.paid"
]
}Minimal integration for high-value signals.
{
"events": [
"workorder.status.published", // Work order available
"workorder.status.assigned", // Provider assigned
"workorder.status.work_done", // Work completed
"workorder.status.approved" // Ready for payment
]
}Subscribe to 4-6 critical events initially:
workorder.createdworkorder.status.assignedworkorder.status.work_doneworkorder.status.approvedVerify your system handles events correctly before adding more.
Expand to additional events as you build new features.
Don't subscribe to events you won't use.
| Strategy | Description | Impact |
|---|---|---|
| ❌ Bad | Subscribe to all 33 events "just in case" | Increases processing overhead and log volume. |
| ✅ Good | Subscribe only to events your system processes | Cleaner logs, less noise, lower server load. |
Maintain internal documentation mapping events to your handlers:
| Event | Handler | Purpose |
|---|---|---|
workorder.status.published | publishHandler() | Notify provider network |
workorder.status.assigned | assignHandler() | Update dispatch board |
workorder.status.work_done | completeHandler() | Trigger approval flow |
Last updated on