# Cron Expression Parser & Next Runs (`hipersoft/cron-next-runs`) Actor

Validate cron expressions, explain them in plain English, and compute the next N run times in any timezone. Sanity-check schedules across many jobs at once.

- **URL**: https://apify.com/hipersoft/cron-next-runs.md
- **Developed by:** [hiper soft](https://apify.com/hipersoft) (community)
- **Categories:** Developer tools, Other
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.001 / cron parsed

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Cron Expression Parser & Next Runs

**Validate cron expressions, explain them in plain English, and list their next run times** — in any timezone, for many expressions at once. Sanity-check schedules across all your jobs before they go live.

![Cron Expression Parser & Next Runs input — configure the options in the Apify Console](https://api.apify.com/v2/key-value-stores/SUfvnaFLd9z9eBCtV/records/cron-next-runs-input.png)

### What it does

- **Validates** each cron expression and flags bad ones.
- **Explains** it in plain English (e.g. "At 09:00, Monday through Friday").
- Computes the **next N run times** in your chosen IANA timezone.

### Use cases

- **DevOps** — audit cron schedules across many jobs and timezones.
- **Docs & dashboards** — turn cron strings into human-readable descriptions.
- **Debugging** — confirm exactly when a schedule will fire next.

### Input

```json
{ "expressions": ["0 9 * * 1-5", "*/15 * * * *"], "timezone": "America/New_York", "count": 5 }
```

| Field | Type | Description |
|---|---|---|
| `expressions` | array | Cron expressions to validate and expand. |
| `timezone` | string | IANA timezone (e.g. `UTC`, `Asia/Singapore`). |
| `count` | integer | Upcoming run times to list per expression (1–50). |

### Output

![Cron Expression Parser & Next Runs output — the results as a clean dataset](https://api.apify.com/v2/key-value-stores/SUfvnaFLd9z9eBCtV/records/cron-next-runs-output.png)

```json
{ "expression": "0 9 * * 1-5", "valid": true, "humanText": "At 09:00 AM, Monday through Friday", "nextRuns": ["2026-08-17T13:00:00.000Z", "..."], "timezone": "America/New_York" }
```

#### Output schema

| Field | Type | Description |
|---|---|---|
| `expression` | string | The cron expression. |
| `valid` | boolean | Whether it parsed successfully. |
| `humanText` | string | Plain-English description. |
| `nextRuns` | array | Next run times (ISO). |

### FAQ

**Which cron syntax is supported?** Standard 5-field cron plus common extensions (steps, ranges, lists).

**Can I automate it?** Yes — via [integrations on the Apify platform](https://apify.com/integrations) and the [Apify API](https://docs.apify.com/api/v2).

### Notes

Original clean-room implementation.

# Actor input Schema

## `expressions` (type: `array`):

One or more cron expressions to validate and expand, e.g. "0 9 \* \* 1-5".

## `timezone` (type: `string`):

IANA timezone for the computed run times, e.g. "UTC", "America/New\_York", "Asia/Singapore".

## `count` (type: `integer`):

How many upcoming run times to list per expression (1–50).

## Actor input object example

```json
{
  "expressions": [
    "30 2 * * *",
    "0 0 1 * *"
  ],
  "timezone": "UTC",
  "count": 5
}
```

# Actor output Schema

## `results` (type: `string`):

The results as dataset items.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "expressions": [
        "0 9 * * 1-5",
        "*/15 * * * *"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("hipersoft/cron-next-runs").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "expressions": [
        "0 9 * * 1-5",
        "*/15 * * * *",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("hipersoft/cron-next-runs").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "expressions": [
    "0 9 * * 1-5",
    "*/15 * * * *"
  ]
}' |
apify call hipersoft/cron-next-runs --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,hipersoft/cron-next-runs"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/UteWmkUDTF1F25WhG/builds/ULoFwVZxDzM9ZnkGF/openapi.json