> For the complete documentation index, see [llms.txt](https://docs.akto.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.akto.io/api-protection/how-to/create-internal-workflow-item.md).

# Create Internal Workflow Item

## **Overview**

When you review a threat activity in Akto, you may need to involve internal teams for deeper investigation, tracking, or coordinated remediation. You can create workflow items directly from the threat activity details, including Jira tickets or internal work items, ensuring smooth cross-team collaboration.

## **Create Jira Ticket**

### **Prerequisites**

* Before creating Jira tickets from Akto, ensure that your Jira account is integrated with Akto.
* If not yet configured, complete the setup here: [Jira](/integrations/jira.md)

### Steps

{% stepper %}
{% step %}
Navigate to **Threat Activity** under **API Threat Detection**.
{% endstep %}

{% step %}
Open the **activity details** for the threat event you want to send to Jira.
{% endstep %}

{% step %}
On the right panel, select **Create Jira Ticket**.

<figure><img src="/files/hhs8Q5nsxT5evNp3xJF6" alt="" width="563"><figcaption></figcaption></figure>
{% endstep %}

{% step %}
In the dialog box, choose the **Jira project** and **issue type** from the dropdown options.

<figure><img src="/files/NUPEpsoyq26vGbaS29ua" alt="" width="563"><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Click **Create Ticket** and Akto will automatically generate the Jira ticket with the selected configuration.
{% endstep %}
{% endstepper %}

### How the Jira Ticket Appears

After creation, you will see a confirmation summary in Akto. Below is an example of how the ticket typically appears:

<figure><img src="/files/E8aui4N9CkJUVMY1ZOzM" alt="" width="540"><figcaption></figcaption></figure>

## **Create Work Item**

If your team uses internal workflows within Akto, you can log and assign tasks using **Work Items**.

### **Prerequisite**

Before creating Jira tickets from Akto, ensure that your Azure DevOps Board is integrated with Akto. Follow for [**Integrations Setup**](/integrations/azure-devops-boards.md)

### **Steps**

{% stepper %}
{% step %}
Open **Threat Activity** under **API Threat Detection**.
{% endstep %}

{% step %}
Select the threat activity that requires internal follow-up.
{% endstep %}

{% step %}
Click **Create Work Item** from the action panel.

<figure><img src="/files/sYAwtyFEtLczEplsxi76" alt="" width="563"><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Choose details such as title, description, severity, assignee, or notes for internal tracking.
{% endstep %}

{% step %}
Save the work item.
{% endstep %}
{% endstepper %}


---

# 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.akto.io/api-protection/how-to/create-internal-workflow-item.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.