LogoLogo
Documentation
Documentation
  • Getting Started
    • Introduction
    • Sign up to Developer Edition
    • Build Your First Agent
    • Developer Support
  • Core Concepts
    • Agent
      • Knowledge
      • Webhook
    • PII Masking
    • Sub-Agent
    • Intent
    • Workflow
      • Node
        • Input
        • Output
        • Loader
        • Display
        • API Node
        • Web Crawler
        • Table Write
        • Table Read
        • Ruleset
        • Upload Document
        • Javascript
        • Workflow
        • Loop
        • Document To Image
        • External Database
        • Storage Write
        • Storage Read
        • Fetch Document
        • Prompt
        • RAG Query
        • Vector Search
        • Emit Event
    • RAG
    • Model Hub
      • Entity Recognizers
    • Data Gateway
    • Rulesets
    • Code Snippets
    • Tables
    • Storage
    • Widget
  • Overview of GenAI
    • Introduction
    • Key concepts
      • Intent Classification
      • Inference
      • Generative AI Models
      • Large Language Models (LLMs)
      • Prompt Engineering
      • AI Agents
      • RAG (Retrieval Augmented Generation)
      • AI Workflow Automation
      • AI Agents vs LLM-based APPs
Powered by GitBook
On this page
  • Overview
  • Configurations
  • Example Use-cases
  • Key Takeaways for Developers
Export as PDF
  1. Core Concepts
  2. Workflow
  3. Node

Input

Overview

The Input Node in UPTIQ Workbench is designed to collect user input dynamically within a workflow, ensuring that processes requiring user-provided data can proceed efficiently. This node plays a crucial role in workflows where structured or freeform input is required before the next action is executed.

Unlike static configurations, the Input Node enables real-time user interaction, allowing workflows to adapt based on user-provided values. It supports multiple input types, including basic text, numbers, and rich text formatting, making it ideal for structured and detailed data collection scenarios.

Configurations

Type (Required)

Defines the format of user input to be collected. Supported types:

  • Rich Editor: Provides a rich text editor for detailed responses, such as structured reports, summaries, or project documentation.

  • String/Number: Collects basic text or numeric input, useful for entering loan amounts, names, or other direct values.

Rich Editor Input Configuration (Optional, applicable only when Type = Rich Editor)

  • Template: Predefines a structured format to guide user input in the rich text editor.

  • Example: A template prompting users to enter an executive summary and key objectives.

Output Format

  • The collected user input is structured in following JSON format

{
  "userInput": "<user-entered value will be available here. Accessible via 'userInput' key>"
}

Example Use-cases

1. Capturing Detailed User Input in a Loan Application

Scenario: A financial institution requires applicants to provide a loan justification with structured details about their project. The Input Node, configured as a Rich Editor, guides the applicant in submitting the required information.

Configuration for Rich Editor Input

Field
Value

Type

Rich Editor

Template

<p><strong>Executive Summary:</strong> Please provide a brief overview of the project.</p><p><strong>Key Objectives:</strong></p><ul><li>Objective 1</li><li>Objective 2</li><li>Objective 3</li></ul>

Output

{
  "userInput": "<p><strong>Executive Summary:</strong> This project aims to improve operational efficiency by automating key processes.</p><p><strong>Key Objectives:</strong></p><ul><li>Streamline workflow management</li><li>Reduce manual errors</li><li>Enhance reporting capabilities</li></ul>"
}

🔹 Why this is useful: This ensures that the applicant provides structured and detailed information, improving processing efficiency and data consistency.


2. Collecting Numeric Input for Loan Amount

Scenario: A loan application workflow requires the user to enter the requested loan amount before proceeding to eligibility checks. The Input Node is configured to accept a number as input.

Configuration for Numeric Input

Field
Value

Type

Number

Output

{ "userInput": 10000 }

🔹 Why this is useful: The workflow can now process the entered amount, apply eligibility criteria, and proceed with loan approval steps dynamically.

Key Takeaways for Developers

✅ Enables User-Driven Workflows – Collect user input in real-time, ensuring workflows proceed only when required information is provided.

✅ Supports Multiple Input Types – Choose between basic text, numbers, or rich text to accommodate different data collection needs.

✅ Structured Input with Templates – Use predefined templates in Rich Editor mode to ensure users provide information in a consistent format.

✅ Seamless Integration – Output data is formatted in JSON, allowing smooth processing in subsequent workflow nodes, such as AI models, validation logic, or database storage.

By incorporating the Input Node, developers can enhance interactivity in UPTIQ workflows, enabling intelligent and user-driven automation. 🚀

PreviousNodeNextOutput

Last updated 3 months ago