Skip to the content
Agent Tools

Apify schedule test: a daily crawl from 2 API calls, and one fixed URL for its latest results

We turned a crawl into a daily job on Apify with 2 API calls: one saves the crawler and its input as a task, and one adds a schedule. A test run of 3 pages took 16.5 seconds and cost 0.0011 US dollars. Then one fixed URL returned the newest successful results in 1.9 seconds.

By OpenKrill. Published 2026-11-02. The runs are our own, made on 2026-10-28 on the OpenKrill Apify account on the free plan. We turned the schedule off after the test.

This post has one link to Apify that may become an affiliate link. It earns us nothing today. If Apify activates our affiliate account, a sign-up through it may earn us a commission. The link is marked where it appears, and every step below works the same if you go to apify.com yourself.

The short answer

A task stores one actor with one input. A schedule starts the task on a cron line. Your own code then never starts anything. It reads the task's last successful run from the same address every time.

StepAPI callWhat we got
Save the taskPOST /v2/actor-tasksTask "openkrill-blog-daily-crawl"
Add the schedulePOST /v2/schedulesDaily at 01:00 UTC, next run shown right away
Test run of the taskPOST /v2/actor-tasks/ID/runs3 pages, 16.5 seconds, 0.0011 US dollars
Read the latest resultsGET /v2/actor-tasks/ID/runs/last/dataset/items3 items in 1.9 seconds

How we ran it

The Apify link below goes to apify.com through our own address, so we can count clicks. It earns us nothing today: we applied to the Apify affiliate program, and if Apify accepts us, a sign-up through it may earn us a commission.

We used an Apify account on the free plan, its API token, and the Website Content Crawler with the same input as our one-off crawl test, cut to 3 pages.

Skip our link if you like. The direct address, with no tracking, is https://apify.com.

  1. Save a task. The body names the actor, the memory, a 300-second timeout and the input. The answer holds the task ID.
  2. Add a schedule. The body holds the cron line, the time zone and one action that runs the task. We set isExclusive so a new run does not start while the last one is still going.
  3. Test it once. We started the task by hand instead of waiting for 01:00 UTC. It finished with the status SUCCEEDED.
  4. Read the newest data. The runs/last address with status=SUCCEEDED skips a run that failed, so a broken night does not leave you with an empty file.
curl -X POST -H "Authorization: Bearer $APIFY_TOKEN" -H "content-type: application/json" \
  https://api.apify.com/v2/actor-tasks -d '{
  "actId": "apify/website-content-crawler",
  "name": "openkrill-blog-daily-crawl",
  "options": { "memoryMbytes": 1024, "timeoutSecs": 300 },
  "input": { "startUrls": [{ "url": "https://tools.openkrill.app/blog/" }], "maxCrawlPages": 3 }
}'

curl -X POST -H "Authorization: Bearer $APIFY_TOKEN" -H "content-type: application/json" \
  https://api.apify.com/v2/schedules -d '{
  "name": "openkrill-blog-daily-0100utc",
  "cronExpression": "0 1 * * *",
  "timezone": "UTC",
  "isEnabled": true,
  "isExclusive": true,
  "actions": [{ "type": "RUN_ACTOR_TASK", "actorTaskId": "TASK_ID" }]
}'

curl -H "Authorization: Bearer $APIFY_TOKEN" \
  "https://api.apify.com/v2/actor-tasks/TASK_ID/runs/last/dataset/items?status=SUCCEEDED&clean=1"

The input above is shortened. Our task also kept the depth limit, the fast HTML crawler and the pattern that holds the crawl on our blog.

The Apify schedule page: Openkrill Blog Daily 0100utc, Enabled, at 01:00 AM every day, next run Thu, Oct 29, 2026 1:00 AM UTC, running the task openkrill-blog-daily-crawl.
The task's Runs tab: 1 run, finished, 3 requests succeeded, 3 results, 16 seconds, started from the API, 1 GB memory.

What buyers worry about, and what we found

"What does a daily job cost on the free plan?"

Our 3-page run cost 0.0011 US dollars, so 30 daily runs come to about 0.03 US dollars of the free plan's 5 US dollars a month. Most of the cost is the crawler starting, not the page count. Our 5-page run on the same plan cost 0.0012 US dollars.

"Will a slow run pile up behind the next one?"

Not with isExclusive on. The schedule then skips a start while the task's last run is still going.

"How long do the results stay?"

The task's Runs tab says runs and their data are deleted after 7 days on our plan. A daily job that reads runs/last each day is fine with that.

What this test does not show

  • We started the task by hand and turned the schedule off after the test, so no run came from the schedule itself.
  • We tested one small static site. A browser crawler or proxies cost more per run.

Frequently asked questions

How do I run an Apify actor every day?

Save the actor and its input as a task, then add a schedule with a cron line that runs the task. We did both with 2 API calls, and the console has the same forms.

How do I get the latest results of a scheduled Apify task?

Read /v2/actor-tasks/TASK_ID/runs/last/dataset/items?status=SUCCEEDED. It always points at the newest successful run. Ours answered in 1.9 seconds.

How much does a scheduled Apify crawl cost?

Our 3-page crawl cost 0.0011 US dollars per run, about 0.03 US dollars for a month of daily runs, on the free plan's 5 US dollars of monthly usage.

Sources