Uptime monitoring for Bubble and Webflow backends
Bubble and Webflow excel at UI; most serious SaaS still depends on an external API (Xano, Supabase, custom Node host). The marketing page can load from a CDN while workflows, auth, or billing connectors fail — so external monitoring must hit the backend health URL, not only the no-code front door.
StillOnline checks one public HTTPS URL from the internet, hosts a status page, and sends owner alerts through the StillOnline Telegram bot, Slack, or email.
Quick answer
Bubble and Webflow front ends often load while the backend API (Xano, Supabase, Railway) is down. Point StillOnline at a public health URL on that API returning 200 when customers can use the product — Free allows one URL and five-minute checks (pricing). Bubble’s page domain alone is rarely enough — no-code status page guide.
Platform limits and workarounds
| Stack | Limit | Monitoring approach |
|---|---|---|
| Bubble | Workflows fail while page loads | Backend GET /health via API connector host |
| Webflow | Static site ≠ app API | Monitor API host, not *.webflow.io only |
| Xano / Supabase | Rate limits on heavy health | Lightweight SELECT 1 or static OK response |
| Proxy backend | Single ingress for no-code | One StillOnline check on proxy /health |
If Bubble calls your API through a connector, the health URL should live on the API origin StillOnline can reach from the public internet.
Step 1 — Create one health URL
Many teams add a 10-line health workflow in Xano or Supabase:
GET /health→ 200 +{ "status": "ok" }- No secrets in response
- Under two seconds
Test externally:
curl -I https://your-api.example.com/health
Step 2 — Register in StillOnline
- Start free.
- New project.
- Paste health URL — GET, 200, five-minute interval.
- Share status page in onboarding or B2B docs — public status page guide.
Settings → Connect Telegram → StillOnline bot — Telegram guide.
Free: one owner channel. Pro / Ultimate: all three — pricing.
When the no-code front and API split
| Customer symptom | What failed | What to monitor |
|---|---|---|
| Page loads, login broken | Auth API | Backend health with auth dependency |
| Page loads, data empty | Database / workflow | Backend health with DB ping |
| Page does not load | CDN or Bubble/Webflow | Only if that is the product |
On Free, pick the single URL that best matches “customers cannot use the product.”
Related guides
- No-code SaaS status page
- Supabase backend monitoring
- Health check URL quickstart
- API-only SaaS checks
FAQ
Can StillOnline monitor only my Bubble app domain?
Only if that URL proves real availability. Most setups need the backend health URL because Bubble pages load while API workflows fail. Free = one URL — choose API health — API-only guide.
Should I monitor Webflow marketing site and API separately?
On Free, monitor the API health URL if the product depends on it. Marketing CDN uptime alone does not prove app functionality — no-code guide.
Does StillOnline require code on Bubble or Webflow?
StillOnline needs no plugin — only a public HTTPS URL returning 200. The health route usually lives on Xano, Supabase, or your proxy — health quickstart.
Can I get StillOnline Telegram alerts without writing a full app?
Yes. Link the official StillOnline bot in settings after the health URL is green — Telegram guide · Pricing.