> For the complete documentation index, see [llms.txt](https://omniminds-ai.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://omniminds-ai.gitbook.io/whitepaper/9.-use-cases-and-applications/enterprise-workflow-automation.md). # Enterprise Workflow Automation Many enterprises still rely on human staff to perform routine digital tasks, such as data entry, report generation, form submissions, and dashboard operations, due to fragile or unavailable integrations. However, Omniminds solves this by allowing humans to train agents in the Dojo to mimic staff workflows precisely, without requiring backend access. Arena requests allow non-technical teams to specify automation needs, while LaunchBay agents can be deployed on-demand without IT involvement. With this, agents can upload invoices to ERP systems, generate weekly analytics reports from multiple sources, and manage CRM workflows (e.g., lead input, tagging, follow-ups) --- # 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://omniminds-ai.gitbook.io/whitepaper/9.-use-cases-and-applications/enterprise-workflow-automation.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.