Use case
Scheduled Firebase work without the Blaze plan.
Firebase Scheduled Functions require the Blaze billing plan because they sit on Cloud Scheduler under the hood. Crontap is the external alternative: call your own HTTPS endpoint on any cron, your endpoint talks to the Firebase Admin SDK, and you stay on the Spark plan if your other usage allows it.
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 cost surface and the IAM surface are the difference.
- 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 (an HTTPS Cloud Function, a Cloud Run service, an FCM-aware backend on your own server) on any cron in any IANA timezone. Your endpoint talks to the Firebase Admin SDK or FCM directly. Failures alert to email / webhook (Slack / Discord / Telegram).
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. Free tier available for slower cadences. Cloud Scheduler also has a 1-minute minimum; the difference is the cost surface and the lack of per-target IAM.
- How do I get notified if a push fails?
- Wire failure alerts to email / webhook (Slack / Discord / Telegram) on the schedule's Integrations panel. The failure payload includes the run's status code, duration, and response body so an FCM rejection or a backend timeout shows up in the alert.
Related guides
Adjacent use cases
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