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

# Automations

Automations run work without a manual start. Each automation pairs a trigger — a time-based cron schedule, or when a run finishes — with an action: run a feature suite, run a load test, or run an AI assistant job.

![The Automations view](/files/XLRmzQmWUPf0BN6rDq2Q)

## Create An Automation

1. Select **Automations** from the navigation rail.
2. Select **+** (New automation) in the list rail.
3. Name it, then choose a **Trigger mode**:
   * **Time (cron)** — pick a schedule preset and timezone (for example, daily at 02:00 UTC).
   * **When a run finishes** — run automatically after a run completes; optionally only when it finished `passed` or `failed`.
4. Choose an **Action**:
   * **Run features (a suite)** — set the site URL, the features to include, and a configuration.
   * **Run a load test** — pick a load-test feature and an optional site URL.
   * **Run AI assistant** — give the assistant a prompt to run headlessly, with an optional site URL and email for the report.
5. Make sure **Enabled** is on, then **Save**.

## Manage Automations

| Control            | What it does                                                                                         |
| ------------------ | ---------------------------------------------------------------------------------------------------- |
| Enabled toggle     | Pauses or resumes the automation without deleting it. Disabled automations keep their configuration. |
| Run now            | Dispatches the automation immediately — useful to verify settings before trusting the schedule.      |
| Last run indicator | Each list entry shows when the automation last dispatched.                                           |

## Good Defaults

* A nightly full-suite regression at a quiet hour catches drift without slowing anyone down.
* A regression suite that runs **when a smoke run passes** chains coverage without manual hand-off.
* Point scheduled automations at a stable environment — a staging URL that resets overnight will fail for reasons unrelated to your app.

## Related Help

* [Schedule runs](/run-tests/schedule-runs.md)
* [Run a group](/run-tests/run-group.md)
* [Choose browser, viewport, and configuration](/run-tests/browser-viewport-configuration.md)


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.testvibe.com/run-tests/automations.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.