Developer Platform: MCP server availableDeveloper Platform: MCP server available, App SDK from Q4 2026

[ Developer tools ]

Supabase integration for your workflows.

Connect Supabase to Collabase once and use 22 actions and 1 trigger in your workflows. No code needed, hosted in Switzerland.

Sign-inCustom credentials
CategoryDeveloper tools
UpdatedOctober 2026
LicenceOpen source (MIT)
Back to the directory

Supabase in Collabase

Connect Supabase to Collabase once and use 22 actions and 1 trigger in your workflows. No code needed, hosted in Switzerland.

[ About the service ]

The open-source Firebase alternative

How to connect it

  1. Open the integrations in the workspace settings.
  2. Choose Supabase and connect your account.
  3. Add a trigger or an action to the workflow.
  • Go to your Supabase Dashboard
  • Select your project
  • Go to Settings → API
  • Copy the Project URL (format: https://your-project-ref.supabase.co)
  • Use Service Role Key (secret) for server-side operations
  • Has full access to bypass Row Level Security (RLS)

[ Developer tools ]

Related integrations

All integrations

Tools that often share a workflow.

Questions about Supabase

What can I automate with Supabase in Collabase?

Supabase brings 22 actions and 1 trigger, for example Upload File, Create Row, Update Row, Upsert Row and 18 more. You combine them in a workflow without code and mix them with every other integration.

How do I connect Supabase to Collabase?

You open the integrations in the workspace settings, choose Supabase and connect your account once, using custom credentials. After that all triggers and actions are available in the workflow.

Can Supabase start a workflow?

Yes. Supabase provides 1 trigger, for example New Row. The workflow runs as soon as the event happens.

Does the Supabase integration cost extra?

No. All integrations are included in every licence, in the Isolated Cloud and in Self-Hosted operation. There is no module price.

Test it against your own content. A proof of concept is ready within days.

We set up an instance with your content and you test it against real workflows. In a first conversation we clarify scope, operating model and timing.