# Node Input

In Scripting contexts you can get the node input by calling the instance id of the previous node from which you want to get your data we have 3 types of data inputs:

{% content-ref url="/pages/dZi9n9tNK2Uf2dLQZuNX" %}
[DataFrame](/6.1/scripting/contexts/node-input/dataframe.md)
{% endcontent-ref %}

Example Nodes: VisualQuery, Query, DataPrep, QueryInMemory...

{% content-ref url="/pages/YXsjiZZKg57YiiJ5A2d6" %}
[File](/6.1/scripting/contexts/node-input/file.md)
{% endcontent-ref %}

Example Nodes: FileUploader, ExcelBuilder, FileRenamer, File Listener...

{% content-ref url="/pages/U386SWv4IumIDJBNDelg" %}
[DataObject](/6.1/scripting/contexts/node-input/dataobject.md)
{% endcontent-ref %}

Example Nodes: ScriptSourceObject, JSONObject...

#### Example Use:

```typescript
// Example get DataFrame from VisualQuery_1
VisualQuery_1.row(0).name

// Example get File from FileUploader_1
FileUploader_1.asFile()

// Example get DataObject from ScriptSourceObject_1
ScriptSourceObject_1.asData();
```


---

# 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.b2winsuite.com/6.1/scripting/contexts/node-input.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.