> For the complete documentation index, see [llms.txt](https://docs.datalogz.io/guides/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.datalogz.io/guides/workflows.md). # Workflows Workflows turn a monitor alert into a one-click action. Instead of manually deciding what to do each time an alert fires, you configure a workflow once and it appears as a button on every matching alert, ready for anyone with access to run it. Each workflow runs one or more [**plugins**](/guides/workflows/setting-up-a-workflow.md#plugins), which are the individual actions the workflow takes (for example, sending a notification email). In this release, workflows are triggered manually from monitor alerts, and the available plugin is [**Send Email**](/guides/workflows/setting-up-a-workflow.md#send-email). ## How Notification Workflows Fit into Control Tower Notification workflows sit on top of: * **Inventory:** where assets, ownership, and health are defined * **Monitors & Alerts:** where issues are detected (unused, orphaned, failed refresh, etc.) They act as the execution layer that ensures these signals lead to action. --- # 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.datalogz.io/guides/workflows.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.