Linking Turso 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.

The Turso connector syncs your database metadata, usage, members, billing, and operational data from Turso into the PostHog data warehouse. Turso is an edge database platform built on libSQL, an open-source fork of SQLite.
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 Turso.
- You need an API token from Turso. Go to your Turso dashboard, navigate to Settings > Tokens, and create a new token.
- Back in PostHog, enter the token in the API token field, enter your Turso organization name, and click Next.
- Select the tables you want to sync, set the sync frequency, then click Import.
Once the syncs are complete, you can start using Turso data in PostHog.
Available tables
| Table | Description | Sync method |
|---|---|---|
databases | Database metadata, placement, and access settings | Full refresh |
groups | Database groups and their primary locations | Full refresh |
members | Organization members and their roles | Full refresh |
invites | Pending invitations to join the organization | Full refresh |
invoices | Issued organization invoices and their payment status | Full refresh |
audit_logs | Actions performed within the organization (off by default) | Full refresh |
database_usage | Current calendar month usage totals and instance metrics for each database | Full refresh |
database_instances | Primary and replica instances of each database, with their regions and hostnames | Full refresh |
database_stats | Top queries of each database, with the rows they read and wrote | Full refresh |
organization_usage | Current billing cycle usage totals for the organization and each database | Full refresh |
locations | Location codes where databases can be created or replicated, with their names | Full refresh |
Note: The
audit_logstable requires the Turso Scaler plan or higher. It's disabled by default – enable it in the table selection to start syncing.
Full refresh tables reload all data on each sync.
Sync limitations
All tables use full refresh only. The Turso API doesn't support pagination or server-side timestamp filters, so incremental syncing isn't available.
Configuration
| Option | Type | Required |
|---|---|---|
Organization slug | text | Yes |
Platform API token | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
databases | Database metadata, placement, and access settings. | Full refresh | — | DbId |
groups | Database groups and their primary locations. | Full refresh | — | uuid |
members | Organization members and their roles. | Full refresh | — | username |
invites | Pending organization invitations. | Full refresh | — | id |
invoices | Issued invoices and their payment status. | Full refresh | — | invoice_number |
audit_logs | Organization activity. Requires the Scaler plan or higher; enable this table to sync it. | Full refresh | — | — |
database_usage | Current calendar month usage totals and instance metrics for each database. | Full refresh | — | database_id |
database_instances | Primary and replica instances of each database, with their regions and hostnames. | Full refresh | — | database_id, uuid |
database_stats | Top queries of each database, with the rows they read and wrote. | Full refresh | — | database_id, query |
organization_usage | Current billing cycle usage totals for the organization and each database. | Full refresh | — | uuid |
locations | Location codes where databases can be created or replicated, with their names. | Full refresh | — | code |





