Event scheduling from natural language
Describe a known event directly in the schedule input, then define when each workflow should run relative to that event. rrule.net validates the intent, computes the occurrences, and keeps the schedule inspectable.
Try an event-aware input
Start from a plain-language schedule that includes the event, trigger timing, audiences, and local delivery time.
Next occurrences
Validate the input to preview the computed schedule.
What rrule.net extracts
The schedule input stays natural-language first. Internally, validation extracts the event, relative trigger, optional targets, and webhook context needed to run the schedule deterministically.
Event
The event is described in the input itself, including its date, point in time, or interval.
Triggers
The timing is relative to that event, such as 7 days before, 1 day before, or 1 day after.
Targets
When the input mentions several audiences or locations, rrule.net can keep separate target contexts and timezones.
Webhook context
Each execution can carry the schedule, occurrence, target, timezone, and metadata needed by the receiver.
Natural-language input
Write the event, relative trigger, timezone, and target context as one schedule description.
Target-aware execution
Use one logical schedule for multiple audiences, regions, systems, or workflow branches.
Inspectable schedules
Validate before creation, preview occurrences, and inspect the normalized schedule from the dashboard or API.
When to use event scheduling
Use it when the schedule is defined relative to a concrete event you already know: a maintenance window, migration window, incident drill, customer communication window, or any other event with explicit dates or times.