Use rrule.net as an n8n Schedule Trigger

When this helps

Use this integration when cron is too rigid or too hard to audit. rrule.net owns the schedule logic, validates the recurrence before publication, and calls n8n whenever an occurrence is due. Natural-language inputs can be written in English, French, or other languages supported by the parser.

Community node setup

Install the rrule.net community node package in n8n, then add the rrule.net Schedule Trigger node to your workflow.

1. Install @rrulenet/n8n-nodes-rrulenet as an n8n community node.
2. Create an API key from your rrule.net dashboard.
3. Create a rrule.net API credential in n8n.
4. Add rrule.net Schedule Trigger to a workflow.
5. Configure the schedule name, schedule text, timezone, and deactivate behavior.
6. Publish the workflow.

During local testing, expose your local n8n instance through a public tunnel and set n8n's WEBHOOK_URL to that public URL before publishing a live workflow.

What the node manages

The node keeps the n8n workflow connected to a persistent remote schedule in rrule.net.

Workflow published
  -> rrule.net Schedule Trigger creates or resumes a remote schedule
  -> rrule.net evaluates the recurrence and calls the n8n production webhook
  -> n8n receives one normalized trigger item

Workflow unpublished
  -> the remote schedule is paused by default
  -> or deleted if you choose Delete on deactivate

Trigger output

Each execution emits one normalized item. Downstream n8n nodes can use the schedule identifiers, timestamps, timezone, original input, and raw webhook payload.

{
  "schedule_id": "sched_...",
  "schedule_name": "n8n lead sync",
  "execution_id": "exec_...",
  "scheduled_for": "2026-04-30T09:00:00.000Z",
  "executed_at": "2026-04-30T09:00:08.236Z",
  "timezone": "Europe/Paris",
  "input_type": "natural",
  "input_value": "Every business day at 9:00 and weekends at 10:00",
  "raw_payload": {}
}

Native n8n Schedule Trigger vs rrule.net

Manual webhook workflow

If you do not want to install a community node, or if you want to inspect the raw webhook contract, you can still use the manual workflow template. It receives webhook deliveries from rrule.net, normalizes the payload, and responds quickly with a 200.

rrule.net schedule
  -> n8n Webhook Trigger
  -> Normalize rrule.net payload
  -> Acknowledge rrule.net
  -> your n8n workflow actions