Insert Row: Supabase action

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
Table Name table	string	Required	Table Name. Example: users
Row Data (JSON) data	string	Required	JSON object with column names as keys

Sample request

{
  "table": "e.g. users",
  "data": "{\"name\": \"John Doe\", \"email\": \"john@example.com\"}"
}

Returns

[
  {
    "id": 1,
    "name": "John Doe",
    "email": "john@example.com",
    "created_at": "2025-01-15T12:00:00Z"
  }
]

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

FAQ

Questions about Insert Row.

What does the Insert Row action do in Supabase?

Inserts a new row into a Supabase table with the supplied field values. Respects table RLS policies based on the API key in use.

What inputs does Insert Row require?

Required: Table Name, Row Data (JSON). 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 Insert Row support batch operations?

Yes. Run Insert Row 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