TL;DR
Database Change Alerts is a monitoring workflow that chains Slack + Supabase to automate a common task. Get a Slack alert whenever a critical Supabase table row is created, updated, or deleted — ideal for audit trails. Once configured, it runs through Claude Code, Cursor, Windsurf or any MCP-compatible AI agent.
Database Change Alerts
Get a Slack alert whenever a critical Supabase table row is created, updated, or deleted — ideal for audit trails.
How it works
Run with MCPizy
NewExecute this recipe in your browser — no local install, no Claude Code. Streams results live.
Why this combo?
Supabase Realtime fires on every row change with full before/after values; Slack delivers those changes to whoever needs to know instantly. For compliance-sensitive tables like billing, permissions, or user accounts, this combo creates a real-time audit trail that lives in your team chat.
Without this workflow
Critical row changed. Nobody noticed. Discovered in a quarterly audit. No record of who changed it or when.
With MCPizy
Every critical change posts to #db-alerts with old and new values. Complete audit trail in Slack history.
Business value
Concrete ROI — not marketing fluff.
Time saved
- De-risks insider threat: every admin action on billing/permissions is visible to the team in real-time
- Catches buggy deploys that silently corrupt data — team sees anomalous UPDATE patterns within minutes
Workflow steps
- 1Enable Supabase realtime for target table
- 2Subscribe to INSERT / UPDATE / DELETE events
- 3Format change summary (old → new)
- 4Post to #db-alerts Slack channel
- 5Throttle to prevent alert storms
Use cases
- Alert when user role or permissions change in the database
- Monitor billing table for unexpected changes or deletions
- Track configuration table changes that affect production behavior
- Compliance audit trail for GDPR-sensitive tables
Agent prompt (copy into Claude Code)
This prompt is the workflow. Paste into Claude Code, Cursor, or Windsurf.
You are a database-audit agent. Subscribes to Supabase Realtime for critical tables.
For each event on tables in audit-tables.yaml (billing, user_roles, api_keys, settings):
1. Format an audit message:
- :pencil2: UPDATE on ${table} (id=${id}) by ${actor}
- Changed: field1: old → new, field2: old → new (diff)
- Context: updated_at, updated_by, request_id
2. Call slack.send_message(channel="#db-alerts", blocks=[...]) with a structured block:
- header: action emoji + table
- section: actor + changed fields as key:value pairs
- actions: [View record in admin] [View user]
3. Throttle: if >10 events/min on same table, batch into one digest message
For DELETEs on billing/user_roles, also mention @oncall in the message.Trigger & credentials
How this workflow fires and what env vars you need.
Supabase Realtime: postgres_changes on audit tables (INSERT, UPDATE, DELETE)
One-command deploy
Install everything — MCPs, prompt, env template — in a single call.
$ mcpizy recipe install slack-supabase-db-alerts ✓ Installs all 2 MCP servers ✓ Writes prompt to ~/.mcpizy/prompts/slack-supabase-db-alerts.md ✓ Generates .env.example in current directory ✓ Ready to paste into Claude Code
Requires mcpizy CLI v1.1+ — install via npm i -g mcpizy.
Quick install (MCPs only)
$ mcpizy install slack && mcpizy install supabaseMore Monitoring recipes
Error Alerting Pipeline
Sentry new issues are de-duplicated, enriched with commit info, and routed to the right Slack channel based on project.
Database Monitoring Dashboard
Stream Postgres metrics — query latency, lock waits, vacuum stats — into Grafana for a live operations dashboard.
Alert Routing from Grafana
Grafana alerts are enriched with runbook links and routed to the correct Slack channel based on severity and team labels.
Analytics Dashboard
Connect ClickHouse to Grafana to build real-time analytics dashboards over billions of events with sub-second query times.
Frequently asked questions
What is this workflow?
Database Change Alerts is a monitoring automation that uses Slack + Supabase together via the Model Context Protocol. Get a Slack alert whenever a critical Supabase table row is created, updated, or deleted — ideal for audit trails.
How long does setup take?
Setup takes around 5 min setup, real-time audit trail. You install the required MCP servers with `mcpizy install slack && mcpizy install supabase`, connect your accounts, and the workflow is ready to run.
What does this workflow change in practice?
De-risks insider threat: every admin action on billing/permissions is visible to the team in real-time; Catches buggy deploys that silently corrupt data — team sees anomalous UPDATE patterns within minutes.
Which MCP servers do I need for this?
You need 2 MCP servers: Slack (mcpizy install slack), Supabase (mcpizy install supabase). All are installable in one command via the MCPizy CLI and configured in your `.claude.json` or `.cursor/mcp.json`.
Does this work with Claude Code, Cursor, and Windsurf?
Yes. The workflow runs with any MCP-compatible AI agent — Claude Code, Claude Desktop, Cursor, Windsurf, VS Code with Copilot, and custom agents built on the MCP SDK. The MCP servers are identical across clients; only the config file path (`.claude.json` vs `.cursor/mcp.json`) changes.
Start building this workflow
Install the required MCPs from the directory and automate this in 5 min setup.
$ mcpizy install slack && mcpizy install supabase
Free to install. Connect your accounts and this workflow runs itself.