Blog · No-code
Cron for Bubble and other no-code visual builders
Bubble's recurring workflows are powerful, but the cadence floor and the workflow-unit cost make every-minute work painful. These posts cover the external cron pattern that gets you there.
About this topic
No-code
Bubble's recurring workflow runs once on a schedule and reschedules itself, which works until you realize each tick burns workflow units and the cadence floor is plan-dependent. Going from once-an-hour to once-a-minute work on Bubble alone often requires moving up a plan or two, plus the workflow-unit cost adds up before the workflow does anything useful. Webflow's classic visual editor doesn't ship periodic logic at all, which means anything cadence-driven (newsletter digests, cache warming, sitemap refreshes) ends up wired to a third-party.
The pattern is small: expose a Workflow API endpoint in Bubble (or a public route in your no-code backend), authenticate it with a token, and let Crontap call it on the cadence you actually need. 1-minute floor on Pro, per-schedule IANA timezones for region-specific work, retries on 5xx, and failure alerts that surface a stuck workflow in real time. The posts below walk Bubble specifically; the same shape applies to any visual builder that exposes a callable endpoint.
Blog on No-code
2 items- Comparisons
Bubble Scheduled Workflows vs external cron: the workload-unit math
Bubble's `Schedule API Workflow` action is itself a workflow action billed at 0.7 WU per call. At minute cadence that is 30,240 WU/month on bookkeeping alone, ~17% of a Starter plan before any work runs. Here is the math and the external cron pattern that drops scheduling overhead to zero.
- Guides
How to schedule a Bubble.io workflow every minute (without burning workload units)
Bubble's native scheduler stops at daily and the only sub-daily path is a recursive API workflow that pays 0.7 WU per re-schedule. Here is the click-by-click setup for triggering a public API workflow from external cron in 5 minutes, so the schedule itself costs 0 WU.
Related on Crontap
The same No-code topic, from other angles.
FAQ
Common questions on No-code
- Bubble's recurring workflow already covers cron. Why an external one?
- It does, until you do the workflow-unit math. Each tick costs units, and the lower cadences are plan-gated. For every-minute work, an external Crontap schedule calling a Workflow API endpoint costs one request per tick instead of a unit-per-tick. The dedicated post has the breakdown.
- Will I still need Bubble's scheduler for in-app actions?
- For per-user actions like sending an email in 3 days, yes, the in-app scheduler is the right shape. For app-wide periodic work (digests, syncs, cache warming, polling) the external pattern is cheaper and easier to reason about.
- Does this work for Webflow too?
- Webflow doesn't expose a Workflow API. The usable pattern is to host the periodic work in a small companion backend (Vercel function, Cloudflare Worker, Railway service) and let Crontap call that. Webflow stays the front of house.
- How do I keep the Bubble Workflow API endpoint private?
- Bubble's Workflow API supports an Authorization header. Crontap sends custom headers per schedule, so a long random token on Bubble's side and the same token in the Crontap schedule header keeps the endpoint locked to your scheduler.
More from Crontap
Topics across the site.
Every topic Crontap covers, in one row. Each one has its own page on the blog surface.
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