Integrations · Analytics & data

Supabase in the conversation.

A Postgres platform with auth and storage, and the application database for a lot of modern products. Connect it once and your copilot works with tables, rows, buckets and users without leaving the thread — and your workflows can act on it while the customer is still typing.

No credit card required · 7-day free trial

Supabase
Analytics & data
01 · COPILOT

Ask for it in plain language. It does the Supabase part.

Copilot rides inside the inbox. With Supabase connected it reads tables, rows, buckets and users and acts on them from the same panel as the conversation — no second tab, no copying an order number across.

  • Query a table for rows matching a filter
  • Insert or update a row
  • Read a user record
  • List tables in a schema

What a specific connection exposes is decided by Supabase, not by us: Settings → Apps lists the real tools your connection carries, each with its own switch.

02 · WORKFLOWS

Read Supabase from inside a workflow.

Supabase is a place a workflow looks things up rather than one that starts it. Trigger on a conversation, a schedule or another app's event, then use an AI Agent step to work in Supabase and hand the answer to the steps that follow — a message, a CRM update, an escalation.

If Supabase does publish events to your workspace, they appear in the trigger picker the moment the connection is made.

03 · THE AI AGENT STEP

One step that decides which Supabase tools to call.

A workflow's AI Agent step runs a bounded tool-calling loop over the apps you have connected and returns an object whose fields you declared. So "find the record, check the status, and give me status and owner" is one step rather than four — and the fields it returns are available to every step after it.

You declare the output

The rows you name become the variables downstream steps read, so a branch can test what Supabase said.

You cap the effort

A step budget and a model tier per node — the loop stops where you told it to.

Only what you switched on

The loop can call the Supabase tools you left enabled and nothing else.

What teams do with it

Two ways Supabase earns its connection.

01

Your own product data in the thread

Subscription state, usage limits, account flags — Copilot reads them straight from your application database while the customer waits.

02

Fix it without an engineer

A workflow with a narrow, reviewed write can flip the flag the customer is asking about, and log what it changed.

Setup

Connect Supabase in about a minute.

  1. 1

    Open Settings → Apps

    It is open to everyone in your organization, not just admins — which apps your copilot can reach is part of doing the job.

  2. 2

    Find Supabase in Browse

    The catalogue runs to hundreds of apps and is searchable. Connect Supabase from its card.

  3. 3

    Authorize with your own Supabase account

    You sign in on Supabase's own screen and approve the access. The connection carries that account's permissions — no API keys are pasted into Cloodot.

  4. 4

    Choose the tools it may call

    Open the connection and switch off anything you would rather it never touched. A tool you switch off is out of reach from the next question onward.

Supabase questions.

How do I connect Supabase to Cloodot?
Open Settings → Apps in Cloodot, switch to Browse, and search for Supabase. Connecting it opens Supabase's own sign-in and consent screen; when you come back, the app is listed as Connected and your copilot can use it. Nothing is installed and no keys are pasted into Cloodot.
What can Cloodot do in Supabase?
Work of this kind: query a table for rows matching a filter; insert or update a row; read a user record; list tables in a schema. The exact list depends on what your Supabase account is allowed to do — Settings → Apps shows every tool the connection actually exposes.
Can I limit which Supabase tools Cloodot may use?
Yes. Open the connection and every tool it exposes is a switch, searchable by name. A tool you switch off is out of reach from the next question onward, so a read-only Supabase connection is a matter of leaving the writes off.
Can a workflow use Supabase without a trigger from it?
Yes. Supabase is read from inside a workflow rather than starting one: a workflow triggered by a conversation, a schedule or another app's event uses an AI Agent step to work in Supabase and hand its answer to the steps that follow.
Who in my team can connect Supabase?
Anyone in the organization — Apps is not restricted to admins and owners, because which apps a copilot can reach is part of doing the job. The connection carries the permissions of the Supabase account that authorized it, so a analytics & data connection is only ever as broad as the account behind it.
See it on your own inbox

Try the whole thing, today.

Start free. Connect a channel, train an agent on your own content, and you'll have a working deployment in your inbox the same afternoon.