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

# Secrets

Whenever you want to reference an API key or a secret in the Studio, you can safely add them to your workspace and make them available in the Studio in a safe manner.

In order to add a new secret, navigate to Settings > Secrets and click on "Create Secret".

<figure><img src="/files/gAQAthwwVRwPpz1OI8SH" alt=""><figcaption></figcaption></figure>

Once added, you will be able to select them in the building by using this syntax:

```
_secrets["my_secret_name"]
```

<figure><img src="/files/JEc0LpnTHAkcwOne62hH" alt=""><figcaption></figcaption></figure>

As an example, if you add a secret named "MY\_SECRET" then you can access it in the builder as:

```
_secrets["MY_SECRET"]
```

For LLM credentials and other third-party integrations, AirOps usually has some native authentications, so before adding a custom secret, ensure that it is not listed in "Settings > Integrations" or "Settings > API providers".

If the integration is already authenticated in **Settings > Integrations**, you can expose its credentials to workflows directly without duplicating them as a secret. See [Integration Authentications](/your-workspace/authentications.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:

```
GET https://docs.airops.com/your-workspace/secrets.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
