CONNECT APP
Build with Supabase
Databases
- API key
MCP
Give your agent Supabase tools
Every Supabase action is exposed as an MCP tool on Pipedream's remote server. Point a client at it with your end user's ID and Connect resolves that user's Supabase account for each tool call — you store no tokens.
// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "supabase",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// e.g. run Batch Insert Rows:
const result = await mcp.callTool({
name: "supabase-batch-insert-rows",
arguments: {
table: "Table",
source: "Source of data",
},
})# access_token: mint a short-lived token with the Connect SDK — see the MCP guide
headers = {
"Authorization": f"Bearer {access_token}",
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", # any stable ID for this user in your system
"x-pd-app-slug": "supabase",
}
async with streamablehttp_client("https://remote.mcp.pipedream.net/v3", headers=headers) as (read, write, _):
async with ClientSession(read, write) as session:
await session.initialize()
tools = await session.list_tools()
# e.g. run Batch Insert Rows:
result = await session.call_tool("supabase-batch-insert-rows", {
"table": "Table",
"source": "Source of data",
})API PROXY
Call the Supabase API directly
For an endpoint with no pre-built tool, the Connect proxy forwards your request to the Supabase API with the connected user's credentials attached. You store no tokens and write no refresh logic.
const resp = await pd.proxy.get({
externalUserId: "{external_user_id}", // any stable ID for this user in your system
accountId: "apn_xxxxxxx",
url: "https://api.example.com/v1/me",
})
// Any allowed Supabase endpoint works here. Pipedream attaches the
// connected account's credentials to the outgoing request.# The path segment is the target URL, URL-safe base64 encoded:
# https://api.example.com/v1/me
curl "https://api.pipedream.com/v1/connect/{project_id}/proxy/aHR0cHM6Ly9hcGkuZXhhbXBsZS5jb20vdjEvbWU?external_user_id={external_user_id}&account_id=apn_xxxxxxx" \
-H "Authorization: Bearer {access_token}" \
-H "x-pd-environment: production"SDK
Run Supabase actions from your backend
Connect a user's Supabase account once, then run Batch Insert Rows on their behalf from your own code — TypeScript, Python, or plain HTTP.
import { PipedreamClient } from "@pipedream/sdk"
const pd = new PipedreamClient({
projectId: process.env.PIPEDREAM_PROJECT_ID!,
clientId: process.env.PIPEDREAM_CLIENT_ID!,
clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
projectEnvironment: "production",
})
const result = await pd.actions.run({
id: "supabase-batch-insert-rows",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
supabase: { authProvisionId: "apn_xxxxxxx" },
table: "Table",
source: "Source of data",
},
})from pipedream import Pipedream
pd = Pipedream(
client_id="{oauth_client_id}",
client_secret="{oauth_client_secret}",
project_id="{project_id}",
project_environment="production",
)
result = pd.actions.run(
id="supabase-batch-insert-rows",
external_user_id="{external_user_id}", # any stable ID for this user in your system
configured_props={
"supabase": {"authProvisionId": "apn_xxxxxxx"},
"table": "Table",
"source": "Source of data",
},
)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "supabase-batch-insert-rows",
"configured_props": {
"supabase": { "authProvisionId": "apn_xxxxxxx" },
"table": "Table",
"source": "Source of data"
}
}'TOOLS
Supabase actions
On-demand operations your product or agent can configure and run on behalf of a connected user.
-
Batch Insert Rows
actionInserts new rows into a database. See the documentationWritev0.0.8 -
Count Rows
actionCounts rows in a database table, with optional filtering conditions. See the docs hereRead-onlyv0.0.2 -
Delete Row
actionDeletes row(s) in a database. See the docs hereWritev0.1.6 -
Insert Row
actionInserts a new row into a database. See the docs hereWritev0.1.6 -
Remote Procedure Call
actionCall a Postgres function in a database. See the docs hereWritev0.1.6 -
Select Row
actionSelects row(s) in a database. See the docs hereRead-onlyv0.1.7 -
Update Row
actionUpdates row(s) in a database. See the docs hereWritev0.1.6 -
Upsert Row
actionUpdates a row in a database or inserts new row if not found. See the docs hereWritev0.1.6
EVENTS
Supabase triggers
Event sources your backend can deploy for users and receive through a webhook.
-
New Row Added
triggerEmit new event for every new row added in a table. See documentation herev0.0.7 -
New Webhook Event (Instant)
triggerEmit new event for everyinsert,update, ordeleteoperation in a table. This source requires user configuration using the Supabase website. More information in the README. Also see documentation hereInstantv0.0.8
MULTI-APP
Use Supabase with other popular apps
Most products don't stop at one integration. Pair Supabase with the other apps your users rely on, and ship use cases that span both.
- App slug
- supabase
- Authentication
- API key
- Categories
- Databases
- Actions
- 8
- Triggers
- 2
- API proxy
- Available