Use case
Scheduled Firebase work without the Blaze plan.
Firebase Scheduled Functions require Blaze because they deploy a Cloud Scheduler-backed function. Crontap can keep Firebase data, Auth, or Hosting on Spark only when the scheduled HTTP runtime is hosted elsewhere and calls the Firebase services it is allowed to use.
Free plan · no credit card required
The problem
Why this is painful without the right tool
- Scheduled Functions require Blaze billing because Cloud Scheduler is under the hood and Cloud Scheduler is paid.
- Spark plan users cannot use Scheduled Functions at all, even for a single daily trigger.
- Cloud Scheduler's 1-minute minimum is the same as Crontap's; the difference is execution model, routing, monitoring, and cross-platform scope.
- Multi-project Firebase setups end up with one Scheduler console per project and no central view.
The fix
How Crontap solves it
Crontap calls your own HTTPS endpoint, such as a Render service, Vercel function, Cloudflare Worker, or backend on your own server. A Firebase Cloud Function still requires a billing-enabled project. The external endpoint talks to Firebase or FCM directly. Human alerts and machine webhook Integrations remain separate.
0 * * * *One concrete pattern from the dataset, archetyped: a Firebase customer running an hourly FCM push from a .NET backend that owns the Firebase Admin SDK credentials. The schedule fires POST /PushFirebase/clickez on the hour; the backend reads a queue and pushes through FCM. Spark plan stays usable because Firebase itself is not running the scheduler.
For multi-project Firebase setups, one Crontap schedule per project per cadence gives you a clean dashboard. The credentials live server-side; Crontap only knows the bearer header your backend expects.
FAQ
Common questions
- Will this still trigger FCM pushes?
- Yes. FCM is the messaging side; the scheduler is the trigger side. Crontap fires your backend on a cron; your backend uses the Firebase Admin SDK or the legacy FCM HTTP API to send pushes. Same end-to-end behavior, different scheduler.
- What's the shortest interval Crontap supports?
- Every 1 minute on paid plans. Cloud Scheduler also has a 1-minute minimum and public HTTP targets do not inherently require OIDC. Compare target type, authentication, retries, alert routing, and monitoring.
- How do I get notified if a push fails?
- Choose connected email, Slack, Discord, or Telegram channels under Notifications, or add a machine webhook under Integrations. If the final attempt fails, the payload includes status code, duration, size, error summary, and attempt history.
Ready to fix it?
Point Crontap at any URL. Pick any cron. Done.
WordPress, Shopify, Railway, Cloud Run, Vercel, HubSpot, Ghost, your own box. If it answers HTTP, Crontap can drive it on a clock you can read, in the timezone that actually matters, and page you when something breaks.
Free forever tier ・ No credit card required
/wp-cron.php?doing_wp_cron=1
Schedule
"every 5 minutes"
Next
in 23s