Decide between pre-built connectors, the REST connector, the REST API, and webhooks based on your system, control needs, and real-time requirements.
Field Nation offers multiple integration paths that work together. The right starting point depends on what system you are connecting, how much control you need, and whether you need real-time event notifications.
Start from the top and follow the path that matches your situation.
Where do webhooks fit?
Webhooks are not a separate integration path — they are the real-time event layer. Pre-built connectors and the REST Connector have event sync built-in. If you use the REST API, pair it with Webhooks so you get notified when work orders change instead of polling.
| Pre-built Connector | REST Connector | REST API | Webhooks | |
|---|---|---|---|---|
| Purpose | Sync with supported platforms | Sync with any OpenAPI system | Full programmatic access | Real-time event notifications |
| Best for | Salesforce, ServiceNow, Autotask, ConnectWise, etc. | Niche or internal systems with an OpenAPI spec | Custom integrations needing full control | Knowing when something changed without polling |
| Technical skill | No code / low code | Low code | Developer required | Developer required |
| Setup time | Hours | Hours to days | Days to weeks | Minutes (once API is set up) |
| Data flow control | Field mappings via UI | Field mappings via UI | Complete programmatic control | Event-driven push (you choose which events) |
| Real-time events | Built-in | Built-in | Pair with Webhooks | This IS the event layer |
| Maintenance | Managed by Field Nation | Managed by Field Nation | Your team | Your team (endpoint + signature verification) |
Start here if a connector exists for your system.
Pre-built connectors are no-code integrations maintained by Field Nation. They handle authentication, field mapping, bi-directional sync, and real-time event triggers through a configuration UI.
Event handling: Connectors automatically trigger sync when work orders are created, updated, or change status. You do not need to set up webhooks separately.
When to escalate
Some buyers start with a connector and later add REST API calls for capabilities that connector field mappings do not cover — bulk operations, custom reporting, or advanced workflow control. The two approaches work together.
Try this if your system is not in the list above but provides an OpenAPI specification.
The REST Connector is a universal, configuration-driven connector. Upload your system's OpenAPI spec and Field Nation auto-discovers available endpoints. Map fields through the same UI as pre-built connectors.
Provide your system's OpenAPI 3.x specification file. The REST Connector parses it and discovers available endpoints, request schemas, and authentication methods.
Map Field Nation work order fields to your system's fields through the visual mapper. Set up inbound and outbound sync directions.
Configure which events (work order created, status changed, completed) trigger sync between systems. Event handling is built-in — no separate webhook setup needed.
Good fit for: Internal tools, niche platforms, or any system that exposes a REST API with an OpenAPI spec file.
Learn about the REST Connector
Use this when you need full control over data flow.
The REST API gives you direct, programmatic access to every Field Nation capability. Pair it with Webhooks for real-time event notifications.
REST API
Create, update, search, and manage work orders programmatically. Full control over data flow, business logic, and error handling.
Webhooks
Receive real-time HTTP callbacks when work orders change status, providers check in, tasks complete, or any of 33 events occur.
Without webhooks, your integration must poll the REST API repeatedly to check for changes — wasteful and slow. With webhooks, Field Nation pushes events to your endpoint the moment something happens.
| Pattern | Without Webhooks | With Webhooks |
|---|---|---|
| Detect status change | Poll GET /workorders every N minutes | Receive instant HTTP POST when status changes |
| Latency | Minutes (depends on poll interval) | Seconds |
| API calls | Hundreds per hour | Only when you need to act on an event |
| Complexity | Simpler to start | Requires endpoint + signature verification |
The four capabilities are layers, not alternatives:
Typical integration structures:
Last updated on
