> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/products/integrations/video-management-systems/milestone/milestone-how-to-trigger-a-specific-milestone-action-using-ascii-text.md).

# Trigger a specific Milestone action using ASCII text

Configure ASCII text or CRPS to trigger a Milestone action for an individual item.

The Milestone MIPs Plugin v1.0.134 can be extended for additional event types, but that only triggers events **by type**. All non-door events appear in Milestone against the server item, and you can trigger on all open and off events but **not** for one specific input or output. To send a message for an **individual item**, use the **ASCII text plugin** or **CRPS** instead.

### Setup

1. In Command Centre, configure a unique string to send, most efficiently via an **\[ES] event source** dynamic name in an Action Plan. Set the external-system IP address to the **Milestone server**.
2. In Milestone **Tools → Options**, enable the **Generic Events data source**, and set its IP to the source of the message (for example the middleware PC).
3. Create a **Generic Event Rule** whose expression matches the string sent from Command Centre (for example "Input 1"). Use one rule per input or unique string, or use regular expressions.
4. Create a rule to trigger the Milestone action, including a **Create Log entry** for audit.


---

# 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://help.security.gallagher.com/knowledge-hub/products/integrations/video-management-systems/milestone/milestone-how-to-trigger-a-specific-milestone-action-using-ascii-text.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.