> For the complete documentation index, see [llms.txt](https://docs.terrakube.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.terrakube.io/user-guide/workspaces/actions/built-in-actions.md).

# Built-in Actions

The following actions are added by default in Terrakube. However, not all actions are enabled by default. Please refer to the documentation below if you are interested in activating these actions.

### **General**

* [Open Documentation](/user-guide/workspaces/actions/built-in-actions/terrakube.open-documentation.md): Adds a button to quickly navigate to the Terraform registry documentation for a specific resource.
* [Resource Details](/user-guide/workspaces/actions/built-in-actions/terrakube.resource-details.md): Adds a new panel to visualize the state attributes and dependencies for a resource.

### **Azure**

* [Open in Azure Portal:](/user-guide/workspaces/actions/built-in-actions/terrakube.open-azure.md) Adds a button to quickly navigate to the resource in the Azure Portal.
* [Restart Azure VM](/user-guide/workspaces/actions/built-in-actions/restart-azure-vm.md): Adds a button to restart the Azure VM directly from the workspace overview.

### **Monitor**

* [Azure Monitor](/user-guide/workspaces/actions/built-in-actions/terrakube.azure-monitor.md): Adds a panel to visualize the metrics for the resource.

### **AI**

* [Open AI](/user-guide/workspaces/actions/built-in-actions/terrakube.open-ai.md): Adds a button to ask questions or get recommendations using OpenAI based on the workspace data.


---

# 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.terrakube.io/user-guide/workspaces/actions/built-in-actions.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.