Input Node
Last updated
Last updated
The input node allows you to pass data of various data types into a pipeline. While not always, inputs are usually the start of a pipeline.
The input node does not have any node inputs.
Type: The data type that the input will allow. Use the Type dropdown to signify the data type:
Text (default): raw text (e.g., a user message, text from an article, etc) that will appear as an editable text box.
File: The most common file types are: PDF, Doc, Docx, txt, xls, xlsx, csv, rtf, odt, tsv, ods, JPEG, PNG, etc. The file input type will appear as a field where users can upload a file.
Audio: Audio recording that you can record through the VectorShift platform.
Based on the selected type, there are different node outputs for the input node
Input Type Text
Text: the inputted text.
Type: Text
Example usage: {{input_0.text}}
Input Type File
Processed_text: The inputted file processed into text
Type: Text
Example usage: {{input_0.processed_text}}
File: The inputted file
Type: File
Example usage: {{input_0.file}}
Input Type Audio
Audio: The inputted Audio
Type: Audio
Example usage: {{input_0.audio}}
The most common nodes the input node is connected to are the LLM node (as information in the prompt) and the knowledge base node (to query the knowledge base for information)
You can expose input to end users by exporting the pipeline.
Chat: The chat interface takes in one input of type Text and one output of type Text.
Form: The form interface takes in an arbitrary number of inputs of any Type and an arbitrary number of outputs of any Type.
Voicebot: The voice interface takes in one input of type Audio and one output of type Audio.
The below example is a pipeline for chatting with a knowledge base. The input node, representing the user message, is connected to both the knowledge base (to query the knowledge base semantically) and to the LLM (so the LLM can respond to the user question).