Supabase integration

Databases · 8 actions · API key auth

Open-source Firebase alternative providing a Postgres database, authentication, instant APIs, and realtime subscriptions

Put Supabase to work View Supabase integration docs

Overview

The ModuleX Supabase integration lets a ModuleX agent operate Supabase on your behalf — running update and remove actions across select rows, rows and batch insert rows — directly from a plain-English request, using your organization's own Supabase credentials. No pre-built workflow is required: the agent picks the right Supabase action for the task.

Supabase is a databases platform. ModuleX adds the agent layer: ask for an outcome and it selects and runs the right Supabase action — or, when you want a repeatable process, the composer assembles a Supabase workflow for you, streaming the nodes onto the canvas as it builds.

Ask the assistant

Drive Supabase in plain English

Type what you want. A ModuleX agent picks the right Supabase action — or chains several — and runs it. No workflow to build.

Update row(s) in a Supabase database table matching a column value
resolves toupdate_row
Select row(s) from a Supabase database table with optional filtering and ordering
resolves toselect_row
Insert a new row into a Supabase database table
resolves toinsert_row

Use cases

What you can automate with Supabase

Update a row the moment something changesupdate_row
Select row(s) from a Supabase database table with optional filtering and orderingselect_row
Insert a new row into a Supabase database tableinsert_row
Insert a row or update it if it already exists in a Supabase database tableupsert_row
Delete row(s) from a Supabase database table matching a column valuedelete_row
Insert multiple rows into a Supabase database table at oncebatch_insert_rows

At a glance

Supabase integration at a glance

VendorSupabase

CategoryDatabases

Actions available8

AuthenticationAPI key

Uses your own credentialsYes

Works with the assistantYes

Works in the composerYes

Multi-step / tool-chainingYes

Technical referenceView docs

Integration version1.0.0

Last updatedJun 2026

Reference

All 8 Supabase actions

Select Rows1

select_row

Select row(s) from a Supabase database table with optional filtering and ordering

Rows5

insert_row

Insert a new row into a Supabase database table

update_row

Update row(s) in a Supabase database table matching a column value

upsert_row

Insert a row or update it if it already exists in a Supabase database table

delete_row

Delete row(s) from a Supabase database table matching a column value

count_rows

Count rows in a Supabase database table with optional filtering

Batch Insert Rows1

batch_insert_rows

Insert multiple rows into a Supabase database table at once

Remote Procedure Calls1

remote_procedure_call

Call a Postgres function (RPC) in a Supabase database

See full parameters and response schemas in the Supabase integration docs

Two ways

Two ways to use Supabase in ModuleX

Ask the assistantType what you want done and a ModuleX agent picks the right Supabase action and runs it — no workflow to build.

Compose a workflowNeed it to happen every time? Describe the process and the composer wires Supabase into a repeatable workflow you can run on a schedule, from chat, or as an API.

Security

Connecting Supabase

API keySupabase uses API-key authentication. You provide your own Supabase secret key; ModuleX encrypts it and scopes it to your organization, so your whole team can use Supabase without re-authenticating.

Step-by-step setup in the Supabase docs

Pairs well with Supabase

Agents often chain Supabase with these — connect them once and the agent can use all of them in a single task.

PostgreSQL10 actions

MySQL9 actions

Snowflake9 actions

Microsoft SQL Server4 actions

FAQ

Supabase + ModuleX FAQ

A ModuleX agent can run any of Supabase's 8 actions — across select rows, rows, batch insert rows and remote procedure calls — from a plain-English request, using your organization's own Supabase credentials.

No. The agent selects the right Supabase action from your prompt. A workflow is only needed when you want a repeatable process — and the composer builds that for you from a description.

Via your own Supabase API key, stored encrypted and scoped to your organization.

8, spanning select rows, rows, batch insert rows and remote procedure calls.

Supabase runs on your own credentials, so any Supabase usage is billed by Supabase directly. ModuleX meters the agent run — and if you connect your own model keys, there's no ModuleX markup on model usage.

Put Supabase to work in ModuleX.

Connect Supabase once with your own credentials and let your agent run all 8 actions on demand.

Put Supabase to work View technical docs

Last updated: Jun 2026Browse all 175 integrations →