Source connector

Follow Up Boss connector

Follow Up Boss integration for databases, warehouses and BI tools

Real estate lead routing and agent follow-up cadences. Datrise captures Follow Up Boss entities such as leads, people, deals, action plans, calls and agent assignments, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.

The Follow Up Boss REST API v1 authenticates with HTTP Basic, OAuth 2.0, incremental runs key on lastActivityAfter (query parameter on /v1/people; sort=updated is also usable), and Follow Up Boss caps calls at Global context: 250 requests per 10-second sliding window with a valid X-System-Key (125 without); GET /v1/events is capped at 20 per 10 seconds (10 without a key), PUT /v1/people at 25 per 10 seconds.

Of the 6 objects, 5 sync as upserts keyed on the primary key and 1 as append-only streams, so each incremental run moves only what changed since the last watermark. Every object lands in its own table (for example `follow_up_boss_leads`) with a schema derived from the Follow Up Boss API rather than a flattened CSV, in any of the 43 supported destinations.

Datrise is in early access: pick a destination below to open the Follow Up Boss pipeline page, and join the waitlist to get the Follow Up Boss connector (CRM) with guided onboarding.

Incremental syncSchema-aware mapping43 destinations available

What Follow Up Boss data Datrise extracts

Each object lands in its own typed table. Sync mode is derived from the object: history-style objects append, everything else upserts.

Object	Landing table	Sync mode
leads	follow_up_boss_leads	Upsert by primary key, incremental on updated-at
people	follow_up_boss_people	Upsert by primary key, incremental on updated-at
deals	follow_up_boss_deals	Upsert by primary key, incremental on updated-at
action plans	follow_up_boss_action_plans	Upsert by primary key, incremental on updated-at
calls	follow_up_boss_calls	Append-only, incremental by timestamp
agent assignments	follow_up_boss_agent_assignments	Upsert by primary key, incremental on updated-at

Follow Up Boss API: setup facts for the connector

Verified against the vendor documentation on 2026-09-02. Unknown values are left blank rather than guessed.

API	Follow Up Boss REST API v1
Authentication	HTTP Basic, OAuth 2.0 — Per-user API key sent as the Basic Auth username with an empty password, or OAuth2 Bearer tokens for registered systems.
Pagination	cursor — Default offset/limit (max 100, default 10) is supported, but Follow Up Boss recommends the `next` cursor and `_metadata.nextLink` for deep pagination since high offsets are rejected.
Rate limit	Global context: 250 requests per 10-second sliding window with a valid X-System-Key (125 without); GET /v1/events is capped at 20 per 10 seconds (10 without a key), PUT /v1/people at 25 per 10 seconds
Incremental cursor	lastActivityAfter (query parameter on /v1/people; sort=updated is also usable) — There is no single global updatedSince parameter; each resource exposes its own time filter, and /people uses lastActivityAfter rather than a plain updated-since field.
Webhooks	Yes — Webhooks (POST /v1/webhooks subscriptions, e.g. peopleUpdated)
Bulk export	No
Deletes detectable	Yes — GET /v1/people?includeTrash=true surfaces trashed (soft-deleted) contacts that are excluded by default

Official API reference

What bites when replicating Follow Up Boss

Rate limiting uses a sliding 10-second window, not a per-minute bucket: the global context allows 250 requests per 10 seconds with a valid `X-System-Key` header but only 125 without one.
GET /v1/events is throttled separately at just 20 requests per 10 seconds (10 unauthenticated), far tighter than the 250/10s global limit, so event-stream polling needs its own backoff.
Deep pagination via `offset` becomes unreliable at high values; Follow Up Boss instead recommends following the `next` cursor and `_metadata.nextLink` returned in each page's response.
Trashed contacts are excluded from `/v1/people` results unless `includeTrash=true` is passed, so a naive sync will not detect soft-deleted leads without adding that parameter.

Compare this against every other documented API

Popular destinations for Follow Up Boss

Choose a destination below to open the ready pipeline page.

A
Airtable
Relational spreadsheet destination for ops and go-to-market teams.
View pipeline
A
Amazon Athena
Serverless SQL over S3 data lake tables.
View pipeline
A
Amazon DynamoDB
Serverless key-value and document store on AWS.
View pipeline
A
Amazon QuickSight
AWS serverless BI with SPICE and embedded analytics.
View pipeline
A
Amazon Redshift
AWS petabyte-scale warehouse with Spectrum.
View pipeline
A
Amazon S3 Data Lake
Object storage landing zone for parquet and snapshots.
View pipeline
A
Apache Superset
Open-source BI for SQL exploration, charts, and dashboard publishing.
View pipeline
A
Azure Data Lake Storage
ADLS Gen2 object storage for analytics workloads.
View pipeline
A
Azure Synapse
Microsoft analytics workspace with SQL pools.
View pipeline

Follow Up Boss connector FAQ

What Follow Up Boss data does the connector extract?: 6 objects: leads, people, deals, action plans, calls and agent assignments. Each lands in its own table with types preserved; history-style objects (1: calls) load as append-only streams.
Is the Follow Up Boss integration incremental?: Yes. After the initial full load, every run reads only records changed since the last watermark (updated-at or event timestamp) and applies an upsert or an append depending on the object.
Where can I load Follow Up Boss data?: Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each Follow Up Boss → destination pair has its own page with the object-to-table mapping.

Related CRM sources

Other sources in the same category, each with its own connector page.

Early access

Launch your Follow Up Boss pipeline with guided onboarding

Join the waitlist to get priority access for Follow Up Boss integrations with guided setup, schema-aware mapping, and production-grade incremental sync.