How do I connect Slack and Supabase to Operator?

You authorize Slack and Supabase once each from your Operator dashboard. Operator holds both connections and refreshes the access tokens for you, so your agent keeps working across them without you signing in again.

What can my agent do across Slack and Supabase?

You describe the outcome in plain language and your agent works between the two, reading from one and acting in the other. It picks the right Slack and Supabase actions on its own, so you do not map fields or pick triggers.

Can my agent keep Slack and Supabase in sync?

Yes. It can watch Slack and act in Supabase, or keep both in step, reading from one and running the matching update in the other. This runs on demand when you ask or on a schedule you set.

Do I need to build a workflow or write code?

No. There is no workflow to build, no fields to map, and no API keys to paste. Operator manages both connections, and you give the agent instructions in plain language.

← All integrations

Connect Slack to Supabase

Try for free

Automate Slack and Supabase with AI

Database events that matter to the team should surface in Slack without someone watching a dashboard. Operator.io points your OpenClaw agent at Supabase and Slack so a new row, failed job, or threshold breach opens a thread with the record fields you define, and engineers can ask for a one off query in chat and get the result inline. Tell it to alert when signups spike and it runs the check on your schedule and posts when the count crosses the line you set.

It reaches both apps directly or through connectors like Composio MCP and Pipedream MCP, which handle the sign in and token refresh, so there is no Zap to build and no API keys to paste.

What your agent can do with Slack and Supabase

What your agent does in Slack

Add call participants
Registers new participants added to a Slack call.
Add emoji
Adds a custom emoji to a Slack workspace given a unique name and an image URL; subject to workspace emoji limits.
Add an emoji alias
Adds an alias for an existing custom emoji in a Slack Enterprise Grid organization.
Add Enterprise user to workspace
Adds an Enterprise user to a workspace. Use when you need to assign an existing Enterprise Grid user to a specific workspace with optional guest restrictions.
Add reaction to message
Adds a specified emoji reaction to an existing message in a Slack channel, identified by its timestamp; does not remove or retrieve reactions.
Add a remote file
Adds a reference to an external file (e.g., Google Drive, Dropbox) to Slack for discovery and sharing, requiring a unique `external_id` and an `external_url` accessible by Slack.

All 145 Slack actions →

What your agent does in Supabase

Create project api key
Creates a 'publishable' or 'secret' API key for an existing Supabase project, optionally with a description; 'secret' keys can have customized JWT templates.
Delete an API key from the project
Permanently deletes a specific API key (identified by `id`) from a Supabase project (identified by `ref`), revoking its access.
Delete third party auth config
Removes a third-party authentication provider (e.g., Google, GitHub) from a Supabase project's configuration; this immediately prevents users from logging in via that method.
Get a third-party integration
Retrieves the detailed configuration for a specific third-party authentication (TPA) provider, identified by `tpa_id`, within an existing Supabase project specified by `ref`.
List third-party auth integrations for project
Lists all configured third-party authentication provider integrations for an existing Supabase project (using its `ref`), suitable for read-only auditing or verifying current authentication settings.
Update an API key for the project
Updates an existing Supabase project API key's `description` and/or `secret_jwt_template` (which defines its `role`); does not regenerate the key string.

All 116 Supabase actions →

How it works

Tell the agent what you want to happen between Slack and Supabase, for example to watch one and act in the other, or to keep the two in step. It reads what it needs from Slack, works out what to do, and runs the matching action in Supabase without you mapping a single field.

You can have it run once, on a schedule, or whenever something changes. Ask it for a status any time and it reads the latest from both apps back to you in the same chat.

Common questions about Slack and Supabase

How do I connect Slack and Supabase to Operator?: You authorize Slack and Supabase once each from your Operator dashboard. Operator holds both connections and refreshes the access tokens for you, so your agent keeps working across them without you signing in again.
What can my agent do across Slack and Supabase?: You describe the outcome in plain language and your agent works between the two, reading from one and acting in the other. It picks the right Slack and Supabase actions on its own, so you do not map fields or pick triggers.
Can my agent keep Slack and Supabase in sync?: Yes. It can watch Slack and act in Supabase, or keep both in step, reading from one and running the matching update in the other. This runs on demand when you ask or on a schedule you set.
Do I need to build a workflow or write code?: No. There is no workflow to build, no fields to map, and no API keys to paste. Operator manages both connections, and you give the agent instructions in plain language.

Slack and Supabase integrations

Slack

Supabase

More pairings

Active campaign + Slack Affinity + Slack Airtable + Slack Airtable + Supabase Algolia + Supabase Amplitude + Slack Apollo + Slack Asana + Slack

Put your agent on Slack and Supabase

Sign in, connect both apps, and hand your agent the work. The same setup reaches every app in the catalog. Your first week is free.

Try for free