> For the complete documentation index, see [llms.txt](https://www.opal-rt.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.opal-rt.com/docs/rt-lab/automation-api-and-scripting/introduction-to-automation.md).

# Introduction to Automation

## Overview

Automation through scripting empowers users to:

* Automate repetitive and time-consuming tasks
* Create repeatable and reliable test scripts
* Accelerate validation and testing processes

The **RT-LAB API (Application Programming Interface)** is a set of functions that allows external programs to interact with RT-LAB. All functions available through the user interface can also be accessed via the API, including:

* Build, load, execute, and reset operations
* Reading and writing parameters
* Reading and writing signals
* And more

The API is available in several programming languages such as C code, Python, LabVIEW, Java and testStand. Because it is implemented in C, it can be used with any language that supports C function calls, enabling broad interoperability with the RT-LAB API. We recommend to use Python.


---

# 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://www.opal-rt.com/docs/rt-lab/automation-api-and-scripting/introduction-to-automation.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.
