# Steps

Now you are able to add steps or tasks to your pipeline that will be executed and in which order.

There are 3 types of steps to choose from:

\- A starting one that has always been in place.

\- Function: it runs a function of choice.

\- Wait for the user: it awaits the user to choose from a set of given next steps.

\- Notify the user: it launches a notification message.

!\[A screenshot of a computer

Description automatically generated]\(<https://lh7-rt.googleusercontent.com/docsz/AD_4nXfmxPaQTBuVLoych2AM79uFQIEwMY6-aU8Fd-yvApRnAhhpHlIePPe_j4sH2Cqf-94h6eAaa4wA_-ZxOwk934e9lhYISXI5hMLuUo3JSna1_n28aJ-oI0zULi7w89_wzbY3rnyfYEK97RGG_D3G38Yvg62QykR9lo1pY6ly-gBsgnYr2bpUMzo?key=ihWpnacGhFPvEXYYLGtkwA>)

Once a step is added, you have to define its index, Name, Color, Icon, Type (function), wait for user, notify user, and the default step.

The default step is a branching step. You can specify below where the execution should continue based on the previous step function output. If none of the values match a step, the execution will continue with the function indicated here.

!\[A screenshot of a computer

Description automatically generated]\(<https://lh7-rt.googleusercontent.com/docsz/AD_4nXcXKvtPvF1m-D_k3ZnHmCBxDdHA4d-Ye-0wK4_B8DVsoceOF_qb6MvaSne706Xwq2QiFrPT6MbRwwNRqD30EYwLBIQl703qjz4cNllqKXw0F8QMKvpbWONN1xWN_97mDUUeq7niMVQUzQ8jwS6JoEDjB9G-hGSXQ1kBjxh3K6PXwPeiZnEIhQ?key=ihWpnacGhFPvEXYYLGtkwA>)

\
Also, the next task(s) to execute have to be defined. After the function execution, the system variable {FunctionResult} is evaluated. Depending on its value, the next execution step is decided according to the following table:

!\[A screenshot of a computer

Description automatically generated]\(<https://lh7-rt.googleusercontent.com/docsz/AD_4nXcj2yRovwLKE-GdrgFL47NTt-vlJV-mucS4ZYrpUAzIQpOXCVWHa8gVfyiTh4BFAtGB9hF76DkvEAakPe5Hu6WGaA3lB9WcmthpjW--pZ6Fm4gCar6wOgLiBeBiUCT7AEzkiiF7SwJILiOZtcPsd754UBCi5iDCy8hqoMCImkfuC52VwTEJKgM?key=ihWpnacGhFPvEXYYLGtkwA>)

\
\ <br>


---

# Agent Instructions: 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:

```
GET https://docs.libnova.com/libnova/pipelines-module/steps.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.