> For the complete documentation index, see [llms.txt](https://docs.senpiper.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.senpiper.com/workflow-builder/how-to-create-workflows/define-workflow-step/updating-status-and-defining-future-actions-buttons.md).

# Updating the status for a step of the workflow

Updating the status for a step helps in tracking the progress of the workflow and also determines the action to be taken for a step.

In [**Defining conditions for a step**](/workflow-builder/how-to-create-workflows/defining-conditions-for-a-step.md), we defined two conditions that bifurcated the flow into two paths representing the expense greater and lower than Rs. 10,000/- respectively. To further continue with the Reimbursement Workflow (Refer [***Overview***](/workflow-builder/introduction/overview.md)), for both these paths, the status needs to be updated to **Request Raised.** Let's look at how this is done.

### **Path 1: Claim amount <= 10000**

When the initiator submits the form, and the expense reimbursement amount is up to Rs. 10,000, the status should be updated to **Request Raised.**

To do so,

1\.    Click <img src="/files/-MhIq32JnXq34Tqc0FHq" alt="" data-size="line"> and then click **Continue.** The node n - 4 is created in the following manner.

<figure><img src="/files/yG6TgSI9PU8a5m1hrw68" alt=""><figcaption><p><em>Add New Step</em></p></figcaption></figure>

2\.    Under the **What should be the updated status?** dropdown list, select the required status. In this case, it is **Request Raised**.

{% hint style="info" %}

Can you update the status for **Path 2: Claim Amount > 10,000** as **Request Raised** in a similar manner? &#x20;
{% endhint %}

The end result will look like this:

<figure><img src="/files/FIVYSZdFmMXZO1awuplZ" alt=""><figcaption></figcaption></figure>


---

# 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.senpiper.com/workflow-builder/how-to-create-workflows/define-workflow-step/updating-status-and-defining-future-actions-buttons.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.