Start free
ActionSupabaseUpdated June 2026

How do I list every table in a Supabase database?

Short answer: Drop the "Supabase → List Tables" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Use this actionAll 7 Supabase actions
Sample request
{}
Returns
{
  "definitions": {
    "users": {
      "type": "object",
      "properties": {
        "id": {
          "type": "integer"
        },
        "name": {
          "type": "string"
        }
      }
    }
  }
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for List Tables.

Any of these apps can fire this action as part of a workflow.

Gmail → Supabase
1 Gmail triggers
Slack → Supabase
13 Slack triggers
Google Sheets → Supabase
2 Google Sheets triggers
HubSpot → Supabase
18 HubSpot triggers
FAQ

Questions about List Tables.

What does the List Tables action do in Supabase?
Lists all tables in a Supabase database (from the public schema) with their column metadata. Used to dynamically populate table pickers and column dropdowns.
What inputs does List Tables require?
List Tables has no required inputs. Sensible defaults are applied if you leave fields blank.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if Supabase returns an error?
The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.
Does List Tables support batch operations?
Yes. Run List Tables inside a Loop node to process arrays. Tiny Command handles Supabase's rate limits automatically so you don't have to throttle manually.
More actions

Other Supabase actions.

Action
Call Function (RPC)
Calls a Postgres function (RPC) defined in your Supabase database with the supplied JSON arguments. The escape hatch when typed table operations don't express the business logic you need.
Action
Delete Rows
Deletes rows from a Supabase table that match a filter (eq, neq, gt, in, like, etc.). PostgREST requires at least one filter, so empty filters are rejected as a safety guard.
Action
Insert Row
Inserts a new row into a Supabase table with the supplied field values. Respects table RLS policies based on the API key in use.
Action
Select Rows
Selects rows from a Supabase table with optional filters, order, and limit. Supports joined selects via the PostgREST embed syntax (e.g. *, author(name)).
Action
Update Rows
Updates rows in a Supabase table that match a filter. PostgREST requires at least one filter, so empty filters are rejected to prevent accidental table-wide updates.
Action
Upsert Row
Inserts a row, or updates it if a conflict occurs on the primary key or a unique constraint. The right tool for idempotent sync flows from another source-of-truth system.

Send list tables from your workflows.

Triggered by anything in the catalog. Free tier available. No credit card.

Try for freeRequest a demo