Technical referenceOfficial documentation16 min readReference data

FastGPT Workflow Node Reference

A grouped reference of the 34 workflow nodes defined in the FastGPT open-source repository, with node type, tool support and parameter counts.

This table describes FastGPT development snapshot 5957d06 (2026-09-07). Development definitions can precede a stable release; check the version you deploy.

How to use this table

This page lists the 34 workflow nodes defined in the open-source repository, grouped by category, with the node type identifier, whether the node can be mounted as a tool, and how many input and output parameters it declares. Use it to find which node provides a capability before building a workflow, or to locate a node by its type identifier in an exported workflow JSON.

Columns

ColumnMeaning
Node typeThe flowNodeType in the definition; used in exported workflow JSON, check compatibility when upgrading
NameThe node name shown in the interface
As toolYes means the node can be mounted as a tool by a tool-call node
Inputs / requiredDeclared input parameters, and how many are required
OutputsDeclared output parameters
DocsThe documentation path recorded in the definition

Three things to know before using this table

1. Only 9 of the nodes record an introduced version, and the formats differ.

Node typeNameRecorded versionNote
agentAgent4.17.0not yet in a released version
chatNodeAI Chat4.9.7—
classifyQuestionClassify4.9.2—
comment—4811uses the older numbering format
contentExtractText Extract4.9.2—
datasetSearchNodeDataset Search4.9.2—
emptyNode—481uses the older numbering format
toolCallTool calling4.9.2—
readFilesRead files4.9.2—

The remaining 25 nodes have no such field, so this table cannot say which version first shipped them. To confirm whether a node exists in a given version, check the node panel of that deployment.

2. 6 nodes have no readable name in the definition and are listed as missing.

Node typeCategory
appModuleOther
commentSystem input
emptyNodeSystem input
pluginModuleOther
toolOther
toolSetOther

Most of these are internal or placeholder nodes and do not appear in the node panel.

3. Parameter counts follow the definition, not the interface. Some parameters are shown or hidden based on earlier choices, so the interface can show fewer than the number here; the node with the most inputs declares 33, and most scenarios only need the required ones.

AI capabilities (8 nodes)

Node typeNameAs toolInputs / requiredOutputsDocs
chatNodeAI ChatYes22 / 04Node documentation
agentAgent—33 / 02—
classifyQuestionClassifyYes5 / 01Node documentation
toolParamsCustom Tool VariableYes0 / 00—
datasetSearchNodeDataset SearchYes14 / 12Node documentation
stopToolStop Tool calling—0 / 00—
contentExtractText ExtractYes5 / 13Node documentation
toolCallTool callingYes20 / 02Node documentation

Tools (10 nodes)

Node typeNameAs toolInputs / requiredOutputsDocs
answerNodeAssigned ReplyYes1 / 10Node documentation
codeCode runYes5 / 25Node documentation
ifElseNodeConditionYes1 / 01Node documentation
httpRequest468HTTPYes10 / 34Node documentation
loopRunLoop NodeYes7 / 21Node documentation
loopRunBreakLoop break—0 / 00—
parallelRunParallel RunYes7 / 33Node documentation
textEditorText EditorYes1 / 11Node documentation
readFilesRead filesYes1 / 13—
variableUpdateUpdate variablesYes1 / 00—

System input (8 nodes)

Node typeNameAs toolInputs / requiredOutputsDocs
nestedEndEnd—1 / 10—
loopRunStartLoop start—3 / 03—
pluginInputPlugin Input—0 / 00—
pluginOutputPlugin output—0 / 00—
nestedStartStart—2 / 11—
workflowStartStart—1 / 01—
comment——2 / 00—
emptyNode——0 / 00—

Interactive (2 nodes)

Node typeNameAs toolInputs / requiredOutputsDocs
formInputForm inputYes2 / 01—
userSelectUser SelectYes2 / 01Node documentation

Other (6 nodes)

Node typeNameAs toolInputs / requiredOutputsDocs
customFeedbackCustom FeedbackYes1 / 10Node documentation
datasetConcatNodeDataset search citation merge—2 / 01Node documentation
appModule——0 / 00—
pluginModule—Yes0 / 00—
tool—Yes0 / 00—
toolSet—Yes0 / 00—

When this table goes out of date

  1. New nodes and parameter changes ship with versions. Counts follow the current definition files and need rechecking after an upgrade.
  2. The commercial edition may provide additional nodes. This table covers the open-source repository only.
  3. Parameter count is not configuration effort. Most nodes require one or two fields; the rest have defaults or apply to specific scenarios.
  4. Check node identifier and name compatibility when upgrading. Use the identifier for programmatic checks.

Next steps

The tables above can be checked against the open-source repository. If a specific deployment needs to be assessed against these values, contact sales for support; the cloud service can be used directly without preparing the environment first.

  • Contact sales: assess your deployment against these values
  • Get started: use the cloud service and skip environment setup
  • Pricing: compare what each form covers

References

Parameter counting

Parameter totals count array entries in each node definition, including shared templates. Required totals count flags declared directly in that definition; shared templates and runtime conditions can add required fields.