Use case

Kick off freshness checks and overnight ELT on a real clock.

Overnight ELT jobs run, usually. When they do not, your 9am dashboard is stale and somebody screenshots it in Slack. Crontap is the external clock that fires the freshness endpoint on time and pages you when it fails, so the morning surprise lands at 4:05am instead of 9:30am.

Get started

Free plan · no credit card required

The problem

Why this is painful without the right tool

  • Overnight ELT skips silently when the orchestrator's worker is down or the dbt Cloud trigger is plan-gated.
  • dbt Cloud's run trigger is plan-gated; lower tiers cannot trigger via API on a schedule.
  • Airbyte's own scheduler is opaque; failures land in the Airbyte UI but the Slack alert is yours to wire up.
  • Snowflake tasks need a trigger; pairing TASK with EXTERNAL FUNCTIONS or with the Snowflake REST API is more setup than a small external cron.

The fix

How Crontap solves it

Crontap fires the freshness or ELT-trigger endpoint on a clock (dbt Cloud's API, Airbyte connection-trigger URL, your Snowflake task wrapper, your warehouse's health endpoint). Failures alert to email / webhook (Slack / Discord / Telegram) with the run's status, duration, and response body.

cron expression
0 4 * * *
Nightly at 04:00 local, trigger the warehouse ELT run.

Two patterns are common. First, a single morning trigger at 04:00 that kicks off the ELT, plus a 09:00 freshness ping that checks the warehouse for fresh tables and alerts if the 04:00 run never landed. Second, an hourly freshness ping against your Snowflake / BigQuery health endpoint, with the ELT trigger living elsewhere (Airflow, dbt Cloud, your own orchestrator).

For multi-warehouse setups, one Crontap schedule per warehouse keeps the dashboard parseable. Failures alert per warehouse; pause per warehouse during maintenance windows.

FAQ

Common questions

Will this replace dbt Cloud or Airbyte's scheduler?
Not for orchestration logic; those tools own the dependency graph. Crontap fires the trigger URL and adds the alerting story; the orchestrator still owns the actual run plan.
What's the shortest interval Crontap supports?
Every 1 minute on paid plans. Free tier available for slower cadences. Most warehouse freshness patterns sit at every 15 minutes, hourly, or daily.

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

GET

/wp-cron.php?doing_wp_cron=1

Running
Your next schedule

Schedule

"every 5 minutes"

Next

in 23s