Marketers
See which channels and pages bring visitors who convert.
Review Turso libSQL databases, rows read and written, storage bytes and API tokens in a read-only data source.
Updated November 2026
| Database name | Rows read | Rows written |
|---|---|---|
| app-prod-db | 1,240 | 1,240 |
| 640 | 640 | 640 |
| 210 | 210 | 210 |
See which channels and pages bring visitors who convert.
Get a weekly traffic summary without opening another dashboard.
Send each client the same clean traffic report every month.
Read databases, usage summaries and token metadata using your Turso Platform API token.
Datapipe reads Turso data for reports. It never changes anything in Turso.
Databases are never modified.
Combine database hostnames, rows read and storage bytes in one report.
An API key or token from your Turso account.
Read access only. Datapipe never changes anything in Turso.
Read-only. Databases are never changed, token values are not included, and usage covers up to 500 databases per report.
Current databases, usage per database totalled over the report dates, and Platform API token names from Turso.
Read-only reporting access using your Turso organization slug and Platform API token. Databases are never modified.
Read-only. Databases are never changed, token values are not included, and usage covers up to 500 databases per report.
3 reporting datasets, each with its own fields. Pick one in the app, then choose your columns.
Current databases in your Turso organization with hostname, group, primary region and whether writes are blocked. Not filtered by report dates.
Rows read, rows written, storage bytes and bytes synced per Turso database, totalled over the report dates.
Current Platform API tokens of the Turso user who owns the token, with name, creation date and the organization each is limited to (blank when it covers every organization). Token values are not included.
17 report fields across 3 datasets.
Hover or tap a field to see what it means. Custom fields from your own account appear after you connect.
No fields match. Try another search or choose All.
Claude or ChatGPT can read the same numbers. You ask in a normal sentence, and the answer stays with your report.
Summarize Turso libSQL database regions, rows read/written, and storage bytes.
app-prod-db in iad recorded 18.4M rows read and 412 MB storage across primary and replica nodes.
Current databases in your Turso organization with hostname, group, primary region and whether writes are blocked.
Use this template →Rows read, rows written, storage bytes and bytes synced per Turso database, totalled over the report dates.
Use this template →Current Platform API tokens of the Turso user who owns the token, with name, creation date and the organization each is limited to (blank when it covers every organization).
Use this template →Create a project and choose Turso in Data sources.
Pick where it goes. This one sends the numbers to Google Sheets.
Pick where it goes. Choose databases, usage or tokens and a destination.
| Database name | Rows read | Rows written | Storage bytes | Bytes synced | Database name | Group | Primary region |
|---|---|---|---|---|---|---|---|
| app-prod-db | 1,240 | 1,240 | 1,240 | 1,240 | app-prod-db | default | iad |
| 640 | 640 | 640 | 640 | 640 | 640 | 640 | 640 |
| 210 | 210 | 210 | 210 | 210 | 210 | 210 | 210 |
Sample numbers, so you can see the shape. Your report uses your accounts.
Add both to the same project. Each keeps its own report, so you can check them side by side or ask ChatGPT or Claude a question that needs both.
Free to start. Paid plans add more data sources and refresh faster.
Free and Starter refresh once a day. Pro refreshes every hour. Agency refreshes every 15 minutes on the first 50 data sources.
No. Name a project, add a data source, then choose a report and destination.
OAuth means you sign in with the service and grant access, without pasting an API key. Datapipe works with multiple partners to provide that sign-in. Some partners already provide it. Some integrations are API-only at present, so you paste a key or token. OAuth is coming soon for some. Some partners do not provide OAuth at all. The setup steps on each integration page say how that source connects. Signing in is only how the connection is made. It is not permission to change records. Where a source supports changes, those writes stay off until the workspace owner turns specific actions on and approves each one. We do not promise OAuth on every source, and we do not share dates.
This integration is read-only in Datapipe. You can report on Turso, send the reports to your destinations and ask an AI assistant about them. Datapipe never changes anything in Turso. Read-only reporting access using your Turso organization slug and Platform API token. Databases are never modified.
This page lists 17 report fields across 3 datasets. You pick the columns when you build the report.
Current databases, usage per database totalled over the report dates, and Platform API token names from Turso. Account permissions and the records available from the provider determine which rows can be read.
One for each Turso account you add to a project. Adding the same account to another project counts again. Reports and destinations do not use extra data sources.
Yes. The same numbers can go to a sheet, a chart, a warehouse, or an assistant.
Build the report first, then add Turso when you are ready.