Runner.Run SQL queries against the Supabase database.
Supabase Runner Workflows
Query databases, manage tables, and keep backend data accessible in the workflow.
Runner uses Supabase through the Composio toolkit for database queries, table management, and API operations.
SupabaseDatabases
+New Session
Sessions
Connected appsSupabase
Slack
GitHub
SupabaseSlackGitHub+
Connect a new appWhat would you like to do?
What Runner actually does with Supabase
This page is tied to the real connector definition inside Runner. The highlights below describe the kinds of actions, safeguards, and workflow patterns the app page represents, not a generic integration directory blurb.
Manage tables and rows for application data.
Pull backend data into reporting and decision workflows.
Backend surface
Composio toolkit powers this connector inside Runner. Backed by the `supabase` toolkit in Runner's backend catalog with database and API operations.
Operational notes
- Supabase provides Postgres-compatible SQL queries with Row Level Security.
Popular workflows with Supabase
Real workflow pages where Supabase is part of the connected stack. Each workflow shows the trigger, connectors, and outcome.
Triggers and actions
What Runner can do with Supabase. These are grounded in the real backend connector definitions, not generic marketing filler.
Query the database
“Run a query to show active users by plan tier from the last 30 days.”
Application data becomes part of the operating context for product and business decisions.
Check table state
“Show me the schema and recent rows from the customer_events table.”
Backend state stays visible alongside the rest of the workflow.
Manage rows and records
“Insert a new row into the feedback table with the sentiment score and source channel.”
Application data updates happen as part of the workflow instead of requiring a separate admin panel.
Use Supabase inside a real workflow
Download Runner to connect Supabase to the rest of your workflow instead of treating it like another isolated tab.