> 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/event-workflows/building-event-workflows/using-action-outputs.md).

# Using Action Outputs

## Using Action Outputs

One important feature while creating workflows is to use action outputs. Action outputs are the outputs of a previously added action or coming right from the trigger event itself. In case of command workflows, if no parameter is passed then the action outputs of the trigger remains empty. You can access the action outputs by using "@" in any text field in the subsequent actions.

Example 1:

### In the trigger command, since no parameters are being passed, we don't see any outputs available in the next step. And using "@" gives us no options. 

![](/files/-LCCCRD16-Lx4GYoLo4b)

![](/files/-LC8ortTOSQHG7fk7bVU)

### In this case, a parameter was passed in the trigger command, so we see "build" appearing as a data option. 

![](/files/-LCCCU9Kh9ovrHEoP_Dr)

![](/files/-LCCCVJoyMMDYEpzigyS)


---

# 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/event-workflows/building-event-workflows/using-action-outputs.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.