Get started

Quick start

Create an account, add a collection, and schedule your first HTTP task.

Before you start

You need:

  • A reachable HTTPS (or HTTP) endpoint CronFox can call
  • An email address for signup (or a Google account)

Starter plan limits apply on day one: 2 tasks, 60-minute minimum cadence, 2 integrations, 7-day history. See Plans and limits.

Step-by-step

  1. Create an account
    Open Create account. Sign up with email and password (accept the legal terms) or continue with Google. Confirm your email if prompted — unverified accounts do not get scheduled runs.

  2. Open Collections
    After login you land on the dashboard. In the left sidebar, go to Collections.

  3. Create a collection
    Click New Collection (or the equivalent create control). Give it a clear name, such as Getting started or Ops. Collections are folders; they do not run by themselves.

  4. Open the collection
    Click the collection to open /collections/view?id=…. Tasks are created and edited only from this view — there is no separate /tasks page.

  5. Add your first task
    Create a new task and fill in at least:

    • Name — something you will recognize in history
    • URL — the endpoint CronFox should call (for example https://example.com/api/hourly)
    • Method — usually GET or POST
    • Schedule — a five-field cron expression that respects your plan’s minimum cadence (Starter: no more often than once per hour)

    Example hourly schedule: 0 * * * * (at minute 0 of every hour).

  6. Save and enable
    Save the task and leave it enabled. Disabled or archived tasks do not run on schedule.

  7. Optional: run now
    From the task’s execution view, use Run now to fire one execution immediately without waiting for the next cron tick.

Verify the run

  1. Open the task from the collection (/collections/view?id=…&taskId=…).
  2. Check Executions for a new row with status completed or failed.
  3. If it failed, open the details and confirm the URL, method, and any auth headers.

Tip: While testing, start with a public GET endpoint you control. Add auth headers and a request body after the first successful run.

What to do next