−50%

50% off your first month on any paid plan · code WELCOME50 · until Nov 30

Start free →
Guide

Cloud Cron for Email Campaigns: Scheduled Sends Without the Infrastructure

Email campaigns run on schedules. Weekly newsletters go out Tuesday at 10 AM. Drip sequences fire 3 days after signup. Digest emails compile overnight activity and land in inboxes by 8 AM. All of these need a reliable trigger, and most teams duct-tape it together with server cron or queue workers that nobody monitors. Cloud Cron for email campaigns offers a simpler way: an external trigger that fires on schedule without touching your server.

Why email scheduling breaks more often than you'd expect#

The email itself usually works. The template renders, the SMTP connection sends, the recipient gets the message. What breaks is the trigger, the thing that says "now" at the right time.

Server-side cron is the default trigger for scheduled emails. A crontab entry fires a script or artisan command, the script queries the database for pending emails, and the send happens. Simple enough until the server restarts and nobody re-enables the crontab. Or the queue worker dies and emails pile up in the jobs table. Or a deploy replaces the crontab and the email schedule vanishes. We watched a client's weekly newsletter silently stop for three weeks after a routine server migration because the crontab wasn't part of the deployment checklist.

The pattern is always the same: the email system works fine, but the clock that triggers it doesn't. Reliable cron email automation needs a trigger that survives infrastructure changes. That's exactly what cloud cron for email campaigns does.

How Cloud Cron replaces server cron for email sends#

Cloud Cron hits an HTTP endpoint on a schedule you define. Your application receives the request and does whatever it needs to. In this case, send emails. The trigger lives outside your infrastructure, so server restarts, deploys, and queue crashes don't affect when the request fires.

