Return

Set up backend logic on top of Supabase

Keep Supabase as your database and use WeWeb API Endpoints as the secure logic layer on top.

TEMPLATE AVAILABLE

If you wish to skip the manual setup, there is a workflow template available called Get data w/Supabase. You can find it inside the templates available when creating an API workflow.

RECOMMENDED SUPABASE MODE

This guide matches Supabase as data source only (the recommended option when you create your first Supabase table). In that mode, WeWeb manages API Endpoints and access control, and Supabase stays your database.

Learn about both Supabase modes →

Steps at a glance

1. Connect Supabase in WeWeb.
2. Create a Supabase table in Supabase as data source only mode (or keep that as your default).
3. Create an API Endpoint for the logic you want to protect.
4. Add Supabase actions inside that API.
5. Secure the API.
6. Call it from the Interface.

1) Connect Supabase

1. Open the Data & API tab or Interface tab, then open Integrations.
2. Add Supabase.
3. Connect the right project for your environment.
4. Confirm you can see the tables or actions you need.

2) Create your Supabase table in the recommended mode

1. Go to the Data & API tab, then open the Tables subtab.
2. Click Add Table and choose Supabase.
3. If asked How do you want to use Supabase?, choose Supabase as data source only.
4. Keep Create API endpoints on your WeWeb server to access or update table data enabled if you want starter endpoints.
5. Finish table setup.

3) Create a backend API for your logic

Create an API Endpoint when you want to do more than a simple direct table call.

Examples:

• Validate data before saving it
• Check who the current user is
• Update more than one table in one flow
• Return only the data your interface actually needs

To start:

1. Go to the Data & API tab, then open the Backend Workflows subtab and go to API Endpoints.
2. Create a new endpoint (or start from a generated table endpoint).
3. Add the inputs your interface will send (for example id, status, or note).

THESE WORKFLOWS RUN ON WEWEB

API Endpoints always run on your WeWeb server, not on your Supabase instance. That is expected, even when Supabase is connected.

4) Add Supabase actions

Inside the API Endpoint, add the Supabase action that matches your use case.

Common options:

• Database | Select To retrieve rows
• Database | Insert To create rows
• Database | Update To change rows
• Call Postgres Function When you already have logic inside Supabase
• Invoke Edge Function For custom server-side logic hosted in Supabase

Then:

1. Bind your API inputs into the Supabase action.
2. Add any checks or extra steps you need.
3. End with Send Response so the interface receives a clean result.

5) Secure the endpoint

Before calling the API from the interface, open the Security panel and decide who can use it.

Common setup:

• Authenticated When users must be signed in
• Middleware when you want to check ownership or more complex rules

One common pattern is:

1. Keep Supabase as the source of truth for the data.
2. Use WeWeb API Endpoints to decide what the interface is allowed to retrieve or change.

6) Call it from the interface

1. Open an interface workflow.
2. Add your API Endpoint action.
3. Pass the values it needs.
4. Use the response to update the UI.

Common pitfalls

It works in preview but not in production

• Check that the correct Supabase project is connected for each environment.

The API returns no rows

• Check your filters first.
• If you rely on Supabase Row Level Security, make sure the current setup allows the operation.

You put all logic directly in the interface

• Move sensitive or reusable logic into an API Endpoint so users cannot change it from the browser.

Related guides

Securing APIs

Protect your APIs so only the right users can access sensitive data.

Beginner7 min

Using table views

Use views to save filters and reuse the same dataset across your project.

Beginner6 min