Supabase

Supabase + Konnectify

Supabase Integration with Konnectify

Connect to the Supabase Data API and Storage API to automate database row operations, bucket management, file workflows, and polling-based storage triggers from Konnectify.

Database Rows Storage Buckets Storage Objects 3 Triggers 24 Actions

On this page

→ What is Supabase? → API & authentication → How to connect → Triggers (3) → Actions (24) → Popular automations → FAQ

What is Supabase?

Supabase is an open-source Firebase alternative that provides a hosted Postgres database, authentication, storage, edge functions, and APIs for building modern applications. Its Data API, powered by PostgREST, makes database tables available through secure REST endpoints, while Supabase Storage helps manage buckets and objects.

By integrating Supabase with Konnectify, teams can connect application data and storage events to downstream tools, automate CRUD operations, synchronize files, and build data-driven workflows without writing custom middleware.

New to Supabase?

Create a Supabase project to host your Postgres database and storage buckets.

Visit Supabase →

New to Konnectify?

Use Konnectify to automate workflows across Supabase and your business apps.

What you can automate

• Insert, search, update, upsert, and delete database rows

• Bulk insert or bulk delete rows by primary key values

• Create, find, list, empty, and delete storage buckets

• Upload, retrieve, update, move, copy, and delete storage objects

• Generate and use time-limited signed URLs for files

• Poll for newly added buckets, new objects, and updated objects

API & authentication

API Key authentication

The Supabase connector uses credential-based API key authentication. When creating a connection in Konnectify, provide your Project URL and Secret API Key. The Project URL may be the base project URL, such as https://<project_ref>.supabase.co, or the REST URL, such as https://<project_ref>.supabase.co/rest/v1.

Use a server-side Supabase secret or service role key that has permission to access the tables, buckets, and objects required by your workflow. Treat this key as sensitive and avoid using it in client-side applications.

Supported API capabilities

Supabase Data API operations for creating, finding, searching, updating, upserting, and deleting rows.
Bulk row operations using JSON array payloads or primary key value lists.
Supabase Storage bucket lifecycle operations, including create, list, find, empty, and delete.
Supabase Storage object operations, including upload, retrieve, update, copy, move, delete, and signed URL retrieval.
Polling triggers for newly created buckets, newly created objects, and recently updated objects.

Important: Available tables, storage permissions, rate limits, and API behavior may vary based on your Supabase project settings, Row Level Security policies, database grants, and plan limits. For production workflows, verify permissions with a test connection before activation.

For more details, review the official Supabase API documentation.

How to connect Supabase to Konnectify

Prerequisites

A Konnectify account with permission to create or edit workflows.
An active Supabase project.
Your Supabase Project URL.
A Supabase Secret API Key with access to the required database tables and storage buckets.
Any required table permissions, primary keys, bucket names, object paths, and Row Level Security policies configured in Supabase.

Add Supabase to a Workflow

Open Konnectify and create a new workflow or edit an existing workflow.
Choose Supabase as the trigger or action app.
Select the event that matches your automation requirement.

Authorize via API Key authentication

Click to add a new Supabase connection.
Enter your Supabase Project URL.
Paste your Secret API Key and save the connection.

Configure the Trigger or Action

For database row actions, select the table and provide the row fields, primary key, conflict key, search operator, or JSON payload as required.
For storage actions, provide the bucket name, object path, file content, prefix, metadata, or signed URL token as required.
For object triggers, choose the bucket and optionally add a prefix to monitor a specific folder-like path.

Tip: Confirm that your API key has the correct database and storage permissions. Row Level Security and bucket policies can prevent a workflow from reading or writing data even when the connection is valid.

Test the Workflow

Run a test to verify that Konnectify can reach your Supabase project.
Review returned records, objects, bucket details, or API responses.
Adjust field mappings and retry until the workflow behaves as expected.

Activate the Workflow

Turn on the workflow when testing is successful.
Monitor task history for API errors, validation failures, or permission issues.
Update the workflow whenever your Supabase schema, bucket policy, or object path convention changes.

Triggers 3

Supabase includes 3 polling triggers in Konnectify. Polling triggers check Supabase at scheduled intervals and pick up newly created buckets, newly created objects, or updated objects based on timestamp ordering.

Storage Buckets 1 trigger

New Added Bucket

Triggers on newly created buckets using created_at in descending order.

Storage Objects 2 triggers

New Added Object

Triggers on newly created objects by bucket and optional prefix using created_at in descending order.

Updated Object

Triggers on updated objects by bucket and optional prefix using updated_at in descending order.

