> For the complete documentation index, see [llms.txt](https://docs.docontrol.io/docontrol-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docontrol.io/docontrol-user-guide/workflows/workflow-events.md). # Workflow events Workflows is an event-driven policy engine, triggered by various types of event, such as SaaS app events and DoControl events and alerts. DoControl supports hundred of types of propagated raw events from your integrated SaaS apps. ### Enriched event data in workflow queries SaaS app events sometimes lack important metadata. DoControl pre-processes the SaaS app raw events on-the-fly and enriches them with essential metadata fields. The additional metadata fields give you more control over trigger execution to create advanced workflows. Examples of additional metadata fields: Folder parent ID, document full URL in Google, calculated targets, calculated asset IDs. The **Query event fields** window contains details from the event in JSONata, including the additional metadata fields. You can use one of the macros from the list appearing at the top of the query page. ![Query event macros can be edited with a single click](https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2FIPoF0rjJ19UAPeNDAWcg%2Fimage.png?alt=media\&token=988838c6-09fa-47bb-81da-a2c9c3374ca1) --- # 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.docontrol.io/docontrol-user-guide/workflows/workflow-events.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.