> For the complete documentation index, see [llms.txt](https://docs.ox.security/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ox.security/automate-with-ox-workflows/ox-automations.md).

# About OX Workflows

When suspicious security activity is identified in your system, you can define automations that block the activity or notify the relevant team members.

Automations ensure security events are handled immediately and consistently, without relying on manual intervention. In the OX platform, automations are created through workflows.

Automations are flexible and fully customizable. You can configure simple workflows, such as sending an alert for a specific type of issue, or build complex logic that combines multiple conditions and actions.

This allows you to tailor automated responses to your organization’s needs, from handling isolated exceptions to managing alerts across hundreds of applications.

Automations help you:

* Enforce security and compliance policies in real time.
* Reduce delays by eliminating repetitive manual responses.
* Ensure that the right people are notified at the right time.
* Prioritize issues based on business impact and context.

Common use cases:

* Send alerts for critical vulnerabilities to Slack, Teams, or email.
* Open tickets automatically in Jira, Azure DevOps, or other trackers.
* Adjust the severity of findings based on known exceptions or business priority.
* Trigger webhooks to integrate with internal systems or external automation platforms.


---

# 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.ox.security/automate-with-ox-workflows/ox-automations.md?ask=<question>&goal=<endgoal>
```

`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.