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.
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
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.
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.
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.
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.
The rows you name become the variables downstream steps read, so a branch can test what Supabase said.
A step budget and a model tier per node — the loop stops where you told it to.
The loop can call the Supabase tools you left enabled and nothing else.
Subscription state, usage limits, account flags — Copilot reads them straight from your application database while the customer waits.
A workflow with a narrow, reviewed write can flip the flag the customer is asking about, and log what it changed.
It is open to everyone in your organization, not just admins — which apps your copilot can reach is part of doing the job.
The catalogue runs to hundreds of apps and is searchable. Connect Supabase from its card.
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.
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.
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.