> For the complete documentation index, see [llms.txt](https://developer.kizen.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.kizen.com/docs/concepts/agentic-workflows/automation-code-steps/recurrence-rules-rrule.md).

# Recurrence Rules (RRule)

Learn how to use recurrence rules (RRULE) in Kizen to schedule advanced automation triggers, with examples and tools for building complex schedules.

Recurrence rules are a [standardized](https://datatracker.ietf.org/doc/html/rfc2445#section-4.8.5.4) way to define the schedule for a recurring event like an <code class="expression">space.vars.automation</code> Trigger. <code class="expression">space.vars.Kizen\_company\_name</code> provides a simple, easy to use UI set up recurring events, but for advanced or complex cases you may enter RRULEs directly.

For example, if you wanted your <code class="expression">space.vars.automation</code> to run on the second Monday and last Friday of each month:

```apache
RRULE:FREQ=MONTHLY;INTERVAL=1;BYDAY=2MO,-1FR
```

There are a number of community-maintained and official [tutorials](https://www.nylas.com/blog/calendar-events-rrules/), [calculators](https://icalendar.org/rrule-tool.html), and [validators](https://balsoftware.net/rrule/) you can use to create advanced schedules.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developer.kizen.com/docs/concepts/agentic-workflows/automation-code-steps/recurrence-rules-rrule.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
