ActionSupabaseUpdated May 2026
How do I call a Postgres function in Supabase?
Short answer: Drop the "Supabase → Call Function (RPC)" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Inputs
The fields this action accepts.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Function Name function_name | string | Required | Function Name. Example: get_user_stats |
Parameters (JSON) params | string | Optional | JSON object of function arguments |
Sample request
{"function_name": "e.g. get_user_stats","params": "{\"user_id\": 123}"}
Returns
{"total_orders": 42,"total_revenue": 1234.56}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for Call Function (RPC).
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Call Function (RPC).
What does the Call Function (RPC) action do in Supabase?
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.
What inputs does Call Function (RPC) require?
Required: Function Name. Every input accepts a static value or a variable from any upstream node in your workflow.
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 Call Function (RPC) support batch operations?
Yes. Run Call Function (RPC) 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
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.
ActionInsert 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.
ActionSelect 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)).
ActionList 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.
ActionUpdate 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.
ActionUpsert 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 call function (rpc) from your workflows.
Triggered by anything in the catalog. Free tier available. No credit card.
