> For the complete documentation index, see [llms.txt](https://docs.yellowant.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.yellowant.com/workflows/command-workflows/building-command-workflows/trigger.md).
# Trigger
A trigger for a command workflow is a command that triggers actions across various applications. The initiation point is when the user executes that command in the chat window or the YellowAnt native console. This means the workflow carries out the entire chain of events only if this command is executed and in no other circumstances. When you start building a workflow, you will be asked to create a command or it gets created with a default name.
Here we see, the default command name is: my-custom-workflow-name\
If you create another one with default name, it just gets appended by a number: my-custom-workflow-name-2
\
Here we see, the user command name is: startmyday You can also see the collection is: demo-collection
---
# 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.yellowant.com/workflows/command-workflows/building-command-workflows/trigger.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.