Linking Fulcrum as a source
This source is currently in alpha. The interface and available tables may change.
The Fulcrum connector syncs your Fulcrum (Spatial Networks) field-data-collection data – records, forms, choice lists, media metadata, and more – into PostHog, so you can analyze your inspections and geospatial field data alongside your product data.
Prerequisites
You need a Fulcrum account with an active Developer Pack subscription (REST API access is gated behind this paid tier) and an API token. Each token is scoped to a single organization.
Create a token in your Fulcrum account settings.
Adding a data source
- In PostHog, go to the Sources tab of the data pipeline section.
- Click + New source and click Link next to this source.
- Enter your credentials (see Configuration below) and click Next.
- Select the tables you want to sync, choose a sync method and frequency, then click Import.
Once the syncs are complete, you can start querying this data in PostHog.
When linking Fulcrum, you'll need:
- API token – the token you created in your Fulcrum account settings, sent as the
X-ApiTokenheader on every request.
Sync modes
Each table can be synced in one of several modes, depending on what the source supports:
- Webhook (when available) – the source pushes changes to PostHog in real time. Fastest freshness, lowest ongoing cost, and the only mode that reliably captures updates and deletes.
- Incremental – only new or updated rows are synced on each run, using a cursor field (such as an
updated_attimestamp). Cheaper than a full refresh, but deletes aren't captured. - Append only – new rows are appended using a cursor field; existing rows are never updated. Ideal for immutable, append-only tables like event logs.
- Full refresh – the whole table is reloaded on every sync. Use it when a table has no reliable cursor or when you need deletions reflected.
See sync methods for a full explanation of how each mode works and how to choose between them.
The records table syncs incrementally on updated_at using Fulcrum's server-side updated_since filter, so each run only fetches records changed since the last sync. All other tables use full refresh, because Fulcrum doesn't expose a server-side change filter for them.
Fulcrum enforces an hourly request cap (roughly 5,000 requests per hour), so very large record volumes may take several syncs to backfill fully.
Configuration
| Option | Type | Required |
|---|---|---|
API token | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
records | Individual data-collection entries captured against a form, including their geospatial location and per-form field values. | Incremental, Full refresh | updated_at | — |
forms | Form definitions (the schema of a data-collection app), including their custom elements. | Full refresh | — | — |
choice_lists | Reusable lists of choices that can be referenced by choice fields across forms. | Full refresh | — | — |
classification_sets | Hierarchical classification taxonomies referenced by classification fields on forms. | Full refresh | — | — |
projects | Projects used to group and organize records. | Full refresh | — | — |
memberships | Members of the organization and their role assignments. | Full refresh | — | — |
roles | Roles that define the permissions granted to organization members. | Full refresh | — | — |
changesets | Groups of record changes captured together, used to track edits over time. | Full refresh | — | — |
webhooks | Registered webhook endpoints that receive record, form, and other change events. | Full refresh | — | — |
photos | Metadata for photos captured against records (the binary files are fetched separately). | Full refresh | — | — |
signatures | Metadata for signatures captured against records (the binary files are fetched separately). | Full refresh | — | — |
videos | Metadata for videos captured against records (the binary files are fetched separately). | Full refresh | — | — |
audio | Metadata for audio clips captured against records (the binary files are fetched separately). | Full refresh | — | — |
Troubleshooting
If your sync is failing or data looks wrong, see the Data warehouse troubleshooting guide. If that doesn't help, contact support – we're happy to help.