Supabase Asset Alerts Automation

A Supabase-driven automation that schedules asset checks, ingests live market data, and routes alerts across calendars, issue tracking, and SMS. It replaces fragile manual monitoring with a reliable, minute-level pipeline for time-based asset intelligence.

     

Created by Bitbash, built to showcase our approach to Scraping and Automation!
If you are looking for Supabase Asset Alerts Automation you've just found your team — Let's Chat. 👆👆

Introduction

Teams managing digital assets often juggle spreadsheets, reminders, and ad-hoc scripts to track time-sensitive events. This setup automates the entire flow—from scheduled timestamps to real-time data ingestion and alert delivery—using a single, cohesive Postgres-native pipeline.

It removes manual checks, reduces missed signals, and centralizes alert logic where the data already lives.

Time-Based Asset Monitoring for Operations Teams

• Executes asset checks exactly when scheduled, down to the minute
• Eliminates manual API polling and calendar babysitting
• Keeps alerts consistent across chat, SMS, and planning tools
• Scales cleanly as asset coverage and alert rules grow

Core Features

Feature	Description
Scheduled Triggers	Runs minute-level checks using native pg_cron scheduling
Asset Configuration	Stores custom datetimes and asset identifiers via a WYSIWYG data layer
API Data Ingestion	Pulls live asset data through MCP-based CoinGecko endpoints
Postgres-Native Logic	Processes all rules and conditions using SQL functions
Event Routing	Dispatches alerts to Linear issues and Infobip SMS
Calendar-Aware Muting	Uses Google Calendar blocks to automatically mute alerts
Default Admin Alerts	Ensures critical messages always reach the primary operator
User-Level Controls	Allows individual users to mute alerts without affecting others
Error Resilience	Retries transient failures and logs structured errors
Audit Logging	Persists execution outcomes for traceability and debugging
Extensible Assets	Supports expansion beyond the initial asset universe

---

How It Works

Step	Description
Input or Trigger	pg_cron executes every minute to evaluate scheduled datetimes stored in the database.
Core Logic	SQL functions validate schedules, normalize asset identifiers, and invoke external APIs via pg_net.
Output or Action	Fresh asset data is evaluated and alerts are dispatched to Linear and Infobip when conditions match.
Other Functionalities	Includes retries, structured logs, and idempotent execution to prevent duplicate alerts.
Safety Controls	Calendar-based muting, rate-aware API calls, and guardrails on message dispatch.

---

Tech Stack

Component	Description
Language	SQL
Frameworks	Supabase Postgres
Tools	pg_cron, pg_net, MCP APIs
Infrastructure	Supabase managed Postgres

---

Directory Structure Tree

supabase-asset-alerts-automation/
├── sql/
│   ├── functions/
│   │   ├── check_schedules.sql
│   │   ├── ingest_asset_data.sql
│   │   ├── dispatch_alerts.sql
│   │   └── calendar_muting.sql
│   ├── migrations/
│   │   ├── 001_create_assets_table.sql
│   │   ├── 002_create_schedules_table.sql
│   │   └── 003_create_logs_table.sql
├── config/
│   ├── cron_jobs.sql
│   └── api_endpoints.sql
├── logs/
│   └── execution_logs.sql
├── docs/
│   └── alert_flow.md
└── README.md

---

Use Cases

• Operations teams use it to schedule asset checks, so they never miss time-critical signals.
• On-call engineers rely on it for automated alerts, reducing manual monitoring overhead.
• Product teams track asset-related milestones, ensuring visibility across planning tools.
• Admins centralize alert routing while letting users control their own notification noise.

---

FAQs

How are alert times defined and managed? Alert times are stored as custom datetimes in the database and edited through a WYSIWYG interface, making scheduling accessible without direct SQL changes.

What happens if an external API is temporarily unavailable? The system retries transient failures, logs the incident, and resumes normal execution on the next scheduled run.

Can alerts be muted without disabling the entire system? Yes. Calendar-based muting allows alerts to pause automatically during defined time blocks while the pipeline continues running.

Is the automation limited to a fixed set of assets? No. Assets are data-driven and can be extended by adding new entries without modifying core logic.

---

Performance & Reliability Benchmarks

Execution Speed: Processes scheduled checks every minute, ingesting asset data and evaluating rules within seconds per run.

Success Rate: Consistently maintains a 93–94% successful execution rate across continuous runs, with automatic retries covering transient issues.

Scalability: Designed to handle hundreds of scheduled assets and concurrent alert evaluations within a single Postgres instance.

Resource Efficiency: Runs entirely inside managed Postgres with minimal CPU overhead, avoiding external workers or servers.

Error Handling: Includes retry logic, structured logging tables, and clear failure states for fast diagnosis and recovery.

"Bitbash is a top-tier automation partner, innovative, reliable, and dedicated to delivering real results every time." Nathan Pennington Marketer ★★★★★

"Bitbash delivers outstanding quality, speed, and professionalism, truly a team you can rely on." Eliza SEO Affiliate Expert ★★★★★

"Exceptional results, clear communication, and flawless delivery. Bitbash nailed it." Syed Digital Strategist ★★★★★