Field NationDeveloper Platform
Field NationDeveloper Platform
Pre-built ConnectorsGetting Started

Getting Started

Prerequisites and common setup steps for configuring Field Nation pre-built connectors.

Prerequisites

Field Nation Requirements

Prop

Type

Description

Active Buyer AccountRequired

You must have an active buyer account in Field Nation. Only buyers have access to integration features.

Admin AccessRequired

Administrative access to Field Nation's integration settings to configure connectors.

Company IDRequired

Your Field Nation Company ID (found in Company Settings > Company Profile).

Sandbox Access?Recommended

Sandbox environment access for testing before production deployment.

How to find your Company ID →

External Platform Requirements

Common Setup Workflow

All pre-built connectors follow a similar configuration pattern:

Gather Credentials

Collect required information from your external platform:

  • API credentials (keys, tokens, username/password)
  • Instance URLs or identifiers
  • Object names or IDs you want to integrate
  • Security tokens (if applicable)

Configure in Field Nation

  1. Navigate to Integration Settings in Field Nation
  2. Select your connector from available integrations
  3. Enter connection credentials
  4. Specify the external object to integrate with
  5. Configure optional settings (messaging, custom fields)
  6. Test connection and save

Configure External Platform

  1. Set up webhook or outbound message
  2. Configure automation rules (Flows, triggers, etc.)
  3. Map Field Nation's trigger URL as the destination
  4. Define conditions for when to send data to Field Nation
  5. Test the trigger

Map Fields

  1. Field Nation automatically discovers available fields
  2. Configure field mappings (source field → target field)
  3. Set transformation actions (sync, static, date convert, etc.)
  4. Add custom JSONNET transformations if needed
  5. Save field mappings

Test Integration

  1. Create a test record in your external system
  2. Trigger the automation (meet your Flow/rule conditions)
  3. Verify Field Nation work order is created
  4. Update the work order in Field Nation
  5. Confirm updates sync back to external system

Go Live

  1. Monitor first few synchronizations
  2. Review error logs for any issues
  3. Adjust field mappings if needed
  4. Document configuration for your team
  5. Set up alerting for integration errors

Integration Broker Access

All pre-built connectors are configured through Field Nation's Integration Broker interface:

Sandbox: ui-sandbox.fndev.net/integrations Production: app.fieldnation.com/integrations

First Time Setup: If you don't see the Integrations section, contact Field Nation Support to enable connector access for your account.

Understanding Field Mappings

Field mappings define how data translates between systems. Each mapping consists of:

Mapping Components

Prop

Type

Description

Source Fieldstring

The field from the originating system (e.g., external system field name or Field Nation field name)

Target Fieldstring

The field in the destination system where data will be written

Transformation Actionenum

How to transform the data: Sync (direct copy), Set Static, Array Map, Range Map, Date Convert, Concat, Custom JSONNET

Default Value?any

Value to use if source field is empty or null

Common Transformation Actions

Sync - Direct field-to-field copy with no transformation

Set Static - Always use a specific value (e.g., always set priority to "High")

Date Convert - Transform date formats between systems

Concat - Combine multiple fields into one (e.g., FirstName + LastName → FullName)

Array Map - Transform array or list data

Range Map - Map value ranges (e.g., 1-3 → Low, 4-7 → Medium, 8-10 → High)

Custom JSONNET - Write custom transformation logic for complex scenarios

Learn more about field mappings →

Data Flow Patterns

Inbound: External System → Field Nation

Loading diagram...

Trigger: Record change in external system Result: Field Nation work order created or updated

Outbound: Field Nation → External System

Loading diagram...

Trigger: Work order status change, assignment, completion, etc. Result: External system record updated

Authentication Methods

Different platforms use different authentication approaches:

Used by: Freshdesk, some custom REST APIs

Configuration:

  • Username
  • Password
  • Optional: Security Token

Format: Authorization: Basic base64(username:password)

Used by: Salesforce, ServiceNow (optional)

Configuration:

  • Client ID
  • Client Secret
  • Authorization URL
  • Token URL
  • Scopes

Flow: Authorization Code or Client Credentials

Used by: Quickbase, Smartsheet

Configuration:

  • API Key or Application Token
  • Optional: API Secret

Format: Custom header (e.g., X-API-Key: your-key)

Used by: NetSuite, Autotask

Configuration:

  • Account ID
  • Integration Token
  • Consumer Key/Secret
  • Token Key/Secret

Format: Platform-specific SOAP authentication

Best Practices

Before Configuration

  • ☐ Test in sandbox environment first
  • ☐ Document current workflow and requirements
  • ☐ Identify which fields need to sync
  • ☐ Plan for error handling and monitoring
  • ☐ Review external platform's API limits

During Configuration

  • ☐ Use descriptive names for field mappings
  • ☐ Start with minimal field set, expand later
  • ☐ Test each mapping individually
  • ☐ Document transformation logic
  • ☐ Keep track of credentials securely

After Configuration

  • ☐ Monitor first 24 hours closely
  • ☐ Set up error notifications
  • ☐ Create runbook for common issues
  • ☐ Train team on monitoring dashboards
  • ☐ Schedule regular health checks

Common Pitfalls to Avoid

Testing Your Configuration

Create Test Scenarios

  1. Happy Path: Standard work order creation and completion
  2. Required Fields: Ensure all required fields are populated
  3. Optional Fields: Verify optional fields sync correctly
  4. Status Changes: Test bidirectional status synchronization
  5. Error Handling: Intentionally trigger errors to verify error handling

Test Checklist

  • ☐ Work order created in Field Nation from external record
  • ☐ All mapped fields populated correctly
  • ☐ Status updates sync bidirectionally
  • ☐ Comments/messages sync (if enabled)
  • ☐ Error notifications received when sync fails
  • ☐ Retry logic works for temporary failures
  • ☐ Duplicate prevention works (same record not created twice)

Getting Help

Connector-Specific Guides

Each platform has detailed configuration instructions:

Salesforce

Flows & Outbound Messages setup

ServiceNow

Business Rules & REST Messages

REST Connector

OpenAPI spec configuration

View all platform guides →

Support Resources

  • Support Cases: app.fieldnation.com/support-cases
  • Phone: +1 877-573-4353 (24/7)
  • Troubleshooting: Common issues and solutions

Last updated on

Pre-built Connectors

Out-of-the-box integrations with leading field service management platforms - no code required for standard workflows.

Integration Broker Architecture

Understanding Field Nation's middleware system that powers all pre-built connectors with reliable, scalable data synchronization.

On this page

Prerequisites
Field Nation Requirements
External Platform Requirements
Common Setup Workflow
Gather Credentials
Configure in Field Nation
Configure External Platform
Map Fields
Test Integration
Go Live
Integration Broker Access
Understanding Field Mappings
Mapping Components
Common Transformation Actions
Data Flow Patterns
Inbound: External System → Field Nation
Outbound: Field Nation → External System
Authentication Methods
Best Practices
Before Configuration
During Configuration
After Configuration
Common Pitfalls to Avoid
Testing Your Configuration
Create Test Scenarios
Test Checklist
Getting Help
Connector-Specific Guides
Support Resources