Connections
Authorize Google, HTTPS JSON, and PostgreSQL data sources.
A connection is an authorized link to an external data source. Captures from a connection produce datasets.
Supported providers
| Provider | Scope | Notes |
|---|---|---|
| Google Sheets | Selected spreadsheets | Authorized via the Google consent screen |
| Google Drive | Selected CSV/JSON files | Authorized via the Google consent screen |
| HTTPS JSON | A remote endpoint | URL-based, fetched over TLS |
| PostgreSQL | Allowed relations only | TLS verified, bounded reads |
Authorization and resources
Google connections are granted through the standard OAuth consent flow; you see exactly which files and spreadsheets were selected, and can rename, reconnect, or disconnect each connection from its detail view.
PostgreSQL connections are configured with credentials that are validated against a destination policy before use: the platform verifies connectivity, TLS, and read permissions on the allowed relations with bounded metadata queries — it never evaluates arbitrary SQL from the browser.
Security model
- Credentials are encrypted at rest and are never returned to the browser after submission.
- Replacing credentials is a separate, explicit operation from editing metadata.
- Reads are bounded and deduplicated: concurrent identical requests share one source read, and per-connection concurrency is capped.
- Disabling or rotating a connection stops new captures immediately; existing dataset versions remain intact.
Health and recovery
A failed source read does not corrupt anything: live charts keep their prior capture, and the failure is visible on the connection and dataset views. Use the reconnect and test actions to diagnose authorization or connectivity problems.