Introduction Real-time event notifications from Field Nation to your system. Build reactive integrations that respond instantly to work order changes.
Webhooks are server-to-server HTTP callbacks that notify your system when specific events happen in Field Nation. Think of them as "reverse API calls" – instead of your system asking Field Nation for updates, Field Nation pushes updates to you.
Loading diagram...
Subscribe - Register your HTTPS endpoint and select events to receiveEvent Occurs - A work order is created, updated, or status changesNotification Sent - Field Nation POSTs event payload to your endpointProcess & Respond - Your system processes the event and returns 200 OKAutomatic Retry - If delivery fails, Field Nation retries with exponential backoff
Real-Time Synchronization
Receive updates within seconds of events occurring. Keep your systems in sync without polling delays.
Reduced API Load
Eliminate constant polling. Webhooks push data only when something changes, reducing API calls by 95%+.
Event-Driven Architecture
Build reactive workflows that trigger automatically. Assign providers, update ERP systems, send notifications—all in real-time.
Cost Efficient
Lower infrastructure costs. No need to run continuous polling jobs or maintain complex scheduling logic.
Automatically respond to work order status changes:
Published → Auto-assign to preferred providerAssigned → Update dispatch board, notify technicianChecked In → Log start time in ERP systemWork Done → Trigger approval workflowApproved → Generate invoice, update accounting system
Keep stakeholders informed instantly:
Notify clients when work orders are completed
Alert managers when providers decline assignments
Send SMS/email when work is approved
Update dashboards in real-time
Maintain consistent data across systems:
Sync work order details to Salesforce, ServiceNow, or NetSuite
Update custom dashboards and reporting tools
Mirror Field Nation data in your database
Replicate changes to multiple downstream systems
Track every change for regulatory requirements:
Log all status transitions with timestamps
Record who approved, declined, or modified work orders
Maintain audit trails for compliance reporting
Alert on specific event patterns
Scenario Use Webhooks Use REST API Real-time updates ✅ Ideal ❌ Requires polling Event-driven workflows ✅ Perfect fit ⚠️ Complex to implement Creating work orders ❌ Not supported ✅ Use POST requests Bulk data queries ❌ Not designed for this ✅ Use GET endpoints On-demand data retrieval ❌ Event-based only ✅ Query anytime Reducing API calls ✅ Push notifications ❌ Constant polling
Best Practice : Use webhooks for event-driven updates and REST API for on-demand queries and write operations. Most integrations use both together.
Field Nation Webhooks support 33 distinct events covering the complete work order lifecycle:
Lifecycle Events Status Changes Activity Events
workorder.created - New work order createdworkorder.routed - Routed to specific provider(s)workorder.requested - Provider requested assignmentworkorder.declined - Provider declined assignmentworkorder.undeclined - Decline reversed
workorder.status.published - Work order published to marketplaceworkorder.status.assigned - Provider assigned to work orderworkorder.status.on_my_way - Provider en routeworkorder.status.checked_in - Provider arrived on siteworkorder.status.work_done - Work completedworkorder.status.approved - Work approved by buyerAnd 14 more status changes...
workorder.message_posted - New message or replyworkorder.provider_upload - Document uploadedworkorder.task_completed - Task marked completeworkorder.schedule_updated - Schedule changedworkorder.tag_added / tag_removed - Tags modified View complete event catalog →
HMAC-SHA256 signatures - Verify webhook authenticityCustom headers - Pass authentication tokensIP whitelisting - Restrict to Field Nation IPsHTTPS required - Encrypted transmission
Learn about security →
Exponential backoff - 10s, 20s, 40s, 80s, 160s, 320s, 640sUp to 7 attempts - Based on delivery success rateManual retry - Reprocess failed deliveries via APIDead letter queue - Access failed events for debugging
Understanding delivery →
Delivery logs - Every attempt recordedPre-signed log URLs - Access complete request/responseFiltering & search - Find deliveries by event, status, work orderChange history - Audit trail of webhook modifications
Monitoring webhooks →
Web UI - Visual webhook configuration dashboardREST API - Programmatic webhook managementMultiple webhooks - Different endpoints per event typeStatus control - Active, inactive, or archived
Creating webhooks →
Before working with webhooks, ensure you have:
Buyer account with active contractAPI credentials (client_id and client_secret)Webhook access enabled (contact support if needed)
HTTPS endpoint - Publicly accessible URLResponse within 5 seconds - Acknowledge deliveries quickly2xx status code - Indicate successful receipt
ngrok or localtunnel - For local testingRequest inspection tools - webhook.site, request.binMonitoring setup - Logs, alerts, dashboards Complete prerequisites guide →
Ready to receive your first webhook?
