> For the complete documentation index, see [llms.txt](https://docs.brahma.fi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.brahma.fi/brahma-accounts/strategies-and-agents/automation-and-agents.md).
# Automation & Agents
> Automations are tailored workflows with transactions programmed to execute when certain triggers (conditions) are met. Main Brahma account users authorise these automations to manage and execute designated actions on selected protocols, using the assets provided.
Brahma Automations allow users to automate future execution from their Brahma account with a single signature, significantly reducing time and overhead for position management and coordination. For example, users can set up DCA or TWAP automations to schedule regular purchases or sales of their assets within the Brahma account dashboard.
Examples include:
1. Automated exit
2. a. Trigger variable: asset price, pool liquidity, etc.
b. Bundle: withdraw from position (close position), swap to x token
3. Capital efficient (Buy the dip while farming) Withdraw USDC from a farming position and submit swap order to buy $ETH
4. Trigger variable: $ETHUSD Price
5. Bundle: Withdraw (or unstake + withdraw) + swap
To access Brahma Automations, users have to enable the Brahma Executor Module.
---
# 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.brahma.fi/brahma-accounts/strategies-and-agents/automation-and-agents.md?ask=&goal=
```
`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.