# Actions

<figure><img src="/files/Tux5DrHMP6wkxzEuUqph" alt=""><figcaption></figcaption></figure>

## Overview

*Actions* enable you to build your own *custom workflows* into the AttackForge application user interface, and trigger those workflows with a button click.

You can create Actions to *help you*:

* **Build custom workflows for your teams**
* **Trigger a process automation**
* **Launch an integration with an external system**

Examples of Actions could include:

* Request a QA review / Approve a QA review
* Launch scans within your security tooling
* Create bulk actions which do not currently exist
* Trigger a custom vulnerability risk acceptance workflow
* Enable low-privileged users to perform isolated privileged tasks
* Export data on-demand
* Run custom reports and email the results
* Anything you can imagine :smile:

<figure><img src="/files/5TMH9AztFwHLSSLgFh5W" alt=""><figcaption></figcaption></figure>

> **IMPORTANT**: Actions are only available if you have the [Flows](/attackforge-enterprise/modules/flows.md) module enabled

## How Actions Work

Actions are located in your existing menus, alongside other existing system actions.

<figure><img src="/files/hzEjQKy0DUAzu929HnyU" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/5TMH9AztFwHLSSLgFh5W" alt=""><figcaption></figcaption></figure>

Actions are triggered with a *button click*.

When triggering an Action, a confirmation dialogue will appear:

<figure><img src="/files/ac3spiF6II8U7GOvKxV0" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/s9W1LPFm2GMIHrCyUaaV" alt=""><figcaption></figcaption></figure>

This dialogue provides you with additional information on the Action, depending on your configured access.

After you click on `Run` - the Action will be triggered, and it will show in your `Action Runs Manager`. From here, you can monitor the status of your triggered Action.

<figure><img src="/files/y9cZSFvJnDCbxEZlfaxL" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/W1hYFp6SqdK8Zj9kqA7g" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/iZI3mQE0xDuYcW4lShjC" alt=""><figcaption></figcaption></figure>

You can click on the status to see more information:

<figure><img src="/files/YqTUPDuYt0PNGKNTlBfy" alt=""><figcaption></figcaption></figure>

Actions are powered by [Flows](/attackforge-enterprise/modules/flows.md). Flows is AttackForge's *powerful workflow automation engine*, allowing users to create completely custom workflows, automations and integrations.&#x20;

Flows is powered by [AFScript](/attackforge-enterprise/afscript.md) - AttackForge's *easy-to-use scripting language*, creating infinite possibilities with what your Flows can actually do.

Actions can be linked to multiple Flows - meaning many workflows can be triggered from one single Action.

## Supported Entities

Actions can be created and accessed within any of the following entities:

