> For the complete documentation index, see [llms.txt](https://docs.valohai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.valohai.com/automation-overview.md). # Automation Valohai provides multiple automation mechanisms to help you build efficient, event-driven ML workflows. Whether you need to trigger executions on a schedule, respond to external events, or integrate with your existing CI/CD pipelines, Valohai offers flexible options through triggers, webhooks, and REST APIs. You can for example: * Schedule executions to run at specific times or intervals * Trigger workflows automatically when certain conditions are met * Respond to external events from other systems * Programmatically control all aspects of your ML operations ### Next Steps * [Use triggers](/automation-overview/triggers.md) to start workloads * [Send notifications](/automation-overview/outgoing-webhooks.md) automatically to external services * [Use REST APIs](https://github.com/valohai/dokuhai/tree/main/docs/automation-overview/broken-reference/README.md) to manage workloads --- # 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.valohai.com/automation-overview.md?ask=&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.