> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ruby.ad/llms.txt
> Use this file to discover all available pages before exploring further.

# Schedules

## Add triggers to your agents in the Agent Builder

We introduced a dedicated **Triggers** section in the **Agent Builder**. From there, you can create **schedules** for your agent to follow.

When setting up a **schedule**, you can specify a name, describe the frequency you'd like the agent to run at, and add an optional custom message that will be sent to the **agent**.
You can also specify a timezone you'd like the schedule to effect in. The timezone defaults to the user's location.

A **Large Language Model** is responsible to generate the actual schedule behind the hood. To make sure it generated the right thing, we added an entry that confirms the schedule the **agent** will effectively run at.
Here, it's confirming that the agent will run *at 8:00 AM, every week from monday to friday, in Los Angeles time*.

You just have to Save the **agent** for the **schedule** to be registered.

> [!NOTE]
>
> By default, each run's conversation appears only in your own conversation history. To share runs with your team, pick a Pod under **Where to create this conversation?**: the conversation is then created in that Pod, where all its members can see it.

## Who can add a trigger

You can add a trigger to an agent only if you can use that agent:

* The agent is published, or you're one of its editors.
* You have access to every Space that the agent's tools, knowledge, and skills come from.

Otherwise, saving the trigger fails with the error "The agent configuration was not found." Ask one of the agent's editors or an admin which Spaces the agent relies on, and request access to them.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.