> 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/conditions-and-actions/overview.md). # Overview Conditions and Actions are used extensively in the appRules Integration & Automation Engine. Before continuing with the other sections, please review Conditions and Actions in the documentation for the [Platform Feature](/apprules-r-documentation/platform/platform-features.md)s. Examples of usage of Conditions and Actions in workflow activities include: * **EvaluateCondition** - Evaluates a single condition and makes the result available for use in further evaluations of conditions or workflow activities. * **EvaluateConditions** - Evaluates a group of conditions and performs a set of actions based on the result. * **PerformAction** - Performs the selected action. A value is returned if the action type is Action Field. * **PerformActions** - Performs a list of actions. Conditions can also be entered to indicate the specific actions in the list to be executed. * **Decision Tables** - The decision rows of decision tables are made up of the conditions to evaluate and the actions to execute if the Conditions evaluate to True. --- # 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/conditions-and-actions/overview.md?ask=&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.