> 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.&#x20;

![](/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.&#x20;

![](/files/-LCCCU9Kh9ovrHEoP_Dr)

![](/files/-LCCCVJoyMMDYEpzigyS)
