> For the complete documentation index, see [llms.txt](https://docs.labii.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.labii.com/widgets/section-widgets/productivity/automation.md). # Automation ## Overview The Automation category provides record-level widgets that help users trigger predefined workflow logic directly inside Labii ELN and LIMS records. These widgets are designed for operational scenarios where a user needs to launch approved automation in context rather than manually performing every downstream step. Whether the goal is creating derivative records, starting a standardized processing routine, or initiating a repeatable system action from a sample or request, these tools keep automation close to the record where the work begins. Together, they reduce context switching and make routine process execution faster, more consistent, and easier to monitor. ## Widgets * [Workflows](/widgets/section-widgets/productivity/automation/workflows.md) - Launch predefined workflows and review execution logs --- # 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.labii.com/widgets/section-widgets/productivity/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.