Sealos Logo

Create Your First CronJob

Create your first CronJob on Sealos with one fixed visit a URL walkthrough that uses Webhook.site and exact field values.

This is the canonical zero-to-one CronJob (scheduled task) tutorial for Sealos.

Follow this page when you want one fixed first-success path instead of choosing among different task types.

By the end of this guide, you will create one visit a URL task that calls a unique https://webhook.site URL and stays easy to repeat with the same exact setup pattern.

Before You Begin

Use this tutorial if all of the following are true:

  • You can sign in to the Sealos console.
  • You can open https://webhook.site in another browser tab.
  • You will use the task type visit a URL.
  • You will use one copy-paste schedule value: */5 * * * *.

Keep this first run narrow.

The goal is to complete one visible success case with the exact values in this page, not to explore every CronJob option on the first pass.

What You Will Configure

This tutorial uses one fixed setup so you do not have to choose values while you are learning the basic Sealos flow.

Open Webhook.site, keep the generated target page available, and use the exact values below in the Sealos form.

FieldValue
CronJob namefirst-cronjob-url-check
Task typevisit a URL
Target URLthe unique URL generated by https://webhook.site
Schedule*/5 * * * *

The name, task type, and schedule stay fixed for this walkthrough.

The only value you generate during setup is the unique URL from Webhook.site.

Create the CronJob

  1. Open https://webhook.site in a browser tab. Let the page generate a unique URL for you. Keep that page open so you can copy the exact target URL into Sealos.

  2. Sign in to the Sealos console. Start from the workspace where you want this CronJob to run.

  3. Open the CronJob module. Stay on the CronJob surface for the full setup so the flow remains simple and consistent with this tutorial.

  4. Click the action that adds or creates a CronJob. Wait for the creation form to open before you start entering values.

  5. Set the CronJob name to first-cronjob-url-check. Use this exact name so it is easy to recognize later in the CronJob list.

  6. Choose the task type visit a URL. For this first-success path, do not choose run a command. For this first-success path, do not choose scale an app.

  7. Paste the unique Webhook.site URL into the target URL field. Use the exact URL from the open https://webhook.site page so the request later arrives at the page you are already watching.

  8. Paste the schedule */5 * * * * into the schedule or Cron expression field. Keep this exact value for your first run so you can copy and paste one known schedule instead of inventing a new one.

  9. Review the form and save or deploy the CronJob. After you submit it, keep the same Webhook.site page open because the next phase of this tutorial uses that page to confirm the request arrived.

This page gives you one exact setup path.

Once the CronJob is created, continue with the later verification guidance for checking that Sealos recorded the run and that Webhook.site received it.

How the Schedule Works

The schedule */5 * * * * means this CronJob is scheduled to run every 5 minutes.

For this guide, wait for the next run to appear in Sealos instead of expecting an exact-second execution time.

This page is not a full Cron expression reference.

Verify the CronJob

Use both checks below before you call the first run successful:

  • In Sealos, wait for the next run to appear and confirm a new run or history entry shows for first-cronjob-url-check.
  • In Webhook.site, confirm a request appears for the unique URL you configured.

The request timestamp should be later than the time you created or saved the CronJob.

Do not treat Sealos history alone as full proof for this visit a URL tutorial.

Success

You completed your first CronJob run and verified that the request arrived.

Next Steps

  • Update a CronJob when the CronJob already exists and you need to change future behavior.
  • Pause or Resume a CronJob when you need to stop future scheduled runs temporarily and allow them again later.
  • Delete a CronJob when you no longer need the CronJob and want to stop future scheduled runs completely.
  • Reuse the same workflow with a new Webhook.site URL if you want to repeat the first-success check.

Explore with AI

Get AI insights on this article

Share this article

Tip:AI will help you summarize key points and analyze technical details.

Last updated on

Sealos LogoSealos

Unify Your Entire Workflow.

Code in a ready-to-use cloud environment, deploy with a click. Sealos combines the entire dev-to-prod lifecycle into one seamless platform. No more context switching.

Share to LinkedinShare to XShare to FacebookShare to RedditShare to Hacker News

On this page