Use Supabase in your Crisp app.
Postgres, auth and storage you already have.
Read and write tables, call database functions, manage users and store files in a Supabase project you own. The service role key stays on the server. The public key can be used in the browser.
What you need.
Create the keys in your Supabase account and paste them in. Each one is saved under the name shown, and your app reads it by that name.
- Project URL
SUPABASE_URL- supabase.com, Project settings, API. Https://<ref>.supabase.co
- Service role key
SUPABASE_SERVICE_ROLE_KEY- Project settings, API keys, service_role (server only)
- Public (anon) key optional
SUPABASE_ANON_KEY- Project settings, API keys, anon public
How to connect.
-
Open your project, or start a new one from the dashboard.
-
Open the workspace menu and choose Connectors, then pick Supabase.
-
Paste the keys and save. Your preview restarts, and your app can use the service from then on.
Then ask for the feature
- “Show the orders table from my Supabase project”
- “Sign users in with my existing Supabase auth”
What happens to your keys.
- Each key is saved as a private setting of your project, under the name shown above.
- The AI that builds your app sees only the names. It writes code that reads each key by name, and never the value.
- The values reach your preview and your published app, and never the chat, the code or the logs.
- Open Connectors in your project to replace a key or disconnect the service. Publish again so your live app uses the change.
Service names and logos belong to their owners; Crisp is not affiliated with them. A service changes its keys and pages now and then. Found something out of date? Tell us and we will correct it.
Ask for the feature, and Crisp builds it with Supabase.
Free plan with $3 of AI usage a month, no credit card. Pro is $20 a month. See pricing.
No credit card. Your code and data stay yours.