Field NationDeveloper Platform
Field NationDeveloper Platform
Pre-built ConnectorsGetting Started

PSA Platforms

CRM & Support

ERP & Project Management

NetSuite ConnectorConfigurationWorkflow Setup

Universal

PlatformsNetSuite

NetSuite Connector

Integrate NetSuite ERP with Field Nation for automated work order creation and service management synchronization.


Overview

The NetSuite connector enables seamless integration between NetSuite ERP and Field Nation:

  • Service order dispatch: Create work orders from NetSuite service records
  • SuiteTalk SOAP API: Token-based authentication (TBA)
  • SuiteScript integration: Custom triggers via SuiteScripts
  • Bidirectional sync: Status, costs, and completion data flow both ways
  • Custom fields support: Map NetSuite custom fields

At a Glance

Authentication

Token-Based Authentication (TBA) - Account ID + Consumer Key/Secret + Token Key/Secret

Supported Records

Service Orders, Cases, Custom Records

Trigger Mechanism

SuiteScript + Webhooks

Data Flow

Bidirectional (create, update, financial)


How It Works

Deploy SuiteScript

Deploy custom SuiteScript in NetSuite that monitors service records

Script Triggers

SuiteScript evaluates conditions (status change, custom field) and sends webhook

Field Nation Receives

Integration Broker receives notification with NetSuite record ID

Fetch Record Data

Broker retrieves complete record via SuiteTalk SOAP API

Create Work Order

Transformed data creates Field Nation work order


Common Use Cases

Service Order Dispatch

Service Order Status = "Ready for Dispatch"
  → SuiteScript triggers
  → Work order created
  → Service order updated

Case-Based Dispatch

Case Type = "On-Site Service"
AND Status = "Escalated"
  → Webhook fires
  → Field technician dispatched

Financial Tracking

FN Work Order = "Approved"
  → NetSuite Service Order updated
  → Costs synchronized
  → Invoice generated

Features

Field Mapping Capabilities

  • Standard Fields: Title, Message, Status, Sales Order Number
  • Custom Fields: All custom fields on target record type
  • Related Records: Customer, Contact, Location, Item
  • Financial Fields: Cost, revenue, billing codes
  • Sublists: Line items, time entries, expenses

Supported Operations

Prop

Type

Description

Work Order Creation?Inbound

Create FN work order from NetSuite service record

Cost Sync?Outbound

Update NetSuite with actual costs from Field Nation

Status Updates?Bidirectional

Sync status changes both directions


Prerequisites

NetSuite Requirements


Authentication

NetSuite uses Token-Based Authentication (TBA) with OAuth 1.0:

Account ID: {account_id}
Consumer Key: {consumer_key}
Consumer Secret: {consumer_secret}
Token ID: {token_id}
Token Secret: {token_secret}

Generate Credentials:

  1. Enable TBA in NetSuite Features
  2. Create Integration Record → Get Consumer Key/Secret
  3. Generate Access Token → Get Token ID/Secret
  4. Note Account ID (found in Setup → Company Information)

Security: Token Secret shown ONCE during generation. Save immediately to secure location.


Best Practices

  • ✅ Use dedicated integration role
  • ✅ Test SuiteScripts in sandbox account
  • ✅ Monitor SuiteTalk API usage
  • ✅ Handle NetSuite's complex data model carefully
  • ✅ Document SuiteScript logic thoroughly

Limitations

  • SOAP-based API (more complex than REST)
  • Token rotation required periodically
  • SuiteScript deployment requires technical expertise
  • Sublist/line item mapping can be complex

Last updated on

Workflow Setup

Create ServiceNow Business Rules and REST Messages to automatically send work order data to Field Nation.

Configuration

Configure the NetSuite connector with Token-Based Authentication and SuiteTalk SOAP API credentials.

On this page

Overview
At a Glance
How It Works
Deploy SuiteScript
Script Triggers
Field Nation Receives
Fetch Record Data
Create Work Order
Common Use Cases
Service Order Dispatch
Case-Based Dispatch
Financial Tracking
Features
Field Mapping Capabilities
Supported Operations
Prerequisites
NetSuite Requirements
Authentication
Best Practices
Limitations