Understand when to use a pre-built connector, the REST connector, or the REST API with webhooks, and how they work together.
Pre-built connectors and the REST API solve the same problem — moving data between Field Nation and your system. They differ in how much control you get, how much code you write, and how real-time events are handled.
| Pre-built Connector | REST Connector | REST API + Webhooks | |
|---|---|---|---|
| You write code | No | No | Yes |
| Setup | Configure through UI | Upload OpenAPI spec, configure through UI | Build and deploy custom code |
| Field mapping | Visual mapper | Visual mapper | Programmatic (you control the transform) |
| Bi-directional sync | Built-in | Built-in | You implement both directions |
| Real-time events | Built-in event triggers | Built-in event triggers | 33 webhook event types, you build the handler |
| Maintained by | Field Nation | Field Nation | Your team |
| Granular control | Limited to available mappings | Limited to available mappings | Complete |
A pre-built connector is the right starting point when:
Work Order Sync
Create and update work orders flowing both directions between your system and Field Nation.
Status Synchronization
Keep status in sync automatically — when a work order moves to "Work Done" in Field Nation, your system reflects it.
Event-driven Triggers
Built-in event handling fires sync on work order creation, status change, completion, and more. No separate webhook setup needed.
Field Mapping
Map standard fields (title, description, location, schedule, contacts) through a visual UI with transformation support.
The REST Connector is the right choice when:
The REST Connector auto-discovers your system's endpoints from the OpenAPI spec and lets you map fields through the same visual UI. It includes the same built-in event triggers as pre-built connectors.
Provide your system's OpenAPI 3.x specification. The connector parses available endpoints, schemas, and auth methods.
Use the visual mapper to connect Field Nation work order fields to your system's fields. Configure inbound and outbound sync.
Choose which work order events trigger sync. The event layer is built-in — no webhook endpoint needed on your side.
Learn more about the REST Connector
The REST API is the right choice when you need capabilities beyond what connector field mappings provide. Pair it with Webhooks for real-time event notifications.
Without webhooks, your REST API integration must poll for changes. With webhooks, Field Nation pushes events to you instantly.
| Scenario | Polling (REST API only) | Event-driven (REST API + Webhooks) |
|---|---|---|
| Detect work order status change | Poll every N minutes, compare state | Receive HTTP POST within seconds |
| Know when a provider checks in | Poll check-in endpoint repeatedly | work_order.checked_in event fires |
| Track task completion | Poll tasks endpoint per work order | work_order.task.completed event fires |
| Monitor SLA approach | Calculate from schedule on each poll | work_order.eta.updated event fires |
Field Nation supports 33 webhook event types covering the full work order lifecycle.
These approaches are complementary
You do not need to choose one path permanently. Many buyers start with a connector for fast time-to-value, then add targeted REST API calls and webhook listeners as their integration matures.
Last updated on
