Appearance
Supabase errors and FAQs
Common pitfalls
The wrong project or environment is connected
If things work in preview but fail in production (or the other way around), check that you connected the right Supabase project and branch for each environment in the connection settings.
“Permission denied” or missing rows
This is usually caused by your Supabase Row Level Security (RLS) setup.
In Supabase, check:
- Whether RLS is enabled for the table.
- Whether you have policies that allow the operation you’re trying to do (select, insert, update, delete).
- Whether the policy conditions match the user you’re testing with.
If RLS feels too complex for your use case, you can keep Supabase as your database and use WeWeb as the layer that secures access instead.
For realtime issues, see If nothing shows up.
FAQs
Do I need different connections for Editor, Staging, and Production?
It depends. Many teams use separate Supabase projects (or branches) for each environment so tests don’t affect real data. WeWeb lets you set this up in the Supabase connection settings.
What’s the difference between “Supabase as data source only” and “Supabase as backend”?
Supabase as data source only (recommended) sends table fetches through your WeWeb server so you can manage API Endpoints and access control in WeWeb. Supabase as backend lets the browser talk to Supabase directly, so you secure data with Supabase RLS instead.
Can I keep using Supabase as the source of truth?
Yes. When you create a WeWeb table from Supabase, Supabase remains the data source. In the recommended mode, WeWeb also gives you a way to build views, API Endpoints, and access controls on top.
Do backend workflows run on Supabase?
No. Backend workflows (API Endpoints, Middleware, Event Triggers, and Functions) always run on your WeWeb server, even if Supabase is connected. You can still call Supabase actions from those workflows.
Where do I set redirect URLs for Supabase OAuth sign in?
If you use Login with Provider, set the Redirect URL in the action. This is the page you want the user to land on after they finish signing in.
Is there a realtime action for Supabase?
No. To listen to live changes, use the Supabase client of your connection in a Custom JavaScript action, in an Interface workflow. See how →
CONTINUE LEARNING
Browse all available integrations and learn how connections work.

