Skip to main content

​
What does it do?

Input nodes define how users provide information to your assistant. They specify what type of data your assistant can receive and how that information should be processed. Think of Input nodes as the entry points where users submit their requests, documents, or data for your assistant to work with.

​
How do I use it?

​
Setting Up an Input Node

When you add an Input node to your workflow, you’ll choose from several input types based on what kind of information users need to provide: Text Input: For written requests, questions, or instructions from users File Input: For document uploads (PDFs, Word docs, spreadsheets, etc.) URL Input: For web links that your assistant should analyze or process Image Input: For photos or images that need analysis or processing Data Input: For structured data like forms or specific data formats

​
Configuring the Input

Each Input node has one main configuration field: Prompt: Describe what type of input you expect users to provide. This helps both users understand what to submit and guides your assistant in processing the information correctly. For example:
  • “Customer support questions or issues”
  • “Resume documents for analysis”
  • “Product images for description generation”
  • “Website URLs for content analysis”

​
Configuration Options

​
Input Types Available

Text Input:
  • Users type their request directly
  • Good for questions, instructions, or written content
  • Example prompt: “Customer service inquiries”
File Input:
  • Users upload documents or files
  • Supports common file formats (PDF, DOCX, images, etc.)
  • Example prompt: “Contract documents for review”
URL Input:
  • Users provide web links
  • Assistant can access and analyze web content
  • Example prompt: “Website URLs for SEO analysis”
Image Input:
  • Users upload photos or images
  • Good for visual analysis or processing
  • Example prompt: “Product photos for catalog descriptions”
Data Input:
  • Users provide structured data
  • Good for forms or specific data formats
  • Example prompt: “Sales data in CSV format”

​
Custom Prompt Guidelines

Your prompt should clearly describe:
  • What type of information you want
  • Any specific format requirements
  • The purpose or context for the input
Good prompts:
  • “Customer support tickets or issues requiring assistance”
  • “Legal contracts in PDF format for clause analysis”
  • “Marketing campaign ideas and target audience details”
Avoid vague prompts:
  • “Input”
  • “Information”
  • “Data”

​
Best Practices

​
Write Clear Prompts

Make it obvious to users what they should provide. Specific prompts lead to better input quality and more accurate processing.

​
Match Input to Purpose

Choose the input type that best matches how users naturally want to provide information. Don’t force users to upload files when they just want to type a question.

​
Keep It Simple

Users should immediately understand what to provide without needing additional explanation or instructions.

​
Test with Real Users

Try your input configuration with actual users to ensure it’s intuitive and collects the information your assistant needs to be helpful.