Supabase

Query Supabase from any myai canvas, function, or chat — PostgreSQL with auth, storage, and Row Level Security awareness baked in.

Data & AnalyticsAvailable now

Supabase is the open-source Firebase alternative that's become the default backend for a lot of modern app builds — Postgres under the hood, with auth, storage, and real-time subscriptions stitched on top. The integration treats Supabase like Postgres (because it is) but with awareness of the auth and storage schemas that make Supabase-specific.

What you can do

  • Full PostgreSQL SQL access — every query that works against vanilla Postgres works here.
  • Row Level Security aware — when RLS policies are in play, queries respect them per the connected user.
  • Auth and storage schema access — read user records, storage object metadata, and any custom application tables from the same connection.
  • JSONB-aware queries for the document-style columns Supabase apps lean on heavily.
  • Connection pooler support — port 6543 by default for better concurrency under load; switch to direct port 5432 when needed.
  • Schema introspection — what tables exist, what columns, what indexes — queryable as structured data.

How to connect

Supabase is PostgreSQL under the hood. Connect via the standard PostgreSQL wire protocol using your project's database host and password. SSL is required.

Setup:

  1. In your Supabase Dashboard, select the project.
  2. Go to Settings → Database.
  3. Copy the host and password from the Connection string section.
  4. Default port: 6543 (connection pooler — recommended). Use 5432 for direct connections if needed.
Connect Supabase in myai

Common use cases

  • RLS-aware reporting — chat-driven queries against the app database that automatically scope to the user's permissions.
  • Cross-source dashboards mixing Supabase app data with warehouse data (BigQuery, Snowflake) in a single canvas.
  • Daily user-activity digests — scheduled function reads yesterday's signups, conversions, or events, posts to the team's chat.

Reference

  • Connection model: PostgreSQL wire protocol against your Supabase project
  • Default port: 6543 (pooler) — switch to 5432 for direct connections
  • Scope: ~8 operations spanning SQL execution, schema introspection, transactions
  • For vanilla Postgres (not Supabase), see PostgreSQL
PreviousSnowflakeNextTeamcenter