> 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/creating-a-workflow/workflow-actions.md).

# Workflow Actions

Actions define what happens when a workflow is triggered and all conditions are met. Actions can range from sending a notification, opening a ticket, to setting an SLA. Actions are how workflows translate security intelligence into operational response.

to check the AI

| **Action**                 | **Category**   | **Description (if known)**                  |
| -------------------------- | -------------- | ------------------------------------------- |
| Azure Boards               | Ticketing      | Create or update work items in Azure Boards |
| Asana                      | Ticketing      | Create tasks in Asana                       |
| ServiceNow                 | Ticketing      | Open incidents or tickets in ServiceNow     |
| Monday                     | Ticketing      | Create/update items in Monday.com           |
| Github Issues              | Ticketing      | Open issues in GitHub repository            |
| Logz.io                    | SIEM & Logging | Send logs or alerts to Logz.io              |
| Splunk                     | SIEM & Logging | Send logs or events to Splunk               |
| Block Pipeline             | Pipeline       | Prevent pipeline execution                  |
| Alert Pipeline             | Pipeline       | Send alert within the pipeline process      |
| Set SLA                    | SLA            | Define a custom SLA for the issue           |
| Reset Severity             |                | Reset the severity level to default         |
| Increase/Decrease Severity | SLA            | Adjust severity level based on logic        |
| Slack                      | Notification   | Send notification to Slack channel          |
| Email                      | Notification   | Send email notification                     |
| Teams                      | Notification   | Send message to Microsoft Teams             |
| Webhook                    | Notification   | Trigger custom webhook                      |
| Zapier                     | Notification   | Trigger automated workflows via Zapier      |
| Open PR                    | Remediation    | Open a pull/merge request with the fix      |
| Jira                       | Ticketing      | Open ticket in Jira                         |
| Jira Comment               | Ticketing      | Add comment to an existing Jira ticket      |
| Set Owner                  | Ownership      | Assign issue owner                          |


---

# 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.ox.security/automate-with-ox-workflows/creating-a-workflow/workflow-actions.md?ask=<question>&goal=<user_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.