1. [Project Request(s)](https://support.attackforge.com/attackforge-enterprise/getting-started/requesting-a-project)
2. [Project(s)](https://support.attackforge.com/attackforge-enterprise/getting-started/creating-and-managing-projects)
3. [Project Vulnerability(s)](https://support.attackforge.com/attackforge-enterprise/getting-started/creating-vulnerabilities)
4. [Project Test Case(s)](https://support.attackforge.com/attackforge-enterprise/getting-started/test-cases)
5. [Portfolio(s)](https://support.attackforge.com/attackforge-enterprise/modules/portfolios)
6. [Portfolio Stream](https://support.attackforge.com/attackforge-enterprise/modules/portfolios)
7. [Group(s)](https://support.attackforge.com/attackforge-enterprise/modules/groups)
8. [Asset(s)](https://support.attackforge.com/attackforge-enterprise/modules/assets)
9. [Writeup(s)](https://support.attackforge.com/attackforge-enterprise/modules/vulnerability-library)
10. [User(s)](https://support.attackforge.com/attackforge-enterprise/modules/users)
11. [Application](#application-actions)

## Building Actions

To start building an Action, click on the `Actions button` in any of the application menus:

<div align="center"><figure><img src="/files/hzEjQKy0DUAzu929HnyU" alt=""><figcaption></figcaption></figure></div>

Then click on the `+` button:

<div align="center"><figure><img src="/files/S5bjAvVVRdRrejmBiXga" alt=""><figcaption></figcaption></figure></div>

Alternatively, you can click on the `Application Actions` menu from the main navigation bar, then click on the `Actions button`:

<figure><img src="/files/KoiiTBSlfI9VBSGHrywg" alt=""><figcaption></figcaption></figure>

Then click on the `New` button:

<figure><img src="/files/j5Gv22khIMPcXlgkZovH" alt=""><figcaption></figcaption></figure>

### Configuring the Action

1. Enter a name for your Action.
2. Select the entities where you want your Action to show.

<figure><img src="/files/lMlLi82jD2H9Rg3c3Ssy" alt=""><figcaption></figcaption></figure>

3. Link the related [Action Event Flows](https://support.attackforge.com/attackforge-enterprise/modules/flows#action-events) to your Action. There is *no limit* on how many Action Event Flows can be linked to your Action.

<figure><img src="/files/koorWzYUAW46MguidNjT" alt=""><figcaption></figcaption></figure>

4. Add an optional **Readme** if required.

<figure><img src="/files/ovcGo1r9EvAmSHQbL2iu" alt=""><figcaption></figcaption></figure>

5. Review the Action configuration and click `Create`.

<figure><img src="/files/YLNoHyAkmT75tXxud605" alt=""><figcaption></figcaption></figure>

If you are seeing the warning `Flow is disabled` - you will need to *enable the Flow* from the [Flows](/attackforge-enterprise/modules/flows.md) module.

<figure><img src="/files/BmPhadESQnT0iEsymrTH" alt=""><figcaption></figcaption></figure>

If you are seeing the warning `Missing access to trigger action flows` - you will need to assign yourself with either `Run` or `Create` access to [Action Triggers](https://support.attackforge.com/attackforge-enterprise/modules/flows#getting-access-to-flows).

<figure><img src="/files/8krGRmLAFIgCHtXfl6VL" alt=""><figcaption></figcaption></figure>

## Triggering Actions

Wherever you see an `Actions button` within the application user interface - you can click it to access existing Actions which you can trigger.

<figure><img src="/files/kQwhJS9nMVy3zdMrmzf4" alt=""><figcaption></figcaption></figure>

When you click on an Action, a confirmation dialogue box will open. You can click `Run` to trigger the Action.

<figure><img src="/files/ac3spiF6II8U7GOvKxV0" alt=""><figcaption></figcaption></figure>

You can click on `Readme` to access more information on this Action.

<figure><img src="/files/s9W1LPFm2GMIHrCyUaaV" alt=""><figcaption></figcaption></figure>

If you have permission to view the linked Flow, you can click on the button to access it:

<figure><img src="/files/J7u4Z7WHv6jIffzPeHkZ" alt=""><figcaption></figcaption></figure>

After you click on `Run` - the Action will show in your `Action Runs Manager`. From here, you can monitor the status of your triggered Action.

<figure><img src="/files/y9cZSFvJnDCbxEZlfaxL" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/W1hYFp6SqdK8Zj9kqA7g" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/iZI3mQE0xDuYcW4lShjC" alt=""><figcaption></figcaption></figure>

You can click on the status to see more information:

<figure><img src="/files/YqTUPDuYt0PNGKNTlBfy" alt=""><figcaption></figcaption></figure>

If you have permission to view [Flow Run Logs](https://support.attackforge.com/attackforge-enterprise/modules/flows#run-logs) - you can click the button to see the detailed information for what each Flow did:

<figure><img src="/files/dyBknqnsmNCjUcat1MZB" alt=""><figcaption></figcaption></figure>

### Status Check Issues

If a status check returns an issue - you will *not be able to trigger the Action*.

If you are seeing the warning `Flow is disabled` - you will need to *enable the Flow* from the [Flows](/attackforge-enterprise/modules/flows.md) module.

<figure><img src="/files/STb3YWVBls6Yzsc6MRt2" alt=""><figcaption></figcaption></figure>

If you are seeing the warning `Missing access to trigger action flows` - you will need to assign yourself with either `Run` or `Create` access to [Action Triggers](https://support.attackforge.com/attackforge-enterprise/modules/flows#getting-access-to-flows).

<figure><img src="/files/2S0yekKuStJ6SG02kb11" alt=""><figcaption></figcaption></figure>

## Viewing All Actions

You can view all of your Actions by clicking on the `Actions button` from the main navigation menu, then again on the `Actions button:`

<figure><img src="/files/f2CF79kKr9kuvRd5xY3f" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/UGKnqVHHK1Te7fjxPBkJ" alt=""><figcaption></figcaption></figure>

You can click on an Action to view the [Action Runs](#viewing-action-runs) related to the Action. You can also view the `Readme` and edit the Action from here.

<figure><img src="/files/HY07n9uHS4Q57Y3P4e82" alt=""><figcaption></figcaption></figure>

### Editing Actions

When viewing an Action, click on the Edit button to make updates:

<figure><img src="/files/h94cbD2pxJwL4IQOj37U" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/ZtqTNbR09Uk27zdGM7Jp" alt=""><figcaption></figcaption></figure>

You can also access the Edit Action page by clicking on the `Settings` button in the Actions menu, then clicking on the `Edit` button:

<figure><img src="/files/NXeJvrVUzMK752YO5y2l" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/F0jTgsfDMdmZMkjgjPj4" alt=""><figcaption></figcaption></figure>

### Deleting Actions

From the All Actions page, use the table row menu to select the Action you want to delete and then click on `Delete`.

<figure><img src="/files/E8bPgb6DfCMwm9gDknlk" alt=""><figcaption></figcaption></figure>

You can also Delete Actions by clicking on the `Settings` button in the Actions menu, then clicking on the `Delete` button:

<figure><img src="/files/NXeJvrVUzMK752YO5y2l" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/qehq417A7joCXsr5zMOZ" alt=""><figcaption></figcaption></figure>

### Viewing Action Runs

You can switch to the Action Runs menu from the All Actions page:

<figure><img src="/files/x2ACDcx3wy7yXLnXsVCs" alt=""><figcaption></figcaption></figure>

You can also view all Action Runs by clicking on an Action from the All Actions page:

<figure><img src="/files/V8hnRxOooLLFqBppnQS1" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/HY07n9uHS4Q57Y3P4e82" alt=""><figcaption></figcaption></figure>

When you click on an Action Run - a dialogue will show which Flows were triggered and their status. If you have permission - you can click on the button next to the status to view the [Flow Run Logs](https://support.attackforge.com/attackforge-enterprise/modules/flows#run-logs).

<figure><img src="/files/Lg3PrMpYqk0JfA8mKP3a" alt=""><figcaption></figcaption></figure>

## Application Actions

Application Actions are accessed by clicking on the `Actions button` from the main navigation menu:

<figure><img src="/files/wUIYDPwap9BMvcDE4ulS" alt=""><figcaption></figcaption></figure>

Application Actions relate to the application itself, they are not tied to any particular entity such as a Project, Vulnerability or Asset.

You can use Application Actions *at any time* - regardless of what access you have to other data and workflows in AttackForge. This makes them ideal for have personal workflows, or delegating privileged workflows to lower-privileged users.

## Sharing Actions

> **Coming soon!**

## Custom Forms on Actions

> **Coming soon!**

## Reordering Actions

You can re-order your custom Actions by clicking on the `Settings` button in the Actions menu:

<figure><img src="/files/NXeJvrVUzMK752YO5y2l" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/SXtb3P7ZGl8k31KmNIwd" alt=""><figcaption></figcaption></figure>

You can drag and drop each row to the order you desire; or use the menu to select the desired re-ordering option:

<figure><img src="/files/Mo6IYLeolMdOQxOFI03G" alt=""><figcaption></figcaption></figure>


---

# 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://support.attackforge.com/attackforge-enterprise/actions.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.