u/gaganrt

I open-sourced a tiny n8n workflow that keeps all your free-tier Supabase projects from pausing (reads a Google Sheet, so you can add projects without touching the flow)
▲ 6 r/n8n_on_server+1 crossposts

I open-sourced a tiny n8n workflow that keeps all your free-tier Supabase projects from pausing (reads a Google Sheet, so you can add projects without touching the flow)

Hey folks,

Supabase free-tier projects pause after ~7 days of inactivity. I have a bunch of side projects and client demos running on free tier and I kept losing track of which ones were napping.

So I built SupaPing - a small, open-source n8n workflow:

  • Your Supabase projects live in a Google Sheet: name, project_url, anon_key, table, enabled
  • n8n runs on a schedule (default: every 6h, totally overkill — 24–48h is fine)
  • For each enabled row it does one GET /rest/v1/{table}?select=*&limit=1
  • Optional email alert on failure
  • Add/pause a project = edit one row in the sheet

What I like about the approach:

  • One workflow handles unlimited projects
  • Non-technical collaborators can manage the list
  • Uses only the anon key + a dedicated empty keepalive table with RLS — no sensitive data exposed
  • Works on self-hosted n8n or n8n Cloud

README has the SQL to create the keepalive table and RLS policy, plus import steps.

MIT-licensed. Ideas, issues, PRs all welcome — especially more notification channels (Slack/Discord/Telegram) and non-Google-Sheets sources.

👉 GitHub: https://github.com/buzz39/SupaPing-n8n

If you've solved this differently (cron + curl, GitHub Actions, edge function, etc.), curious to hear your approach.

u/gaganrt — 5 days ago