Create your first scheduled job

This guide walks you from a brand-new account to a working scheduled HTTP job in a few minutes. You will create the job, confirm it ran, and trigger it on demand to make sure everything works.

Sign up and open the dashboard

Create a free account at cronjobpro.com, then open your dashboard. The Free plan is enough to follow this guide, and you can move to a higher plan later when you need more active jobs, more daily runs, or shorter intervals.

Create your first job

In the dashboard, click New Job and fill in the form. The only required fields are a target URL and a schedule, but the steps below cover the settings most people set on day one.

1. 1

   Name the job

   Give it something recognizable, like Nightly cache warm. The name is just for you and helps you spot the job in lists and alerts.

2. 2

   Enter the target URL and method

   Paste the full https URL CronJobPro should call. Choose the HTTP method your endpoint expects: GET, POST, PUT, PATCH, DELETE, HEAD, or OPTIONS. For a simple health or trigger endpoint, GET is usually right.

3. 3

   Set the schedule

   Choose a 5-field cron expression or a simple interval. If you are not fluent in cron syntax, use the cron generator to build the expression visually, then paste it in. Example: 0 9 * * * runs every day at 09:00.

4. 4

   Pick a timezone

   Each job has its own timezone, and the schedule is evaluated in it. CronJobPro keeps local clock time stable across daylight-saving changes, so a 09:00 daily job stays 09:00 local. Pick UTC if you want to avoid DST ambiguity entirely.

5. 5

   Save

   Click Save. The job becomes active immediately and will fire at its next scheduled time. Optional settings like request headers, a body, a timeout, retries, basic auth, and an overlap policy can be added now or edited later.

Confirm it ran

Open the job to see its Executions list and Last status. Each execution shows when it ran and whether it succeeded, so you can verify the schedule is working as expected.

• Last status: shows success or failure for the most recent run.
• Executions: a history of past runs with timestamps and outcomes.
• If a run failed, check the target URL, method, and any required headers or auth, then test again.

Test it now with Run now

You do not have to wait for the next scheduled time. Click Run now on the job to trigger the request immediately, then refresh the Executions list to see the result. Note that a Run now execution counts toward your plan's daily-run quota, just like a scheduled run.

Next: set up alerts

Once your job runs reliably, decide how you want to hear about problems. Under Settings then Notifications you can add channels such as email, Slack, Discord, Microsoft Teams, a webhook, PagerDuty, or Opsgenie, and CronJobPro will notify you on failure, recovery, and when a job is auto-disabled.

Open Settings to configure notifications →