Integrations for tables

Some integrations can be used as a data source for tables.

That means you can connect an external service (like Airtable, Google Sheets, or Supabase), then create a table in WeWeb that reads and writes data through that integration.

What this enables

Using an integration as a table data source is useful when you want the external service to stay the “source of truth”, but you still want WeWeb features on top.

For example, you can:

• Create views with filters, sorting, and parameters on top of the external data.
• Add access rules so users only retrieve data they’re allowed to see.
• Build API Endpoints to add secure logic (validation, extra checks, or multi-step flows).

Create a table from an integration

1. Go to Data & API → Tables.
2. Click + Add table.
3. In Select a data source, choose the integration you want (for example Airtable).
4. Create or select a Connection.
5. Fill in the table setup (this depends on the integration).
6. Finish setup.

After setup, WeWeb also creates an All Rows view for the table so you can start retrieving data right away.

YOUR PROJECT SERVER AS THE MIDDLE LAYER

When you set up an integration as a table data source, your project’s server sits in between your app and the external service.

So instead of your users talking directly to Airtable (or another data source), your app talks to your project’s server first, and the server can then apply things such as access rules before it retrieves data from the integration.

Here’s what that looks like:

Practical examples (business apps)

Example: Airtable as a data source, with secure access in WeWeb

Use this when Airtable is easy for your team to manage, but you want stronger control over what end users can access.

Typical flow:

1. Connect Airtable and create a table from it in WeWeb.
2. Create a view that only returns what the signed-in user should see.
3. Expose that view through your app (or call it from an API Endpoint when you need extra checks).

This lets you keep Airtable as the data source, while still enforcing security rules in WeWeb.

Example: “Service layer” API Endpoints on top of an integration table

Use this when you want to do work that would be awkward in the external service.

For example:

• Validate inputs before writing to the external table.
• Combine data from multiple sources (tables + integrations).
• Transform data before sending it back to the interface.

Learn more

Browse all available integrations and learn how to connect each one.

Integrations →

CONTINUE LEARNING

Learn how to protect data with views and access rules.

Using views →