> For the complete documentation index, see [llms.txt](https://docs.enate.net/enate-help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enate.net/enate-help/builder/builder-2021.1/case-configuration/adding-actions-to-a-case/adding-ad-hoc-actions.md).
# Adding Ad-hoc Actions
There are two ways to add ad-hoc Actions, depending upon whether the Action in question also appears as part of the standard Case flow:
## **Ad-hoc Actions which DO appear as part of the standard Case flow**
Simply tick the checkbox in the ‘Manual Creation’ column in the Action Info Grid.
Manually starting this type of ad-hoc action will then automatically launch Actions further downstream in the flow.
## **Ad-hoc Actions which DO NOT appear in the Case flow diagram**
Select the '+' icon in the top-right of the Action Info grid and select the type of ad-hoc Action from the Actions menu popup.
Once the Action is added, it shows up in the Action info tab.
Here it will be labelled as an ad-hoc Action. This ad hoc Action is not part of the workflow, but can be launched manually by a Case Owner, if required.
All the configuration settings for this type of ad hoc Actions are same as for every other Action, with the following exceptions:
* The Manual Creation checkbox is auto-ticked and can’t be disabled.
* To delete this Action, you have to do it directly in the grid
---
# 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.enate.net/enate-help/builder/builder-2021.1/case-configuration/adding-actions-to-a-case/adding-ad-hoc-actions.md?ask=&goal=
```
`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.