Linking Lightfield as a source
This source is currently in alpha. The interface and available tables may change.
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
- 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 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, andemails: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_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.
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 | — | — |
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. If that doesn't help, contact support – we're happy to help.