> For the complete documentation index, see [llms.txt](https://docs.tessl.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tessl.io/automations/overview.md).

# Automations overview

Automate recurring work by declaring schedules in your tessl.json and pushing them to your default branch.

Automations run plugins on a schedule so recurring work happens without CI or GitHub Actions configuration.

## Define an automation in tessl.json

The primary way to create an automation is to declare a schedule in your project's `tessl.json`. Add a `schedules` block and push it to your default branch. Tessl syncs the manifest and creates the schedule when it can resolve the project and apply the entry. The schedule lives next to the code it runs against, so it is reviewed and version-controlled like any other change.

See [Schedules](/automations/overview/overview.md) for prerequisites, the `schedules` block reference, validation, and schedule behavior.

## Example schedules

{% content-ref url="/pages/jqRZh2ForMPs2Jpj4zox" %}
[Example Schedules](/automations/overview/overview/example-schedules.md)
{% endcontent-ref %}


---

# 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 dynamically by asking a question.

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

```
GET https://docs.tessl.io/automations/overview.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 `build a script that syncs our docs to a CMS` 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.