> 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.md).

# Custom Action

Avo Assure provides an additional option to its users to craft their own keyword or action in a Test Step when automating an application. This is custom actions and are user-defined steps that expand Avo Assure’s automation capabilities. They are ideal for handling necessary controls or workflows beyond the built-in actions in Avo Assure. Additionally, these actions once created, can be shared across all users within the same Avo Assure instance.

### This document includes:

[**Prerequisites**](/avo-assure/actions/custom-action/prerequisite.md)

Prerequisites for creating Custom Action in Avo Assure

[**Significance & Key Benefits**](/avo-assure/actions/custom-action/significance-and-key-benefits.md)

Significance & Key Benefits of creating Custom Action in Avo Assure

[**Types**](/avo-assure/actions/custom-action/types-of-custom-action.md)

Types of Custom Action in Avo Assure

[**Create and Edit Custom Action**](/avo-assure/actions/custom-action/create-edit-and-delete-custom-action.md)

Steps to create and Edit Custom Action in Avo Assure

[**Examples**](/avo-assure/actions/custom-action/examples-of-custom-action.md)

Examples for Custom Action

[**Best Practices**](/avo-assure/actions/custom-action/best-practices.md)

Best Practices to create Custom Actions in Avo Assure


---

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