Context-aware scheduling you can explain

For workflows, APIs, and agents. Turn natural language, cron, RRule, or canonical JSON into schedules you can validate, simulate, execute, and observe across timezones, business events, and targets.

One deterministic scheduling model, available through the dashboard, REST API, n8n node, MCP server, CLI, and @rrulenet libraries.

Create a Schedule Try the API Explore Ecosystem

From schedule to webhook

Scheduling Lifecycle

From human intent to observable execution

rrule.net covers the complete path: interpret the intent, preview future occurrences, persist the canonical schedule, execute webhooks, and inspect what happened.

Validate

Parse natural language, cron, RRule, or recurrence JSON before anything runs.

Simulate

Preview future occurrences and catch timezone surprises before production.

Schedule

Persist canonical schedules, webhook targets, and execution context.

Execute

Deliver hosted webhook executions with bounded catch-up and idempotency inputs.

Observe

Inspect next occurrences, execution history, skipped runs, and lateness.

Contextual Scheduling

Schedule around the business event, not just the clock

Model a maintenance window once, then notify each audience at the right local time before the event. Every webhook execution carries the target context your workflow needs.

Reference Scenario

Global maintenance window

Event: September 15, 2026, 02:00-04:00 UTC
Triggers: 7 days before and 1 day before at 09:00 local time.
Targets: Paris customers / Europe/ParisPerth customers / Australia/Perth

Webhook context

Target-aware

{
  "schedule_name": "Maintenance customer triggers",
  "scheduled_for": "2026-09-08T01:00:00.000Z",
  "target": {
    "id": "perth",
    "label": "Perth customers",
    "timezone": "Australia/Perth",
    "metadata": {
      "market": "au",
      "segmentId": "brevo-au"
    }
  }
}

rrule.net does not own your customer segmentation. It schedules the trigger and sends enough context for n8n, Slack, Statuspage, CRM, or internal systems to route the workflow.

Ecosystem

One scheduling model across every surface

Use the same scheduling semantics from the dashboard, REST API, n8n, MCP, CLI, or libraries. Choose the surface that fits the workflow without changing the model.

Dashboard

Create, inspect, pause, and observe hosted schedules.

Open dashboard

REST API

Integrate validation, simulation, scheduling, and execution history.

Read API docs

n8n node

Use rrule.net as an advanced schedule trigger for workflows.

Install node

MCP server

Give agents context-aware exploration and scoped hosted-schedule lifecycle tools.

Explore MCP

CLI

Use one command surface for local and cloud scheduling workflows.

View CLI

Libraries

Embed the recurrence and event scheduling model directly.

View packages

Integrations

Use rrule.net when cron is too small for the workflow

The n8n community node lets workflows use rrule.net as an advanced schedule trigger while rrule.net handles recurrence parsing, preview, hosted execution, and webhook delivery.

Install the n8n Node Create an API Key

First workflow channel

n8n Schedule Trigger

Create or update rrule.net schedules from the workflow lifecycle.
Receive webhook executions with schedule and target context.
Keep recurrence parsing, preview, and hosted execution outside n8n.

Workflow handoff

Schedule

rrule.net owns the recurrence and next occurrences.

Trigger

The scheduler delivers a contextual webhook to n8n.

Route

n8n routes by target, timezone, metadata, or payload.

Open Foundation

RRule-compatible at the foundation, context-aware by design

The name reflects a durable scheduling standard, not a product boundary. rrule.net accepts cron and RRule, then extends a canonical model with natural-language input, composed schedules, events, targets, and hosted execution.

Canonical Model

@rrulenet libraries

The hosted platform relies on @rrulenet/recurrence and @rrulenet/events as the model underneath validation, simulation, hosted execution, schedule targets, and contextual event-relative triggers.

Temporal-based time model

Built on Temporal semantics for serious timezone and DST-aware recurrence computation.

Composable by design

Schedules can be simple rules, unions, intersections, or differences without forcing everything into one flat RRule.

Context-aware extension

Event-relative schedules and execution targets extend the same model instead of creating a separate workflow engine.

Get Started

Start with one schedule. Keep the same model as you scale.

Create a hosted schedule, try the API, or connect n8n. The scheduling semantics stay consistent across the ecosystem.

Create schedules
Use the dashboard to create, inspect, pause, and observe hosted webhook schedules.
Use the API
Validate, simulate, create schedules, and read execution history from your own app.
Connect workflows
Trigger n8n and other webhook workflows with the same contextual scheduling model.

Create a Schedule Try the API Explore n8n

Start with validation and simulation. Move into managed execution when the workflow is ready.