Actions 24

Use Supabase actions in Konnectify to write to Postgres tables, manage storage buckets, and manipulate files and signed URLs.

Database Rows 8 actions

Insert Row

Creates a new row in the selected table using the values you provide.

Bulk Insert Rows

Creates multiple new rows in the selected table using a JSON array payload.

Find Row

Finds one row in the selected table by matching the selected primary key and value.

Update Row

Updates one row in the selected table by primary key with the fields you provide.

Delete Row

Deletes one row from the selected table by matching the selected primary key and value.

Bulk Delete Rows

Deletes multiple rows from the selected table by matching primary key values.

Search Rows

Searches rows in the selected table using key, operator, value, sorting, limit, and offset.

Upsert Row

Creates a new row or updates an existing row when the selected conflict key(s) match.

Storage Buckets 5 actions

Create Bucket

Creates a new Supabase storage bucket with optional access and MIME restrictions.

List Buckets

Lists all storage buckets in the current project.

Find Bucket

Finds and returns one storage bucket by bucket name.

Delete Bucket

Deletes a storage bucket by name.

Empty Bucket

Empties all objects from the selected storage bucket.

Storage Objects 11 actions

Upload File

Uploads a file to the selected storage bucket path using text or base64 content.

Update Object

Updates an existing file at the selected bucket path using PUT and replaces its content.

Delete Object

Deletes a file object from the selected bucket using its full object path.

Get Object

Retrieves an object from storage by bucket and object path.

Retrieve Authenticated Object

Retrieves an object from /object/authenticated using bucket and object path.

Generate Presigned Retrieve URL

Generates a time-limited signed URL to retrieve an object from the selected bucket path.

Retrieve Object Via Presigned URL

Retrieves an object via presigned URL route using bucket name, object path, and required token.

Move Object

Moves an object from source key to destination key, optionally into another bucket.

List Objects By Prefix

Lists objects in a bucket using prefix filtering with optional pagination, sorting, and search.

Copy Object

Copies an object from source key to destination key with optional metadata and metadata-copy behavior.

Delete Multiple Objects

Deletes multiple objects from a bucket using the required prefixes array.

Popular automations

Here are common workflow patterns you can build with the Supabase connector in Konnectify.

Sync new Supabase files to your database

When a new object is uploaded to a monitored bucket path, create a row in a metadata table for reporting, downstream processing, or audit logs.

New Added Object → Insert Row

Maintain a latest-file reference

Detect updated storage objects and upsert a row so your app always has the latest path, timestamp, or processing status.

Updated Object → Upsert Row

Automatically prepare newly created buckets

When a storage bucket is added, record it in a governance table and optionally upload a standard README or placeholder file.

New Added Bucket → Insert Row → Upload File

Generate secure file access links

Find a database row, locate the corresponding storage object, and generate a time-limited signed URL for secure retrieval.

New Added Object → Find Row → Generate Presigned Retrieve URL

FAQ

How does Supabase authentication work in Konnectify?

Supabase uses API key authentication in this connector. You enter your Project URL and Secret API Key when creating the connection. Use a key with sufficient permissions for the tables and storage buckets used in your workflow.

Which Supabase plans are supported?

The connector can work with Supabase projects that expose the required Data API and Storage API endpoints. Feature availability, limits, storage capacity, rate limits, and project quotas depend on your Supabase plan and project configuration.

Do Supabase triggers use polling or webhooks?

All Supabase triggers in this version are polling triggers. Konnectify checks Supabase on a schedule and reads the latest buckets or objects using timestamp fields such as created_at or updated_at.

How can I prevent duplicate database records?

Use the Upsert Row action when you want to create a row only if a conflict key does not already exist, or update the existing row when it does. You can also use Find Row before inserting if your workflow requires custom duplicate handling.

How are Supabase rate limits handled?

Supabase may enforce limits based on project resources, API usage, and your plan. If a workflow receives rate limit or transient server errors, review the workflow run history, reduce polling frequency or batch volume where possible, and verify Supabase project capacity.

Can I connect multiple Supabase projects?

Yes. Create a separate Supabase connection in Konnectify for each project URL and API key combination. This is useful for separating development, staging, and production projects.

How do bucket prefixes and object paths work?

Supabase Storage uses bucket names and object paths. A prefix works like a folder filter, such as invoices/2026/. Use prefixes in object triggers or list actions to monitor or retrieve only the objects under a specific path.

Ready to automate your Supabase workflows?

Connect Supabase to Konnectify and build automated workflows for data, storage, files, and signed URLs.

Get started free →