# Goto

`goto` property of server response is optional.

&#x20;

### Goto Step / Sub Flow <a href="#goto-step-sub-flow" id="goto-step-sub-flow"></a>

Use this response to goto a step or sub flow:

```
{
    "version": "v1",
    "content": {
        "goto": "SOMETHING"
    }
}

```

You can goto:

| **Goto**   | **SOMETHING =**    | **e.g.**  |
| ---------- | ------------------ | --------- |
| A step     | step name (unique) | Welcome   |
| A step     | node\_ns           | f244n7831 |
| A sub flow | sub\_flow\_ns      | f244s1032 |

### Get sub\_flow\_ns <a href="#get-sub_flow_ns" id="get-sub_flow_ns"></a>

Find a sub flow and follow steps 1 and 2 in the following screenshot:

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

### Get node\_ns <a href="#get-node_ns" id="get-node_ns"></a>

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

Select a step, click "Copy Ref Url for this step", paste somewhere, then you will see the node\_ns of this step:

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


---

# 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.rapidbott.com/help-center/developers/dynamic-content/goto.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.
