Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Supabase

The open-source Firebase alternative

CategoryDeveloper Tools
Authenticationcustom
Version0.2.0
Published scopes0 published scopes
Last updatedSeptember 24, 2026

Overview

Connect Supabase with Flows360

The open-source Firebase alternative

Use the Supabase connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 9 actions and 1 trigger.

Available actions

  • Upload File
  • Create Row
  • Update Row
  • Upsert Row
  • Delete Rows
  • Search Rows
  • List Tables
  • Get Table Schema
  • Plus 1 additional declared action.

Available triggers

  • New Row

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Supabase
  • Package: @activepieces/piece-supabase@0.2.0
  • Exact artifact digest: sha256:2abb610f02093c92f757fa11404693c6753c60dd1ce327144715ae070cca0cea
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

CUSTOM AUTH. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Upload File (upload-file), Upload a file to Supabase Storage Classification: read.
  • Create Row (create_row), Create a new row in a table Classification: read.
  • Update Row (update_row), Update rows in a table based on filter criteria Classification: read.
  • Upsert Row (upsert_row), Insert or update a row in a table Classification: read.
  • Delete Rows (delete_rows), Remove rows matching filter criteria from a table Classification: read.
  • Search Rows (search_rows), Search for rows in a table with filters and pagination Classification: read.
  • List Tables (list_tables), Returns a list of all public tables and views in the database Classification: read.
  • Get Table Schema (get_table_schema), Returns the column definitions for a specific table Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • New Row, webhook.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objects10
Supported actionsNot published
TriggersNone published

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • Project URL Required
  • API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Upload File Yes No Upload a file to Supabase Storage
Create Row Yes No Create a new row in a table
Update Row Yes No Update rows in a table based on filter criteria
Upsert Row Yes No Insert or update a row in a table
Delete Rows Yes No Remove rows matching filter criteria from a table
Search Rows Yes No Search for rows in a table with filters and pagination
List Tables Yes No Returns a list of all public tables and views in the database
Get Table Schema Yes No Returns the column definitions for a specific table
Custom API Call Yes No Make a custom API call to a specific endpoint
New Row Yes No webhook trigger declared by the pinned package.

Setup

Setup

  1. Add the Supabase connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • Project URL (url), required.
  • API Key (apiKey), required; stored as a sensitive connection value.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-supabase@0.2.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 9 actions and 1 trigger declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Supabase connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-supabase@0.2.0 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com