Quickbase Connector

Overview

The Quickbase connector enables seamless integration between Quickbase applications and Field Nation:

Table-based sync: Create work orders from any Quickbase table
REST API integration: Modern JSON API with user tokens
Webhook triggers: Real-time notifications via Quickbase automations
Bidirectional sync: Data flows both directions automatically
Custom fields support: Map any Quickbase field

At a Glance

Authentication

User Token (Bearer token)

Supported Objects

Any Quickbase table in your apps

Trigger Mechanism

Quickbase Automations (webhooks)

Data Flow

Bidirectional (create, update)

How It Works

Configure Automation

Create Quickbase automation that triggers on record changes

Webhook Fires

Quickbase sends record ID to Field Nation when conditions met

Fetch Record Data

Integration Broker retrieves complete record from Quickbase REST API

Apply Mappings

Transform Quickbase record into Field Nation work order

Create Work Order

Work order created with correlation ID for bidirectional sync

Common Use Cases

Service Request Dispatch

Table: Service Requests
Trigger: Status = "Approved"
  → Work order created in Field Nation

Work Order Tracking

Table: Field Work Orders
Trigger: New record added
  → Automatic Field Nation dispatch

Status Synchronization

FN Work Order = "Completed"
  → Quickbase record Status = "Complete"
  → Completion date updated

Features

Field Mapping Capabilities

All Field Types: Text, numeric, date, checkbox, user, relationship
Formula Fields: Access calculated values
Related Tables: Map fields from related tables via relationships
Multi-select fields: Handle comma-separated values
File Attachments: Optional file sync

Supported Operations

Prop

Type

Description

Work Order Creation?Inbound

Create FN work order from Quickbase record

Record Updates?Outbound

Update Quickbase when FN work order changes

Bidirectional Sync?Both

Keep data synchronized in both systems

Prerequisites

Quickbase Requirements

Authentication

Quickbase uses User Token (Bearer token):

Authorization: QB-USER-TOKEN {user_token}

Generate Token:

Quickbase → Profile → Manage User Tokens
New User Token
Select applications to grant access
Copy token immediately (shown once)

Security: User tokens have same permissions as user. Create dedicated integration user with minimum required access.

Best Practices

✅ Use dedicated integration user
✅ Grant minimum table access needed
✅ Test in sandbox app first
✅ Use Quickbase automations (not external webhooks)
✅ Monitor API usage limits

Limitations

API rate limits: 10 requests/second per user token
Each sync consumes 2-3 API calls
Complex relationships may require custom JSONNET
Formula fields are read-only

User Token

Table Access

API Permissions

On this page

Quickbase Connector

User Token

Table Access

API Permissions

On this page