> For the complete documentation index, see [llms.txt](https://support.attackforge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.attackforge.com/app/automations-and-integrations/actions.md).

# Actions

## Overview

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2FEIIQzlNgbduSdF8SpzoS%2FActions.png?alt=media&amp;token=740a7b17-80b4-422a-a6b0-cb3b1af73662" alt=""><figcaption></figcaption></figure>

Actions add your own buttons to AttackForge. Each button runs a custom workflow, a process automation or an external integration. Users click it from the menus they already use, confirm, and AttackForge does the rest.

{% hint style="info" %}
**Important:** Actions require the [Flows](https://support.attackforge.com/app/automations-and-integrations/flows) module.
{% endhint %}

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2FfS5tdREATeQfqnId2kIt%2Factions-at-a-glance.svg?alt=media&amp;token=68b3f234-8426-42ec-9e1c-54d7bc186206" alt=""><figcaption></figcaption></figure>

For example, you can use Actions to:

| Use case                        | Example                                                                                                                                                                                                        |
| ------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Request and approve reviews** | Ask for, or approve, a QA review on a project                                                                                                                                                                  |
| **Launch scans**                | Start a scan on an asset, and import the results                                                                                                                                                               |
| **Make bulk changes**           | Update many vulnerabilities at once                                                                                                                                                                            |
| **Trigger risk acceptance**     | Start a risk-acceptance workflow on a vulnerability                                                                                                                                                            |
| **Delegate privileged tasks**   | Let lower-privileged users run a specific privileged task, in isolation                                                                                                                                        |
| **Export data**                 | Send project data to another system                                                                                                                                                                            |
| **Run and email reports**       | Generate a custom report and email it. See [Report Automation](https://support.attackforge.com/app/automations-and-integrations/report-automation).                                                            |
| **Run AI agents**               | Start an AI agent to enrich vulnerabilities, retest findings or write an executive summary. See [AI agentic workflows](https://support.attackforge.com/app/automations-and-integrations/ai-agentic-workflows). |

## How Actions work

1. **Actions live in menus you already use,** such as on a project or a vulnerability.
2. **A user clicks the Actions button,** then the Action they want.
3. **They confirm** in a dialogue, and fill in a form if the Action has one.
4. **The Action runs its Flows.** Actions are powered by [Flows](https://support.attackforge.com/app/automations-and-integrations/flows) and [AFScript](https://support.attackforge.com/app/automations-and-integrations/afscript). One Action can run several Flows.
5. **They check the result** in the Action Runs Manager, and click the status for details.

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2FMz0B98WVWmi1luaHa3ne%2FScreenshot%202026-11-11%20at%2011.48.57%E2%80%AFam.png?alt=media&amp;token=e95079e2-4aba-47d6-be6b-754f61c899d8" alt=""><figcaption></figcaption></figure>

## Key terms

| Term                   | Meaning                                                                                                              |
| ---------------------- | -------------------------------------------------------------------------------------------------------------------- |
| **Action**             | A button that runs one or more Action Event Flows                                                                    |
| **User Action**        | An Action a user sets up for themselves. Shown in blue.                                                              |
| **System Action**      | An Action an administrator sets up for Roles, Groups or Users. Shown in green. Users don't need to accept or add it. |
| **Application Action** | An Action in the main navigation, not tied to any record                                                             |
| **Action Owner**       | The user who created the Action                                                                                      |
| **Action Run**         | One run of an Action, and the Flows it triggered                                                                     |

## Why it matters

* **Automation where people work.** Users start workflows from the record they're looking at, without leaving AttackForge or learning a new tool.
* **Safe delegation.** Let people run a specific task without giving them broader access.
* **Consistent processes.** Everyone follows the same steps, with the same checks, every time.
* **Visible results.** Every run is tracked, so users and admins can see what happened.

## Who uses it

| Who                              | To                                                            |
| -------------------------------- | ------------------------------------------------------------- |
| **Administrators**               | Create System Actions for teams, and control who can run them |
| **Automation builders**          | Build the Flows behind Actions, and share them                |
| **Testers and project managers** | Run Actions on projects, vulnerabilities and test cases       |
| **Anyone**                       | Create User Actions for their own workflows                   |

## Where Actions appear

You can create and run Actions from these records:

| Record                  | Learn more                                                                                                          |
| ----------------------- | ------------------------------------------------------------------------------------------------------------------- |
| Project requests        | [Requesting a project](https://support.attackforge.com/attackforge-enterprise/getting-started/requesting-a-project) |
| Projects                | [Projects](https://support.attackforge.com/app/modules/projects)                                                    |
| Project vulnerabilities | [Vulnerabilities](https://support.attackforge.com/app/modules/vulnerabilities)                                      |
| Project test cases      | [Test cases](https://support.attackforge.com/attackforge-enterprise/getting-started/test-cases)                     |
| Portfolios              | [Portfolios](https://support.attackforge.com/app/modules/portfolios)                                                |
| Portfolio streams       | [Portfolios](https://support.attackforge.com/app/modules/portfolios)                                                |
| Groups                  | [Groups](https://support.attackforge.com/app/modules/groups)                                                        |
| Assets                  | [Assets](https://support.attackforge.com/app/modules/assets)                                                        |
| Writeups                | [Writeups](https://support.attackforge.com/app/modules/vulnerability-library)                                       |
| Users                   | [Users](https://support.attackforge.com/attackforge-enterprise/modules/users)                                       |
| The application         | See "Application Actions" below                                                                                     |

## User Actions and System Actions

|                                | User Actions                            | System Actions                                    |
| ------------------------------ | --------------------------------------- | ------------------------------------------------- |
| **Who creates them**           | Any user, for themselves                | Administrators                                    |
| **Who they're for**            | The creator, and anyone they share with | Roles, Groups or Users that administrators choose |
| **Placement in menus**         | Within "My Actions"                     | Same level as all other native system actions     |
| **Do users need to add them?** | Yes, from the Add Actions catalogue     | No. They don't need to be accepted or assigned.   |
| **Who can edit them**          | People with Edit access                 | Administrators, and people with Edit access       |

Administrators can switch an Action between System and User at any time. Administrators can view all User Actions, their runs and access controls, but can't edit those they don't have Edit access to.

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2Fo0KK0wPiDAXywQBTWv7p%2FScreenshot%202026-11-11%20at%2011.51.11%E2%80%AFam.png?alt=media&amp;token=6b2051f6-b1d2-4334-853f-9f9cac3e3f7c" alt=""><figcaption></figcaption></figure>

## Build an Action

### Before you start

* **Build the Flow first.** Create a Flow with an [Action Event trigger](https://support.attackforge.com/app/automations-and-integrations/flows), and enable it.
* **Check your access.** You need Run or Create access to Action triggers. See [Get access to Flows](https://support.attackforge.com/app/automations-and-integrations/flows).

### Open the Action builder

Open it in either of two ways:

* From a record: click **Actions**, then **Add Actions**.

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2FNOCeBS5czjkTGghSicpO%2FScreenshot%202026-11-11%20at%2011.55.10%E2%80%AFam.png?alt=media&amp;token=2797c413-146c-42a2-bcad-6f9f2bbd0b64" alt=""><figcaption></figcaption></figure>

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2FLzqy9nc8JQQzTjI5qCE1%2FScreenshot%202026-11-11%20at%2011.55.49%E2%80%AFam.png?alt=media&amp;token=4e120b6e-b755-44b9-bd93-36c97e235db8" alt=""><figcaption></figcaption></figure>

* From the main navigation: open **Application Actions**, click **Actions**, then **New**.

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2FCdaPMOz20jLh4ImO4LxV%2FScreenshot%202026-11-11%20at%2011.53.59%E2%80%AFam.png?alt=media&amp;token=9599bf20-3489-4e34-903f-079df4054d8f" alt=""><figcaption></figcaption></figure>

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2FNr80dUIqrl4nYiuxBDYB%2FScreenshot%202026-11-11%20at%2011.54.30%E2%80%AFam.png?alt=media&amp;token=59f7520e-6852-4522-938e-6bd245e667b2" alt=""><figcaption></figcaption></figure>

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2FrHt3Hw0EeJ4U86aZ4l9V%2FScreenshot%202026-11-11%20at%2011.54.40%E2%80%AFam.png?alt=media&amp;token=13d1533a-1871-446e-8699-5f6eb3751612" alt=""><figcaption></figcaption></figure>

### Configure the Action

1. **Name** the Action.
2. **Choose the records** it appears on.
3. **Link the Action Event Flows** to run. There's no limit.
4. **Add a readme (optional),** to explain what the Action does.
5. **Review the settings,** then click **Create**.

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2FlgF4EA0WEL4qvgS2SQhG%2FScreenshot%202026-11-11%20at%2011.57.19%E2%80%AFam.png?alt=media&amp;token=5786c0f5-244e-4fb2-9e65-120a6023fbeb" alt=""><figcaption></figcaption></figure>

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2F6eyG8MwZqAHKDqpUEs6p%2FScreenshot%202026-11-11%20at%2011.57.34%E2%80%AFam.png?alt=media&amp;token=6a48975e-16d2-419b-a314-ac8a9f639535" alt=""><figcaption></figcaption></figure>

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2FCYebDPAGG9rYv1uOWR0m%2FScreenshot%202026-11-11%20at%2011.58.34%E2%80%AFam.png?alt=media&amp;token=72bed93d-5f8e-4416-a9a3-54ac354de72f" alt=""><figcaption></figcaption></figure>

If a warning appears, see "Fix status-check problems" below.

### Add a form

Add a form to collect information when someone runs the Action, such as a reason, a date or a choice of report template.

1. Add custom sections and fields to the Action's form, then click **Save**.
2. When users run the Action, they fill in the form.
3. In the first action of your Flow, select the Action in the field at the top right. The form's answers are then available in `data.form`.

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2FhpQ9F5W4MUab93D74oiW%2FScreenshot%202026-11-11%20at%2012.00.20%E2%80%AFpm.png?alt=media&amp;token=f9c7f941-a705-4c48-bb24-90e00fbb5927" alt=""><figcaption></figcaption></figure>

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2F256D2iQVHi0gUF2fQgBk%2FScreenshot%202026-11-11%20at%2012.01.12%E2%80%AFpm.png?alt=media&amp;token=2ceb8c6e-c385-4cf6-8850-2006ab119021" alt=""><figcaption></figcaption></figure>

## Run an Action

1. Click the **Actions** button on a record, or in the main navigation.
2. Choose the Action.
3. In the dialogue, click **Readme** to learn more, or **Run** to start it.
4. The Action Runs Manager opens. Click the status for details.

If you have permission, you can also open the linked Flows and their Flow Run Logs.

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2FbHPf4xNbNrYeUQj2N4Hs%2FScreenshot%202026-11-11%20at%2012.02.59%E2%80%AFpm.png?alt=media&amp;token=4474f2ea-b119-4e5e-a530-74113fc22110" alt=""><figcaption></figcaption></figure>

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2FTg9OvG0RctFya47P854W%2FScreenshot%202026-11-11%20at%2012.04.16%E2%80%AFpm.png?alt=media&amp;token=5312c53e-aac4-4b82-beb0-ac242ed670ed" alt=""><figcaption></figcaption></figure>

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2FavEtxQwTCMvfhZl6jKwO%2FScreenshot%202026-11-11%20at%2012.05.13%E2%80%AFpm.png?alt=media&amp;token=79e991e7-70bd-4326-aa20-d609f0e7174a" alt=""><figcaption></figcaption></figure>

### Fix status-check problems

Before an Action runs, AttackForge checks its Flows. If a check fails, the Action can't run.

| Warning                                    | Cause                                    | Fix                                                              |
| ------------------------------------------ | ---------------------------------------- | ---------------------------------------------------------------- |
| **Flow is disabled**                       | A linked Flow is turned off              | Enable the Flow in the Flows module                              |
| **Missing access to trigger action flows** | You don't have access to Action triggers | Ask an administrator for Run or Create access to Action triggers |

## Application Actions

Application Actions are in the main navigation, under **Actions**. They aren't tied to any record, and anyone they're shared with can run them at any time, whatever their other access.

Use them for personal workflows, or to delegate privileged tasks to lower-privileged users.

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2FjgG1W5J5jJPX18Jiawtf%2FScreenshot%202026-11-11%20at%2012.08.01%E2%80%AFpm.png?alt=media&amp;token=c4e5fb43-2bbd-4f58-b06e-1666f9b857e7" alt=""><figcaption></figcaption></figure>

## Share Actions

### Action Owner

The user who creates an Action is its **Action Owner**. The owner can manage access and delete the Action.

{% hint style="info" %}
**Note:** Administrators have Action Owner privileges on all System Actions.
{% endhint %}

### Who can share with whom

| Who                | Can share              | With                                     |
| ------------------ | ---------------------- | ---------------------------------------- |
| **Administrators** | System Actions         | Roles, Groups or Users                   |
| **Administrators** | Their own User Actions | Roles, Groups or Users                   |
| **Other users**    | Their own User Actions | Groups they belong to, or Users by email |

### Access levels

| Level    | Can                                                               |
| -------- | ----------------------------------------------------------------- |
| **None** | Nothing. Use it to block a user. It applies when Override is Yes. |
| **View** | Run the Action                                                    |
| **Edit** | Run the Action, and edit its configuration                        |

**Override** (Users only): select Yes to make sure the user gets exactly the access you assign, even if a Role or Group gives them different access.

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2FpWXc64WQKvLMBHOZObre%2FScreenshot%202026-11-11%20at%2012.10.31%E2%80%AFpm.png?alt=media&amp;token=d1f6fed3-d56a-40f8-acf0-1c2de08e2c79" alt=""><figcaption></figcaption></figure>

### Create and share a System Action

1. Open **All Actions**, go to **System Actions**, and click **New**.
2. Fill in the details, then click **Create**.
3. Click **Share**, then **Add Access**.
4. Choose Roles, Groups or Users, the Access Level and, for Users, Override.
5. Click **Add**.

### Create and share a User Action

1. Open **All Actions**, go to **User Actions**, and click **New**.
2. Fill in the details, then click **Create**.
3. Click **Share**, then **Add Access**.
4. Choose Groups or Users. Other users enter an email, and can only choose their own Groups.
5. Choose the Access Level and Override, then click **Add**.
6. The people you shared with add the Action from the **Add Actions** catalogue.

### Check effective access

Action Owners can see who has access, from Roles, Groups and Users combined. Open the Action's settings and click **Effective Access**.

<figure><img src="https://372186556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8s1QY2Q6YTHB4a6DMu%2Fuploads%2Fm2kEKuKZ9T11qMVj6GjO%2FScreenshot%202026-11-11%20at%2012.14.03%E2%80%AFpm.png?alt=media&amp;token=0a838ece-8538-41ad-b63a-3bc554695495" alt=""><figcaption></figcaption></figure>

## Manage Actions

### View all Actions

Open the **Actions** menu to see all Actions. Click one to see its runs and readme, and to edit it.

### View Action runs

Switch to **Action Runs** from All Actions, or click an Action. Each run shows the Flows it triggered and their status. If you have permission, you can open the Flow Run Logs.

### Edit an Action

Open the Action and click **Edit**. Or, from **Add Actions**, select the Action, then click **Edit**.

### Reorder Actions

In the **Add Actions** menu, drag and drop Actions into the order you want. Or use the row menu to move an Action, or remove it from your menu.

### Delete an Action

In **All Actions**, open the row menu and click **Delete**.

### Transfer an Action

Only the Action Owner can transfer an Action.

1. Open the Action's settings, and click **Transfer**.
2. Administrators select a user. Other users enter an email.

System Actions can only be transferred to other administrators.

## Tips

* **Build and test the Flow first,** then add the Action. Use test contexts in Flows to try it with sample data.
* **Write a readme** for every Action, so people know what it does before they click Run.
* **Show Actions only where they're relevant,** by choosing the right records.
* **Use a form** to collect what the Flow needs, instead of hard-coding values.
* **Use System Actions for team processes,** so everyone has them without adding them.
* **Use Application Actions to delegate** a privileged task, without giving broader access.
* **Put the Actions people use most at the top,** by reordering the Add Actions menu.

## FAQ

**Do I need Flows to use Actions?** Yes. Actions run Action Event Flows.

**Can one Action run several Flows?** Yes, with no limit.

**Why can't I run an Action?** A linked Flow may be disabled, or you may not have access to Action triggers. See "Fix status-check problems".

**What's the difference between User and System Actions?** Users create User Actions for themselves and share them. Administrators create System Actions for Roles, Groups or Users, and people don't need to add them.

**How do I get information from the user who runs an Action?** Add a form. The answers are in `data.form` in your Flow.

**Where do I see if an Action worked?** In the Action Runs Manager. Click the status for details.

**Can I give someone an Action without giving them other access?** Yes. Application Actions run regardless of a user's other access.

**What happens to my Actions if I leave?** Transfer them to someone else. System Actions can only go to administrators.

## Related pages

* [Flows](https://support.attackforge.com/app/automations-and-integrations/flows)
* [AFScript](https://support.attackforge.com/app/automations-and-integrations/afscript)
* [AI agentic workflows](https://support.attackforge.com/app/automations-and-integrations/ai-agentic-workflows)
* [Report Automation](https://support.attackforge.com/app/automations-and-integrations/report-automation)
* [Groups](https://support.attackforge.com/app/modules/groups)
* [Concepts and Access](https://support.attackforge.com/app/getting-started/concepts-and-access)


---

# 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://support.attackforge.com/app/automations-and-integrations/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.
