Supabase
Insert, query, mutate Supabase from any workflow
Supabase is the open-source-Firebase-alternative built on Postgres, and on Tiny Command its action surface treats every Supabase project as a typed database you can read and write from any workflow. Seven actions: Insert Row, Upsert Row, Update Rows, Delete Rows, List Rows (with PostgREST query syntax for filters and joins), List Tables for discovery, and Call Function for invoking Supabase Edge Functions. The integration uses a Supabase service_role key per project. The connection respects Row Level Security policies you've set up, if a policy blocks a workflow's write, the action returns a clear permissions error rather than silently dropping. List Rows accepts the full PostgREST query syntax (eq, gt, in, ilike, or, and, plus select for column projection and embedded joins), so a single action can fetch joined data without orchestrating multiple calls. Common pattern: a Stripe Customer Created webhook upserts the customer into a Supabase users table, a Supabase Edge Function (Call Function) runs an enrichment script, and the result fans into Slack and HubSpot.
Do anything Supabase can do, from a workflow.
Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.
| Action | What it does |
|---|---|
| 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. |
| 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. |
| 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. |
| 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)). |
| List Tables | Lists all tables in a Supabase database (from the public schema) with their column metadata. Used to dynamically populate table pickers and column dropdowns. |
| 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. |
| 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. |
Pre-built Supabase workflows.
Clone any recipe and customize it in one click. Every recipe is fully editable.
Three things worth knowing.
Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.
Connect Supabase once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.
Every Supabase field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.
Questions about the Supabase integration.
If we missed yours, ping support. We usually reply within an hour.
How do I connect Supabase to Tiny Command?
What Supabase triggers does Tiny Command support?
What Supabase actions can I run from a workflow?
Is the Supabase integration real-time?
Do I need to write code to use Supabase with Tiny Command?
How much does the Supabase integration cost?
More spreadsheets & databases apps people connect.
Same category as Supabase, ordered by how often teams pair them. Hover the carousel to pause.
Do more with Supabase.
Wire it to Slack, Notion, HubSpot, Stripe, or any of the other 438 apps in our catalog. Setup takes roughly two minutes. Free to try, no credit card.
