> For the complete documentation index, see [llms.txt](https://docs.avoautomation.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avoautomation.com/avo-assure/actions/custom-action/types-of-custom-action.md).

# Types of Custom Action

Avo Assure supports majorly two Custom Action types to fit your automation needs:

1. **Generic (not tied to UI elements)**

Define actions under **@Generic** to perform broad operations like fetching file paths, altering environment variables, or handling data—capable of being used anywhere in the test.

{% hint style="warning" %}
**Note:** *Custom Actions for @Generic Element can be written using both, JavaScript and Python.*
{% endhint %}

2. **Element-specific**

* **JavaScript-driven Custom Actions**

Built for dynamic interactions: you select an element from the Element Repository, then write JavaScript that manipulates or validates that selection— e.g., custom DOM logic in MS Dynamics.

* **Python-based Custom Actions**

Ideal for backend or environment operations such as calling os.environ.get("TEMP") to fetch runtime system details. These run outside the browser context and retrieve data based on provided input parameters.

### Input Syntax Guidelines

When working with Custom Actions in Avo Assure, especially those written using Python or\
JavaScript, it is critical to understand how to correctly define and pass input values. These\
values can be **static**, **dynamic**, or **derived from previous steps**.


---

# 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.avoautomation.com/avo-assure/actions/custom-action/types-of-custom-action.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.