Databases
Google Cloud SQL integration
Connect Google Cloud SQL (PostgreSQL or MySQL) to Flitch and build dashboards on your data.
Flitch is an AI framework for your data. It connects to Google Cloud SQL and builds dashboards, apps, reports and workflows on your tables. Cloud SQL runs the stock PostgreSQL and MySQL engines, so Flitch connects with a connection string over the public IP. Pick the PostgreSQL or MySQL edition, choose your tables, and build dashboards, or a workflow that emails you a daily summary from them.
- Works with Cloud SQL for PostgreSQL and MySQL
- Connect read-only over the public IP
- Schedule background refresh
How do you connect Google Cloud SQL to Flitch?
Connect read-only with your database credentials over the public IP.
Start building
Pick a prompt to get started.
Google Cloud SQL integration FAQ
How do I connect Google Cloud SQL to Flitch?
Enable a public IP on your instance, add Flitch to its authorized networks, and connect with a database user. It reads your tables read-only.
Which engines does Cloud SQL support with Flitch?
Both. Cloud SQL for PostgreSQL and Cloud SQL for MySQL run the stock engines, so Flitch connects to either with standard credentials.
Do I need to open my Cloud SQL instance to Flitch?
Add Flitch to the instance's authorized networks and use a read-only database user. Flitch reads only the tables you pick and never writes back.
Can I build a Cloud SQL dashboard without SQL?
Yes. Say what you want in plain language and Flitch assembles the charts, and you can drop into custom SQL when you need precise queries. A scheduled workflow can also email the results each week.
How often does Cloud SQL data refresh?
Set a scheduled refresh and Flitch re-pulls from the instance on that cadence to keep dashboards current.
Does Flitch copy my Google Cloud SQL data?
No. Flitch queries Google Cloud SQL where it sits and pushes the aggregation down as SQL, so it reads back totals rather than holding a copy of your tables. Nothing to keep in step, nothing extra to secure, and a large table stays your database's problem rather than something Flitch has to store. The queries are generated against your data model, so a figure means the same thing on every dashboard built from it.
More in Databases
Compare Flitch with
Not the source you're after?