Use case
Send class reminders, review asks, and daily digests on local time.
WhatsApp Business and the Meta Cloud API deliver messages. They do not schedule them. Twilio's WhatsApp wrapper does not schedule them either. Crontap is the local clock that fires your send endpoint on the cadence and timezone your students, customers or members actually live in.
Free plan · no credit card required
The problem
Why this is painful without the right tool
- WhatsApp Business has no scheduler primitive of its own; the official APIs deliver, they do not schedule.
- Twilio's WhatsApp wrapper has no scheduler either; you still need a clock somewhere.
- Your customer backend has the send endpoint built; it just needs a tick every 30 minutes during local school hours.
- Local timezone matters: classes at 9am Asia/Kolkata should be 9am Asia/Kolkata, not 9am UTC, and 9am Europe/London is a different schedule again.
The fix
How Crontap solves it
Build a /whatsapp-notification?eventName=... endpoint on your side that reads a queue and dispatches via the Meta Cloud API (or Twilio). Let Crontap fire it on the right local cadence, one schedule per event type, each in the right IANA timezone. Failures alert to email / webhook (Slack / Discord / Telegram).
*/30 9-18 * * *One concrete pattern from the dataset: an Indian kids-education business sending WhatsApp class reminders every 30 minutes during local school hours in Asia/Kolkata, plus daily google-review asks at 11:12 local, plus monthly batch reminders, plus daily lead-count metrics, plus a 02:30 nightly lead-tracker insert. The send endpoint is /whatsapp-notification?eventName=...; Crontap fires it on the right local cadence per event, and the endpoint reads a queue and dispatches via the Meta Cloud API.
Real event types this customer drives, all under one Crontap account: class_reminder_to_students_india, google_review, monthly_batch_reminder_2_L1_Finished, metrics_lead_count, insert_new_leads_into_messageTracker. One schedule per event, each on its own cron, all in Asia/Kolkata.
FAQ
Common questions
- Does Crontap talk to WhatsApp directly?
- No. Crontap hits your send endpoint. Your endpoint handles the WhatsApp Cloud API or Twilio call and the message-template selection. Crontap is the clock; your code is the messenger.
- What about the 24-hour messaging window?
- WhatsApp's 24-hour customer-care window and message-template policy are orthogonal to scheduling. Crontap fires your endpoint on time; your endpoint decides whether to send a session message or a template, and which template to use.
- Can I localize per-student or per-customer?
- One schedule per timezone is the cleanest pattern. Crontap supports arbitrary IANA timezones per schedule, so a 9am cohort in Asia/Kolkata, a 9am cohort in America/New_York, and a 9am cohort in Europe/London become three schedules pointed at the same endpoint with different cron timezones.
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