> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt

# Linking Fulcrum as a source

Canonical URL: https://posthog.com/docs/data-pipelines/sources/fulcrum

> **Cloud region:** This page uses US Cloud hosts. For an EU Cloud project, use `https://eu.posthog.com` instead of `https://us.posthog.com` or `https://app.posthog.com` (app host for links).

## On this page

- [Prerequisites](#prerequisites)
- [Adding a data source](#adding-a-data-source)
- [Sync modes](#sync-modes)
- [Configuration](#configuration)
- [Supported tables](#supported-tables)
- [Troubleshooting](#troubleshooting)

**Beta release**

This source is currently in **beta**. It works end to end, but you may still hit rough edges. [Let us know](https://us.posthog.com/#panel=support%3Asupport%3Adata_warehouse%3A%3Atrue) if you do.

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_9608fcca70)

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_dark_a92b0e022d)

Let AI connect your sources for you

Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.

`npx @posthog/wizard warehouse`

![PostHog Wizard hedgehog](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)

![](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)Let AI connect your sources for you

The Fulcrum connector syncs your [Fulcrum (Spatial Networks)](https://www.fulcrumapp.com) 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](https://web.fulcrumapp.com/settings/api).

## Adding a data source

1.  In PostHog, go to the [Sources tab](https://app.posthog.com/data-management/sources) of the data pipeline section.
2.  Click **\+ New source** and click **Link** next to this source.
3.  Enter your credentials (see [Configuration](#configuration) below) and click **Next**.
4.  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-ApiToken` header 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_at` timestamp). 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](https://posthog.com/docs/data-pipelines/sources.md#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 | — | — |
| `records_history` | Every version of every record, including edits, corrections and deletions, so field-level change can be analysed over time. | Full refresh | — | — |
| `audit_logs` | Read-only trail of user activity across the organization: who changed which form, record, membership or other resource, and when. | Incremental, Full refresh | time | — |
| `groups` | Groups used to manage member permissions to forms, layers and projects in bulk. Resolves the group ids carried on memberships and projects. | Full refresh | — | — |
| `form_history` | Past versions of each form's schema, needed to interpret records collected under an earlier form definition. | 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](https://posthog.com/docs/data-warehouse/troubleshooting.md). If that doesn't help, [contact support](https://us.posthog.com/#panel=support%3Asupport%3Adata_warehouse%3A%3Atrue) – we're happy to help.