Linking Gridly as a source
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.
This source is currently in alpha. The interface and available tables may change.
The Gridly connector syncs records, columns, and more into the PostHog data warehouse, so you can analyze them alongside your product data.
Prerequisites
Credentials that can read the data you want to sync. PostHog only reads data, so read access is enough.
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.
Enter your Gridly API key and a View ID to pull that view's records.
Create an API key in your Gridly company settings under Settings → API keys (Owner or Admin access is required). Use a Full Access or Read-only key.
Find the View ID in Gridly by opening your grid, selecting a view, and opening the API panel - it looks like v1v9jwwk1lwnkz. For the default Master branch this is the same as the Grid ID.
You'll be asked for:
- API key
- View ID: for example
v1v9jwwk1lwnkz.
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.
All Gridly tables are full refresh. Each sync replaces the contents of the table.
Configuration
| Option | Type | Required |
|---|---|---|
API key | password | Yes |
View ID | text | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
records | Content records of the configured Gridly view. Full refresh only. | Full refresh | — | id |
columns | Column definitions of the configured Gridly view. Full refresh only. | Full refresh | — | id |
projects | Projects in the Gridly company. Full refresh only. | Full refresh | — | id |
databases | Databases in every Gridly project, with the owning projectId. Full refresh only. | Full refresh | — | id |
grids | Grids in every Gridly database, with the owning dbId. Full refresh only. | Full refresh | — | id |
views | Views of every Gridly grid, with the owning gridId. Full refresh only. | Full refresh | — | id |
Troubleshooting
- If the connection fails with an authorization error, the API key is wrong, expired, or has been revoked. Create a new one, then reconnect the source.
- If a table syncs no rows, the credential may not have access to that data. Check its permissions, then reconnect the source.
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.