# Automated Workflows

OES allows you to automate application delivery workflows with easy-to-create pipelines. OES offers templatized pipeline-as-code to enhance re-usability and provide the ability to insert fine-grain policy within the pipeline, with real-time visibility and diagnostics during the pipeline execution. 

1. **Easy pipeline creation:** DevOps engineers can simplify delivery configuration with OES pipeline-as-code, and manage versioning and automated updates of pipeline changes. 

   To know more about how to create a pipeline, refer [**here**](https://docs.opsmx.com/release-history/previous-releases/isd-4.0/knowledgebase/manage-pipelines/create-a-pipeline).
2. **Manage 1000’s of pipeline**: You can manage continuous delivery OES pipelines with the ease of using your management tools such as power UI, wizards, or JSON API. 

   To know more about managing a pipeline, refer [**here**](https://docs.opsmx.com/release-history/previous-releases/isd-4.0/knowledgebase/manage-pipelines).
3. **Embed Policies**: OES pipelines provide flexibility to enforce static and dynamic policies so that compliance managers can guarantee adherence to SDLC compliance. 

   To know more about how to create a policy, refer [**here**](https://docs.opsmx.com/user-guide/policy/create-policy).
4. **Pipeline Visibility**: OES pipelines allow you to gain visibility from code check-in to test automation to approval to production deployment through integration with JIRA, Jenkins, ServiceNow, AppDynamics, and other CD and APM tools. To know more about available integrations, refer [**here**](https://docs.opsmx.com/user-guide/data-sources).
5. **Notifications**: Connect with collaboration tools of your choice (Git, GitLab, JIRA, Jenkins, ServiceNow, Slack, Hipchat) right away and get notified about deployment status, policy violations, etc. To know more about available integrations, refer [**here**](https://docs.opsmx.com/user-guide/data-sources).


---

# Agent Instructions: 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:

```
GET https://docs.opsmx.com/opsmx-1/opsmx-context-engine/opsmx-intelligent-software-delivery-isd-platform-spinnaker/orchestration-module-opsmx-enterprise-for-spinnaker-oes/oes-features/automated-workflows.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.