> For the complete documentation index, see [llms.txt](https://docs.pletor.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pletor.ai/build-your-system/nodes/input-nodes.md).

# Input nodes

User inputs shape what the AI creates.

Input nodes are the starting point for most flows. They define what information users provide when running your flow — text instructions, reference images, video files, audio clips, or documents.

<figure><img src="https://2795436344-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fnyc5C4KVCklpMy0pLa15%2Fuploads%2FaW9LVS3iThrsFRAvbQb8%2F2025-12-02%2011.26.45.gif?alt=media&amp;token=bee3b726-27bf-4a1f-93b0-09406a8efc4c" alt=""><figcaption></figcaption></figure>

***

### Available input nodes

<table><thead><tr><th width="124.88018798828125">Node</th><th width="135.1328125">What it collects</th><th width="160.1822509765625">Accepted formats</th><th>Use case</th></tr></thead><tbody><tr><td><strong>Text Prompt</strong></td><td>Written instructions or briefs from users</td><td>Free text</td><td>Campaign briefs, creative directions, product descriptions, any text-based input</td></tr><tr><td><strong>Upload Image</strong></td><td>One or more reference images</td><td>Common image formats (JPG, PNG, WebP, etc.)</td><td>Product photos, style references, visual inspiration, logos</td></tr><tr><td><strong>Upload Video</strong></td><td>Video files for processing or reference</td><td>Common video formats (MP4, MOV, etc.)</td><td>Source footage for editing, reference clips, content to transform</td></tr><tr><td><strong>Upload Audio</strong></td><td>Audio files</td><td>MP3</td><td>Custom voiceovers, sound references, audio to sync with video</td></tr><tr><td><strong>Upload File</strong></td><td>Documents or data files</td><td>PDF, CSV, JSON, TXT</td><td>Brand books, data sheets, marketing playbooks, product catalogs</td></tr></tbody></table>

***

### Tips

* **Keep inputs minimal.** Every input is friction for the end user. Only ask for what the flow actually needs.
* **Combine inputs with Text Assistants.** Place a Text Assistant node after your inputs to merge and structure multiple inputs into a single clean prompt before it hits your AI generation node.
* **Label your inputs clearly.** Rename input nodes to describe what the user should provide (e.g., "Product photo" instead of "Upload Image").
* **Use Upload File for rich context.** A PDF brand book gives the AI far more context than a short text prompt — connect it to a Text Assistant to extract the relevant information.