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

# Automation Studio

![Automation Studio](https://1807546539-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhgHCHWL3861o2DBW53aA%2Fuploads%2Fxtvxz2FXxf5J7Y4Fp9W0%2Fve20261112v5-automation-studio.png?alt=media)

## Goal

Run playbooks against lab inventory (spine / leaf / border groups), including Guided Lab solution playbooks and scheduled runs.

## Open it

1. Open **Automation Studio** from the OS app launcher, or
2. From a lab, open the in-lab Automation panel locked to that lab

## What you get

| Surface           | Use it for                                                 |
| ----------------- | ---------------------------------------------------------- |
| **Playbook tree** | DC fabric starters, Guided\_Labs catalogs, your saved YAML |
| **Inventory**     | Auto groups from node names / roles                        |
| **Editor**        | Edit playbook body; secrets are redacted in run logs       |
| **Run**           | Apply / show / validate steps against matching hosts       |
| **Schedules**     | Cron-style enable/disable with last / next run stamps      |
| **Credentials**   | Named platform credentials for device access               |

## Recipe: run a fabric playbook

1. Select the lab
2. Open a playbook (for example `DC_Fabric/01_Deploy_Fabric.yml`)
3. Confirm inventory groups match your node names
4. Click **Run** / Play and watch the output dock
5. Fix failed hosts from the console or Config Studio, then re-run

Guided Labs can seed `Guided_Labs/...` playbooks (apply startup, validate, checkpoint checks). Prefer those when teaching a packaged scenario.

## Related

* Configuration Studio
* [Guided Labs](/labs/guided-labs.md)
* [Features](/getting-started/features.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 by asking a question.

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

```
GET https://docs.vex-nx.com/labs/automation-studio.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.