Linking Secoda 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.
Contents
The Secoda connector pulls your data catalog metadata — tables, columns, collections, users, groups, and tags — into the PostHog data warehouse.
Adding a data source
- Go to the sources tab of the data pipeline section in PostHog.
- Click + New source and then click Link next to Secoda.
- You need an API key from Secoda. Create one from Settings > API in your Secoda workspace. Copy the key value.
- Back in PostHog, paste the key in the
API keyfield and click Next. - Select the tables you want to sync, set the sync method and frequency, then click Import.
Once the syncs are complete, you can start using Secoda data in PostHog.
Available tables
| Table | Description | Sync method |
|---|---|---|
tables | Tables catalogued in Secoda from connected data integrations | Full refresh |
columns | Columns belonging to catalogued tables in Secoda | Full refresh |
collections | Collections used to group and organise resources in Secoda | Full refresh |
users | Users in the Secoda workspace | Full refresh |
groups | User groups (teams) in the Secoda workspace | Full refresh |
tags | Tags used to label and categorise resources in Secoda | Full refresh |
Incremental tables sync only new or updated records on each run. Full refresh tables reload all data on each sync.
Sync limitations
All Secoda tables are full refresh only. Secoda's list endpoints do not support server-side timestamp filtering (only exact, contains, and in operators), so there is no cursor to advance an incremental sync.
Configuration
| Option | Type | Required |
|---|---|---|
API key | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
tables | A table catalogued in Secoda from a connected data integration. | Full refresh | — | — |
columns | A column belonging to a catalogued table in Secoda. | Full refresh | — | — |
collections | A collection used to group and organise resources in Secoda. | Full refresh | — | — |
users | A user in the Secoda workspace. | Full refresh | — | — |
groups | A user group (team) in the Secoda workspace. | Full refresh | — | — |
tags | A tag used to label and categorise resources in Secoda. | Full refresh | — | — |
databases | A database (or similar top-level container) catalogued in Secoda from a connected integration. | Full refresh | — | — |
schemas | A schema catalogued in Secoda, nested under a database. | Full refresh | — | — |
integrations | An integration (connected source system) active in the Secoda workspace. | Full refresh | — | — |
lineage | A lineage edge recording that one Secoda resource feeds another. | Full refresh | — | — |
monitors | A data-quality monitor that measures a metric on a Secoda resource on a schedule. | Full refresh | — | — |
incidents | An incident a Secoda monitor raised when a measurement crossed its thresholds. | Full refresh | — | — |
monitor_measurements | One measurement a Secoda monitor took, with the thresholds in force at that time. | Full refresh | — | — |
charts | A chart catalogued in Secoda, usually a child of a BI dashboard. | Full refresh | — | — |
events | A tracked product analytics event catalogued in Secoda. | Full refresh | — | — |
event_properties | A property sent with a tracked event, catalogued in Secoda. | Full refresh | — | — |
event_categories | A category used to group tracked events in Secoda. | Full refresh | — | — |