workflow/Overview of Node Types

5.3 Overview of Node Types

In Pop's visual workflow, each node is a reusable functional module:

  • It has clearly defined Input Ports and Output Ports
  • It has an associated Executor that handles runtime logic
  • It has UI metadata such as name, icon, category, description (from workflow.json and node meta)

This chapter does not dive into every field. Instead, it helps you understand the overall capability landscape by categories. For in-depth usage of a specific node, refer to its individual documentation.

Below is a bird’s-eye view:

Category Typical Nodes Primary Use Cases
Input / Output entry, form, text-input, chat-input, sink Workflow entry, receiving inputs, outputs
AI & Prompting llm, history-context, prompt, kb, image LLM calls, Prompt building, KB retrieval
Control Flow & Logic conditional, loop, merge, timer, terminate Branching, loops, merges, stopping
Data & Storage dictionary, list, global-params, database, redis Internal data & external DB management
Document & File file-read, file-write, directory, pdf, powerpoint, excel Reading/writing files, document creation
Visualization result-view, table-view, chart, metric-card, web-view, doc-view Displaying results as tables, charts etc.
Tools / Utility http-request, resource-browser, hash, time, random, qrcode, script-exec Utility operations & external calls
Modules & MCP module, group, api-resource, mcp Reuse, grouping, and external tool access

Tip: Names & descriptions match src/locales/zh-Hans/workflow.json → nodes.*. Actual available nodes depend on NodeRegistry in node-registry.ts.

1. Input / Output Nodes (IO)

These nodes receive inputs, trigger workflows, and output results, typically placed at the top or bottom of the workflow.

1. entry — Entry Node

  • Description: The starting point of a workflow.
  • Usage:
    • Collect parameters from forms, chat, or external triggers.
    • Manage execution context (text, files, session info).
  • Features:
    • Supports text/file/chat inputs.
    • Shows UI execution status (ready, running, percent progress).

2. form — Parameter Form

  • Description: Build a form UI to collect user input.
  • Usage:
    • Used when publishing a workflow as an App.
    • Works with entry to build user-facing UIs.

3. text-input

  • Description: Receives a single piece of text.
  • Usage: Prompt testing, pre-processing before LLM.

4. chat-input & chat-output

  • chat-input: Receives multi-turn chat messages.
  • chat-output: Converts workflow data into chat messages.
  • Usage:
    • Build custom chatbots.
    • Combine with history-context.

5. record-input

  • Description: Record audio/video.
  • Usage: ASR workflows, video summarization flows.

6. sink / result-view

  • sink: Writes to DB/files/logs.
  • result-view: Shows the final UI output.
entry → processing → result-view
entry → processing → sink

2. AI & Prompting Nodes

These nodes power Pop's AI capabilities.

1. llm

  • Description: Universal LLM caller.
  • Key Config: model, prompts, temperature, max tokens, MCP tools.
  • Usage: Q&A, summaries, rewriting, translation, coding.

2. prompt

  • Description: Template-based prompt builder.
  • Usage: Shared prompt logic.

3. history-context

  • Extracts chat history with smart truncation.

4. kb — Knowledge Base Search

  • Used for RAG workflows.

5. image / video

  • AI image / video generation.

3. Control Flow & Logic Nodes

1. conditional

Branching via expressions.

2. loop

Iterate lists.

3. merge

Merge multiple branches.

4. timer

Delays / schedules.

5. terminate

Stops the workflow.

4. Data & Storage Nodes

1. dictionary / list

Structure data objects.

2. global-params

Global variables.

3. database

Query/update DB.

4. redis

Cache & state storage.

5. Document & File Nodes

File Operations

file-read, file-write, directory, resource-browser.

Document Generation

pdf, powerpoint, word, excel.

Processing Toolboxes

pdf-toolbox, image-toolbox.

6. Visualization Nodes

result-view, table-view, chart, metric-card, doc-view, web-view, image-view, video-view, canvas, qrcode.

7. Utility Nodes

http-request, hash, base64, random, time, uuid, script-exec, search, mailer.

8. Modules & MCP

module / group

For reuse & organization.

api-resource

Auto-generate forms/tables from APIs.

mcp

Model Context Protocol tools.

Summary

Pop workflows combine:

  • IO for data flow boundaries
  • AI for reasoning
  • Control Flow for logic
  • Storage for data
  • Document Tools for content
  • Visualization for display
  • MCP/Modules for extensibility.
Previous page
Workflow Editor Overview
Next Page
Nodes and Modules (Modules)