Appearance
Supabase
Manage databases, authentication, and storage with the Supabase Management API.
| Detail | Value |
|---|---|
| Category | Cloud & Infra |
| Base URL | https://api.supabase.com/v1 |
| Authentication | Bearer Token |
| Endpoints | 5 |
| Connector key | supabase |
Using Supabase in a workflow
- Go to Connections and click New Connection.
- Pick Supabase from the marketplace.
- Enter your credentials (see Authentication above for what's expected).
- In a workflow, drop an API Call node and select this connection.
- Pick the operation you need from the Operation dropdown — the full list is below.
Available endpoints
| Endpoint | Summary |
|---|---|
GET /projects | List all projects |
POST /projects | Create a new project |
GET /projects/{ref} | Get project details |
GET /projects/{ref}/functions | List edge functions |
POST /projects/{ref}/database/query | Execute a SQL query |
Each endpoint is documented in full below. Use the outline on the right to jump to one.
GET /projects
List all projects
| Detail | Value |
|---|---|
| Operation ID | cloud.listProjects |
| Method | GET |
| Path | /projects |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Supabase connection from the Connection dropdown.
- In the Operation dropdown, select
cloud.listProjects. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Supabase API reference.
POST /projects
Create a new project
| Detail | Value |
|---|---|
| Operation ID | cloud.createProject |
| Method | POST |
| Path | /projects |
Parameters
No parameters.
Request Body
| Field | Type |
|---|---|
name | string |
organization_id | string |
region | string |
db_pass | string |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Supabase connection from the Connection dropdown.
- In the Operation dropdown, select
cloud.createProject. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Supabase API reference.
GET /projects/{ref}
Get project details
| Detail | Value |
|---|---|
| Operation ID | cloud.getProject |
| Method | GET |
| Path | /projects/{ref} |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
ref | path | string | Yes |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Supabase connection from the Connection dropdown.
- In the Operation dropdown, select
cloud.getProject. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Supabase API reference.
GET /projects/{ref}/functions
List edge functions
| Detail | Value |
|---|---|
| Operation ID | cloud.listFunctions |
| Method | GET |
| Path | /projects/{ref}/functions |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
ref | path | string | Yes |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Supabase connection from the Connection dropdown.
- In the Operation dropdown, select
cloud.listFunctions. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Supabase API reference.
POST /projects/{ref}/database/query
Execute a SQL query
| Detail | Value |
|---|---|
| Operation ID | cloud.executeQuery |
| Method | POST |
| Path | /projects/{ref}/database/query |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
ref | path | string | Yes |
Request Body
| Field | Type |
|---|---|
query | string |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Supabase connection from the Connection dropdown.
- In the Operation dropdown, select
cloud.executeQuery. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Supabase API reference.