Skip to content
ClickRuntime

Connect Slack to Supabase

When your product data lives in Supabase, the interesting changes, like a hot lead, an inactive member or a duplicate invoice, are invisible until someone runs a query. Posting them to Slack puts them in front of the team as they happen.
Add to ChatGPTAdd to Claude
Works inChatGPTClaudeClaude CodeCursorCodexVS CodeGemini CLIZedopencodeAny MCP client

Ideas

What you can do with Slack and Supabase

Lead alerts, risk scans, review escalations and duplicate checks from Supabase to Slack. These are ready-made starting points. Anything else you can describe works too.
The moment it happensAI

Score every new lead and post the hot ones to Slack

Each new lead gets an AI score and is saved to your Supabase leads table, and hot leads are posted to your sales channel straight away.

See how it works
On a schedule

Post members who've stopped checking in to Slack each morning

Every morning, Slack lists the members in your Supabase table who haven't checked in for 14 days, highlighting the ones new to the list since yesterday.

See how it works
Every 3 hoursAI

Store new reviews in Supabase and send angry ones to Slack

Every 3 hours, new reviews are saved once in Supabase with a sentiment label, and negative ones go straight to Slack.

See how it works
On a scheduleAI

Post a monthly summary of your Supabase figures to Slack

On the 1st of each month, Slack gets a short written summary of last month's figures from your Supabase table, with the changes from the month before.

See how it works
The moment it happens

Warn Slack about duplicate invoices before they're paid

When a new invoice arrives, it's checked against your Supabase records, saved with a status, and any likely duplicate is flagged in Slack.

See how it works Your own logic

Any other automation you can describe in words

Your own rules, schedule and AI steps with Slack and Supabase, plus any other app. Describe it and your assistant builds it.

See how to build your own

Build your own

Build any Slack and Supabase automation you can describe

The ideas above are ready-made starting points, not a fixed list. Describe what should happen between Slack and Supabase in your own words, with your conditions, other apps or an AI step, and your assistant writes it, tests it and runs it on ClickRuntime.

  • Your own rules

    Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.

  • Any number of apps

    One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.

  • AI where it helps

    Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.

  • On a schedule or on each event

    Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.

For example, ask your assistant

Only post signups from company email domains, and send a daily count for everything else.

Each Friday, post the week's signups, active users and churned users compared with last week.

Use cases

Why people connect Slack and Supabase

How the two apps work together

  • A Supabase database webhook sends new rows to your trigger link, or the script checks every few minutes.
  • The script posts details to the Slack channel you choose.
  • Commands in a Slack channel can be read on the next check and query or update Supabase.

  • Founders watching signups

    New users in Supabase are posted to #growth. The team sees growth live.

  • Engineers watching errors

    Rows in an errors table are posted to #eng. Problems are seen fast.

  • Support teams looking up users

    A Slack message with an email returns the user's row from Supabase. Support answers faster.

  • Ops teams getting daily metrics

    A morning post shows counts from key tables. Everyone sees the numbers.

More apps

Slack, Supabase and other apps in one automation

An automation isn't limited to two apps. Add the next step in another app and it runs as part of the same automation.

Signup log

Post new Supabase signups to #growth and add them to my Google Sheet.

Paid conversions

When a Supabase user becomes a paying Stripe customer, post it to #wins.

Error escalation

If more than 50 rows land in my errors table within 10 minutes, post to #eng and open a PagerDuty incident.

Setup

Connect Slack and Supabase once

Every idea on this page uses the same two connections, so you set them up once. If one is missing, your assistant tells you and links to the right place.

Slack

Team chat

  1. At api.slack.com/apps, create a new app from scratch in your workspace.
  2. Under OAuth & Permissions, add the bot scopes the automation needs, such as chat:write, channels:read and channels:history.
  3. In the ClickRuntime dashboard, open Connections, choose Slack and enter your app's details, then install it to your workspace.
  4. In each channel the automation should use, type /invite @your-app-name.

Supabase

Developer / Database & backend

  1. In your Supabase project, open Settings, then API Keys, and copy or create a secret key (it starts with sb_secret_).
  2. Note your project URL, which looks like https://<project-ref>.supabase.co.
  3. If an automation needs the Management API, go to Account, then Access Tokens, and generate a new token.
  4. In the ClickRuntime dashboard, open Connections & secrets and save the project URL and secret key (and the access token, if you made one).

FAQ

Questions about connecting Slack and Supabase

Does it need database admin access?
No. It uses your project's REST API with a key you choose. Read access is enough for scans and reports.
How often does it check?
As often as you like, down to every 5 minutes, or the moment a record arrives through the trigger link.
Will Slack get noisy?
Alerts post only new findings, and daily scans compare with yesterday so the same records aren't listed again and again.
Which tables can it read?
Any table or view your key can access. Tell your AI assistant the table and the rule to check.
Does it need the service role key?
Only if it must read tables protected by row level security. A read-only role is safer.
Can it post to several channels?
Yes. Route by table or by a column value.
Is it real time?
With a Supabase database webhook it is immediate. Otherwise checks run every few minutes.

Related pages

Keep exploring

Tell your assistant what Slack and Supabase should do together

Free plan. No credit card.

Add to ChatGPTAdd to Claude