Create your first cron job
This tutorial walks you through creating a scheduled HTTP cron job on your personal team and reading the first execution log. Expect about 10 minutes.
Onboarding uses this same path when your primary job is cron jobs. Crystade runs the new job immediately so you do not wait for the next schedule tick.
Prerequisites
Section titled “Prerequisites”- A Crystade account signed in with Google or GitHub
- A public HTTP or HTTPS URL you are allowed to call
- Your personal team selected in the team switcher
Step 1: Create the job
Section titled “Step 1: Create the job”-
Open Cron Jobs on your personal team and choose Create a job (or New Job).

-
Name the job after the task, for example
Keep-alive ping.
-
Set a Unix cron expression. On Free, the minimum interval is 5 minutes (for example
*/5 * * * *). Starter and Standard allow 1 minute. -
Set the URL, HTTP method (
GET,POST,PUT,PATCH, orDELETE), optional headers (max 20), and optional text body (max 256 KB). Body formats are plain text, JSON, or XML. -
Set connection timeout (max 15 minutes) and redirect-follow limit (max 10).
-
Save the job.
Private, loopback, and link-local URLs are rejected. A definition change takes effect within 5 minutes for scheduled runs. A manual trigger always uses the latest saved definition.
Step 2: Run it once
Section titled “Step 2: Run it once”-
From the job page, trigger a manual run. Manual trigger uses the latest definition even if the job is disabled.
-
On Free, manual triggers are limited to 50 per team per week. This first-win run counts toward that limit.
-
Wait on the page until an execution appears, or until the short wait limit is reached. If the wait times out, the job already exists and later scheduled runs still execute.
Disabled and paused jobs are not picked up by the scheduler. You can still trigger them manually when they are disabled.
Step 3: Read the execution log
Section titled “Step 3: Read the execution log”-
Open the execution from the job’s history.
-
Confirm the request snapshot (method, URL, headers, body), response status, and timing: scheduled at, started at, completed at.
-
On Free, response body capture is 0 bytes. Starter captures up to 4 KB; Standard up to 16 KB. All executions are retained; how far back you can see them depends on the plan (30 / 90 / 365 days).