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

# Linking Lightfield as a source

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

> **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)

![](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 Lightfield connector syncs your CRM data – accounts, contacts, opportunities, meetings, tasks, notes, lists, members, and emails – into PostHog.

## Prerequisites

You need admin access to your Lightfield organization to create an API key. Keys are scoped per resource, so grant the read scope (for example `accounts:read`) for each table you want to sync.

## 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 Lightfield, you'll need:

-   **API key** – create one in your Lightfield settings. It starts with `sk_lf_`. Grant the read scope for every table you plan to sync: `accounts:read`, `contacts:read`, `opportunities:read`, `meetings:read`, `tasks:read`, `notes:read`, `lists:read`, `members:read`, and `emails:read`. Tables without their scope show a permission warning in the schema picker.

## 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.

Lightfield's API doesn't support filtering records by their last update time, so all tables sync with full refresh.

## Configuration

| Option | Type | Required |
| --- | --- | --- |
| `API key` | password | Yes |

## Supported tables

| Table | Description | Sync method | Incremental field | Primary key |
| --- | --- | --- | --- | --- |
| `accounts` | Companies and organizations tracked in the Lightfield CRM. | Full refresh | — | — |
| `contacts` | People associated with accounts in the Lightfield CRM. | Full refresh | — | — |
| `opportunities` | Sales opportunities (deals) tracked in the Lightfield CRM. | Full refresh | — | — |
| `meetings` | Meetings recorded in Lightfield, including scheduling metadata and links to related records. | Full refresh | — | — |
| `tasks` | To-do items and follow-ups tracked in Lightfield. | Full refresh | — | — |
| `notes` | Free-form notes attached to records in Lightfield. | Full refresh | — | — |
| `lists` | Saved lists of accounts, contacts, or opportunities in Lightfield. | Full refresh | — | — |
| `members` | Members of the Lightfield organization (read-only). | Full refresh | — | — |
| `emails` | Emails synced from connected mailboxes. List items exclude the message body; subjects may be redacted for metadata-only access. | Full refresh | — | — |
| `custom_objects` | Records of the customer-defined custom object types in Lightfield, across every type the API key can read. | Full refresh | — | — |
| `field_definitions` | Field definitions for each Lightfield object type, including system and custom fields. Resolves the field slugs used as keys in the fields map of each record. | Full refresh | — | — |
| `relationship_definitions` | Relationship definitions for each Lightfield object type. Resolves the relationship keys used in the relationships map of each record. | Full refresh | — | — |

Emails sync without the message body, and subjects may be redacted when the connected mailbox only shares metadata.

## 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.