Skip to content
ClickRuntime

Automate Supabase

Use your Supabase tables as the place where automations read and write. Feeds and prices get collected into tables, webhook events are logged, new rows trigger a Slack ping, sparse records get filled in, and a morning email counts yesterday's signups and orders. Explain the job to your AI assistant, look over the steps it proposes, and after that it runs without you.

Add to ChatGPTAdd to Claude
Works inChatGPTClaudeClaude CodeCursorCodexVS CodeGemini CLIZedopencodeAny MCP client

Try asking

Create a ClickRuntime automation: every hour, fetch new posts from these three RSS feeds and insert them into my Supabase articles table, skipping any URL that's already there.

Paste it into your assistant. It tells you what it will send or change before it runs live.

Ideas

What you can automate in Supabase

Tables that fill themselves from feeds and webhooks, alerts when rows arrive, AI-filled details on sparse records, and daily numbers or weekly backups straight from your database. These are ready-made starting points. Anything else you can describe works too.
Hourly or daily

Fill a Supabase table from feeds on a schedule

New articles, prices or other public items land in your table every hour, with duplicates skipped.

See how it works
The moment it happens

Store your app's events in Supabase

Every event your app sends to a secure link is saved as a row, and each week you get counts by event type.

See how it works
Every 15 minutesAI

Fill in missing company details automatically

Company rows without an industry get one added, along with a short summary and social links taken from their website.

See how it works
Every 5 minutesAI

Log outages in Supabase and get a diagnosis

When a site you watch fails, an incident row is written and you get an email with a short explanation of the likely cause.

See how it works
Every 3 days

Stop a free Supabase project from pausing

Your free project stays active, and you hear about it if the keep-alive query fails.

See how it works
Weekly

Get a weekly list of users who went quiet

A Monday email listing users who haven't been seen in a month, each with a drafted win-back message you can send yourself.

See how it works
On a schedule

Get yesterday's signups and orders by email

Each morning you see how many rows were added to your key tables the day before, compared with the day prior.

See how it works
Every 5 minutes

Get a Slack message for every new signup

New rows in your table show up in Slack within minutes, grouped together when many arrive at once.

See how it works
Weekly

Email yourself a weekly CSV of a table

Every Sunday a CSV copy of one small table arrives in your inbox.

See how it works
DailyAI

Get a daily summary of new feedback

One evening email grouping the day's feedback rows into themes, so you don't read each entry.

See how it works Your own logic

Any other automation you can describe in words

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

See how to build your own

Build your own

Build any Supabase automation you can describe

The ideas above are ready-made starting points, not a fixed list. Describe what Supabase should do 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

Every night, count new rows in my Supabase signups table and email me if signups dropped more than 40% from the previous day.

Every week, export my Supabase orders table to a CSV and save it in a dated Google Drive folder.

Every 15 minutes, check my Supabase feedback table for new rows, have AI classify each as bug, request or praise, email bugs to me in Gmail, and send requests to my Telegram.

Works with

Supabase with the apps you already use

Supabase is often the memory behind a bot or a lead list, while the conversation happens in chat, email or a spreadsheet. Pairing them lets one side store and the other side act.

Supabase works with hundreds of other apps

Name any of them when you ask your assistant, and your automation connects them. Over 248 apps are ready to go, and anything with an API works too.

  • Firebase
  • Neon
  • MongoDB
  • Vercel
  • Netlify
  • GitHub
  • Stripe
  • OpenAI
  • Airtable
  • Notion
  • Postmark
  • Resend
  • Discord
  • PostHog
  • Sentry
  • Typeform
  • Shopify
  • Clerk

Beyond chat

Have Supabase work when you're not in the chat

Connecting Supabase to ChatGPT or Claude lets you ask about it while you chat. ClickRuntime handles the part that should happen on its own: checks on a schedule and actions on each new event, set up from the same chat and running after you close it.

Setup

Connect Supabase

Supabase is connected with a secret key from your own project plus the project URL. Management tasks use a personal access token you generate in your account.

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).

Good to know

Supabase limits that affect automations

  • The secret key bypasses Row Level Security, so it can read and change every table. Point automations at dedicated tables where you can.
  • Free-plan projects are paused after 7 days without activity; a small scheduled query keeps them awake.
  • The older anon and service_role JWT keys are being retired, so use the newer sb_secret_ keys for new connections.
  • Weekly CSV backups go by email as plain text, which suits small tables, not large ones.

FAQ

Questions about automating Supabase

What can ClickRuntime access in my Supabase project?
With a secret key it can read, insert and update rows in any table through the REST API, because that key ignores Row Level Security. Keep it scoped in practice by telling your assistant which tables a job may touch.
Can it react the instant a row is inserted?
Yes, if you set up a Supabase Database Webhook on insert that calls a ClickRuntime link. Otherwise the automation checks for new rows on a schedule, for example every 5 minutes, and batches bulk inserts into one message.
Will it email my users directly?
No. The inactive-users job sends the list and a suggested win-back draft to you, the owner. Sending is up to you.
Do the Supabase automations use AI?
Some do: enriching rows, diagnosing errors and summarising feedback. That AI is part of every ClickRuntime plan, so you don't add your own key. Collecting data, backups and row alerts run without it.
Can it stop my free project from pausing?
Yes. A lightweight select every few days counts as activity, and you get an email if the query ever fails.
Is this a Supabase connector for ChatGPT or Claude?
Not for chatting with Supabase data. A chat connector lets your assistant read and change Supabase while you're in the conversation. ClickRuntime is for the work that should happen without you: you set up an automation from the chat once, and it keeps running on a schedule or on each Supabase event.

Related pages

Keep exploring

Tell your assistant what Supabase should do

Free plan. No credit card.

Add to ChatGPTAdd to Claude