> For the complete documentation index, see [llms.txt](https://knowledge.magicworksitsolutions.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.magicworksitsolutions.com/knowledge/ai-automation/workflow-selection.md). # Selecting workflows for automation How to select business workflows that are suitable for AI automation. Before choosing a model or platform, score the workflow itself. Useful questions include: * How frequently does the task occur? * Is the input digital and accessible? * Can output quality be evaluated? * What happens when the system is wrong? * Are exceptions common or rare? * Is there a clear human owner? * Can the process be measured before and after automation? High-volume but low-consequence workflows can be good early candidates. High-risk workflows may still benefit from AI, but usually require tighter controls, narrower scope and stronger human review. --- # 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://knowledge.magicworksitsolutions.com/knowledge/ai-automation/workflow-selection.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.