Use case
External cron for self-hosted and cloud n8n.
The n8n Cron node is fine when the worker is always running. The two failure modes that break it are a self-hosted instance that crashes silently, and a cloud-n8n plan that meters workflow executions. Crontap fires the workflow's Webhook trigger from outside n8n, on any cron, in any IANA timezone.
Free plan · no credit card required
The problem
Why this is painful without the right tool
- Self-hosted n8n needs the worker process always running for the Cron node to fire; if the host reboots or the process crashes, the cron silently stops.
- n8n Cloud meters workflow executions; the schedule itself does not cost extra, but a chatty cron pattern still bills the executions.
- The Cron node lives inside the workflow, so cadence changes ship through the workflow editor instead of a settings page.
- Failures from the Cron node land in the n8n executions log; rich alerting to email or webhook is left for you to wire up via a separate failure workflow.
The fix
How Crontap solves it
Add a Webhook trigger to the workflow and copy the URL. Paste into Crontap and pick a cron. The workflow fires every time Crontap calls; the cadence and timezone live in Crontap, not in the n8n Cron node. Failures alert to email / webhook (Slack / Discord / Telegram).
0 9 * * 1For self-hosted n8n, the external clock pattern fixes the silent-crash failure mode: if the n8n process is down, Crontap's call returns a connection error, the failure alert fires, you find out within minutes. The Cron node inside n8n cannot tell you that the worker stopped because the worker would be the one telling you.
For n8n Cloud, the change is mostly cadence flexibility and central dashboarding. Multi-workflow accounts can have twenty schedules in Crontap, each pointed at a different workflow Webhook URL, with one alerting channel.
Cross-link: see the existing walkthrough at Schedule n8n workflows externally via webhook for the click-by-click setup.
FAQ
Common questions
- Can I still use the n8n Cron node alongside Crontap?
- Yes. Mix freely. Keep the Cron node for in-workflow logic that benefits from being co-located (a sub-workflow that needs to fire 30 seconds after another step). Use Crontap for the top-level trigger and for everything where you want central alerting.
- What's the shortest interval Crontap supports?
- Every 1 minute on paid plans. Free tier available for slower cadences. The n8n Cron node also supports minute cadence; the difference is the failure-alert story and whether the trigger survives a worker crash.
- How do I get notified if a workflow run 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 a workflow that errored at the n8n Webhook node shows up in the alert with the response body included.
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