The setup takes about two minutes. Create a Cloud Cron monitor in WatchCron, set the URL to your email endpoint (something like https://app.example.com/api/cron/send-newsletter), choose the schedule, and you're done. Cloud Cron sends the HTTP request at the scheduled time and monitors whether your endpoint responds successfully.

That last part matters. If your endpoint returns a 500 or doesn't respond at all, WatchCron alerts you through Slack, email, Telegram, or 16 other channels. With server cron, a failed email send writes to a log file that nobody reads. With Cloud Cron, you get a Slack message within minutes.

Email campaign patterns that work with Cloud Cron#

Not every email belongs on a cron schedule. Transactional emails (password resets, order confirmations) fire immediately on user action. But these common patterns do need a scheduled trigger:

Weekly newsletters. The most straightforward case. Set Cloud Cron to 0 10 * * 2 (Tuesday at 10 AM) and point it at your newsletter endpoint. If you need help with expressions, the cron expression builder can help. The endpoint queries subscribers, builds the email, and sends. If you use a service like Mailchimp or SendGrid, the endpoint can trigger their API instead of sending directly.

Drip sequences. A daily Cloud Cron job at 9 AM queries users who signed up N days ago and sends the appropriate drip email. Day 1 gets the welcome, day 3 gets the feature tour, and day 7 gets the upgrade nudge. We run our own onboarding sequence this way: one endpoint, one schedule, the logic lives in the application code where it's testable and version-controlled.

Activity digests work especially well as a scheduled email cron job. A nightly run at 11 PM compiles the day's activity (new comments, status changes, monitor alerts) into a single digest email per user. Better than real-time notifications for users who don't want 15 separate emails about 15 separate events. The key is batching: one database query collects all events per user, one template renders them, one send per user instead of one per event.

For re-engagement campaigns, a weekly job checks for users who haven't logged in for 30 days and sends a "we miss you" email. Simple query, simple send, but it needs to run reliably every week or you miss the re-engagement window entirely. Add deduplication logic so that users who already received a re-engagement email don't get another one if the job runs twice.

Securing your scheduled email endpoint#

Your email endpoint is a URL that triggers sends. You don't want anyone with the URL to fire off your entire newsletter. Is this a realistic threat? Yes, if the URL leaks through logs, error messages, or a careless commit.

First, use a secret token. Cloud Cron can send custom headers with each request. Add an Authorization: Bearer your-secret-token header and validate it in your endpoint. If the token doesn't match, return a 401 and don't send anything. Always use HTTPS for your endpoint, since a bearer token over plain HTTP is visible to anyone intercepting traffic.

Second, whitelist the request IP. WatchCron publishes its sending IPs on the /ips page. Configure your firewall or application middleware to only accept requests from those addresses. This works well as a secondary check alongside the token.

Both together give you defense in depth. The token proves the request is authorized, the IP check proves it's coming from the right source.

Scheduled email cron: handling time zones and send windows#

Email open rates depend heavily on send time. A newsletter sent at 10 AM EST reaches European subscribers at 3-5 PM and Australian subscribers around midnight or 1 AM. If your audience spans time zones, a single cron schedule means someone always gets the email at the wrong time.

The cleanest approach: split your subscriber list by time zone region and create separate Cloud Cron jobs for each. One fires at 10 AM US Eastern (0 15 * * 2 in UTC), another at 10 AM Central European (0 9 * * 2 in UTC), a third at 10 AM AEST (0 0 * * 2 in UTC). Each hits the same endpoint with a query parameter like ?region=us-east that filters subscribers.

Is this more work than a single send? Yes. But the open rate difference between "delivered at 10 AM local" and "delivered at 3 AM local" can be 5-15 percentage points, and for a weekly newsletter that's the difference between engagement and the spam folder. We split our own digest sends into three regional windows and saw open rates climb noticeably within the first month.

What about queue-based email systems?#

Laravel queues, Sidekiq, Celery. Most frameworks have job queues that handle email sending. Cloud Cron doesn't replace your queue. It replaces the trigger that dispatches jobs into the queue, effectively turning your email cron job into a managed, monitored HTTP call instead of a fragile crontab entry.

Your endpoint receives the Cloud Cron request, dispatches 10,000 newsletter jobs into the queue, and returns a 200. The queue workers process the jobs at their own pace. Cloud Cron's job is done the moment your endpoint acknowledges the request. If the queue backs up or a worker crashes, that's a separate problem, but at least you know the dispatch happened because Cloud Cron confirmed the 200 response.

This separation means you can scale queue workers independently of the trigger. Add more workers during high-volume sends, scale back during quiet periods. The trigger doesn't care how many workers you have. We dispatch about 8,000 onboarding emails weekly this way, and the endpoint returns in under 200ms because the actual sending happens in the queue.

Monitoring your email cron jobs in production#

Cloud Cron includes monitoring by default. That's the whole point. But email sends deserve extra attention because failures are invisible until customers complain.

Set your endpoint to return meaningful HTTP status codes. 200 means emails dispatched successfully. 500 means something went wrong. 503 means the mail provider is down. WatchCron tracks each response and alerts on failures, so you know within minutes if Tuesday's newsletter didn't go out.

For additional safety, have your endpoint return the count of emails dispatched in the response body. Cloud Cron logs the response, so you can check later whether Tuesday's send dispatched 5,000 emails or 50 (which probably means your subscriber query broke).

For more on scheduling patterns, see our cron jobs overview, or explore other Cloud Cron use cases like scheduled backups and data synchronization.

Frequently asked#

No. Cloud Cron triggers an HTTP endpoint on a schedule. Your application handles the actual email sending through SMTP, an API like SendGrid or Mailchimp, or a queue system. Cloud Cron is the clock, not the mailer.

Create a Cloud Cron monitor with the cron expression 0 10 * * 2 (Tuesday at 10 AM UTC) and point it at your newsletter endpoint. The endpoint queries subscribers and triggers the send. Adjust the hour for your target time zone.

Cloud Cron logs the failed response and alerts you through your configured channels (Slack, email, Telegram, etc.). You'll know within minutes that the scheduled send didn't work, instead of finding out days later when subscribers complain.

Use a secret bearer token in the Authorization header (Cloud Cron supports custom headers) and validate it in your endpoint. Always use HTTPS. Optionally, whitelist WatchCron's sending IPs listed on the /ips page for additional security.

Yes. Create separate Cloud Cron jobs for each time zone region, each hitting the same endpoint with a region parameter. This delivers emails at local morning hours for each audience segment instead of one global send time.

Written by Vitalii Holben

Founder of WatchCron. Full-stack developer building monitoring tools that help teams keep cron jobs, uptime, and SSL certificates under control. Based in Europe, shipping code since 2014.

Start monitoring in under 2 minutes.

Free plan includes 20 checks · No credit card required
Pricing Docs
Log in Start free →