> For the complete documentation index, see [llms.txt](https://docs.appstrategy.com/apprules-r-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appstrategy.com/apprules-r-documentation/platform-products/apprules-integration-and-automation-engine/business-rules/performing-actions.md).

# Performing Actions

## Performing Actions

The following activities are used for performing actions:

PerformAction

PerformActions

## PerformAction Activity

The PerformAction activity is used for performing any Action available in appRules.  

To configure a PerformAction activity, drag the PerformAction activity from the Base module of the toolbox on to the designer. Select the Action or configure a new one. Then save the workflow activity.

## PerformActions Activity

The PerformActions activity is used for performing a group of actions.  

To configure the PerformActions activity, drag the PerformActions activity from the "Business Rules" module of the toolbox on to the designer.  The following modal will be displayed:

To add Actions to the list of actions to be performed:

Enter the column values for each Action as follows:

<table><thead><tr><th width="262">Column</th><th>Description</th></tr></thead><tbody><tr><td>Condition</td><td>Select optional condition for executing the action</td></tr><tr><td>Action Default/True</td><td>Select the action to be executed if the condition is not specified or is True. This field is required.</td></tr><tr><td>Action False</td><td>Select optional action to be executed if the condition is specified and evaluates to False</td></tr><tr><td>Description</td><td>Enter the unique name for the action item. This field is required.</td></tr></tbody></table>

&#x20;


---

# 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.appstrategy.com/apprules-r-documentation/platform-products/apprules-integration-and-automation-engine/business-rules/performing-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.