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

# Schedules

> Cron-based scheduled jobs

Schedules trigger functions, agents, or pipelines on a cron timer.

**Key properties:**

| Property | Description |
| - | - |
| `name` | Unique name (per user) |
| `schedule_type` | `function`, `agent`, or `pipeline` |
| `target_namespace` / `target_name` | Function, agent, or pipeline to trigger |
| `cron_expression` | Standard cron expression (e.g., `0 9 * * MON-FRI`) |
| `timezone` | Schedule timezone (default: `UTC`) |
| `input_data` | Input passed to the function or agent |
| `content` | Message content (agent schedules only) |

For agent schedules, a new chat is created for each run with the schedule name and timestamp as the title.

For pipeline schedules (`scheduleType: pipeline` + `pipelineName: ns/name` in YAML), the schedule fires the pipeline with `input_data` as the run input — the standard way to poll an external API on a cursor (see [Pipelines](https://docs.sinas.co/build-resources/pipelines.md)). A `perUser` pipeline fans out to one run per connected user.

**Endpoints:**

```
POST   /api/v1/schedules              # Create schedule
GET    /api/v1/schedules              # List schedules
GET    /api/v1/schedules/{name}       # Get schedule
PATCH  /api/v1/schedules/{name}       # Update schedule
DELETE /api/v1/schedules/{name}       # Delete schedule
```


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