Hub
Pricing About
NodeNode / Manipulator

CASE Switch Start

Workflow ControlSwitches
Drag & drop
Like

This node routes its input to a selectable output port, allowing different branches of the workflow to be activated manually or using a flow variable. The input port type can be chosen when adding an input port using the “…” menu. The type can be changed by removing the input port and adding it again.

To migrate from the deprecated CASE Switch Model (Start) node, select Generic Port when creating the input port.

Node details

Input (Dynamic Inport)
Select the input port type and connect it. Only one input port can be selected at a time. If the input port is removed, all output ports are also removed.
  1. Type: XLS Formatter
  2. Type: GNE SDF Port
  3. Type: FileStorePrefixURIPort
  4. Type: FileStoreReferenceURIPort
  5. Type: FileStoreURIPort
  6. Type: KnimeConnection
  7. Type: PDB Advanced Query Port
  8. Type: Combined FSK object
  9. Type: FSK object
  10. Type: FSK object
  11. Type: Combined FSK object
  12. Type: FSK object
  13. Type: Combined FSK object
  14. Type: FSK object
  15. Type: PCML PortObject
  16. Type: FSK object
  17. Type: URIPortObject managed by FileStore
  18. Type: Binning Port Object
  19. Type: de.mpicbg.knime.scripting.r.port.RPortType2
  20. Type: JChem Database Connection
  21. Type: SP_Conn
  22. Type: SeleniumFirefoxPort
  23. Type: Density Scorer Model
  24. Type: KNFST Model
  25. Type: Outlier
  26. Type: Normalizer
  27. Type: Remote Connection
  28. Type: Feature Selection Model
  29. Type: Fuzzy Basis Function
  30. Type: Radial Basis Function
  31. Type: Sota
  32. Type: Transformation
  33. Type: Gradient Boosting Model
  34. Type: Regression Tree
  35. Type: Tree Ensembles
  36. Type: PMML Discretization
  37. Type: Correlation
  38. Type: CAIM
  39. Type: KnoxHdfsConnection
  40. Type: Spark Context
  41. Type: Spark Data
  42. Type: Spark ML Model
  43. Type: Spark MLlib Model
  44. Type: AWS Comprehend Connection
  45. Type: AWSConnection
  46. Type: AzureConnection
  47. Type: URI Object
  48. Type: Table
  49. Type: Flow Variable
  50. Type: Image
  51. Type: PMML
  52. Type: PortObject
  53. Type: Report Fragment
  54. Type: Color
  55. Type: FilterDefinition
  56. Type: Workflow Port Object
  57. Type: org.knime.credentials.base.CredentialPortObject
  58. Type: DB Data
  59. Type: DB Session
  60. Type: Distance Measure
  61. Type: DLNetworkPortObject
  62. Type: Keras Deep Learning Network
  63. Type: ONNX Deep Learning Network
  64. Type: DLPythonNetworkPortObject
  65. Type: TensorFlow 2 Model
  66. Type: TensorFlow Deep Learning Network
  67. Type: Email Session
  68. Type: Microsoft Fabric
  69. Type: DL4J Model
  70. Type: MOJO
  71. Type: H2O Context
  72. Type: H2O Frame
  73. Type: H2O Model
  74. Type: R Workspace
  75. Type: DocumentVectorPortObject
  76. Type: OpenNlpNerTaggerModelPortObject
  77. Type: StanfordNERModelPortObject
  78. Type: VectorHashingPortObject
  79. Type: Word Vector Model
  80. Type: Weka 3.7 Classifier
  81. Type: Weka 3.7 Cluster
  82. Type: File System
  83. Type: Google Drive
  84. Type: Google Cloud Storage Connection
  85. Type: KafkaConnection
  86. Type: org.knime.mongodb.connection.port.MongoDBConnectionPortObject
  87. Type: Network
  88. Type: Python
  89. Type: org.knime.python3.nodes.PythonBinaryBlobFileStorePortObject
  90. Type: org.knime.python3.nodes.PythonConnectionPortObject
  91. Type: Semantic Web Connection
  92. Type: AbstractHubAuthenticationPortObject
  93. Type: Weak Label Model
  94. Type: XGBoostModel
  95. Type: BPMN Model
  96. Type: Causal Graph
  97. Type: Directly Follows Msd
  98. Type: Directly Follows Model
  99. Type: Hybrid Petri Net
  100. Type: Petri Net
  101. Type: Process Tree
  102. Type: Replay Result in Alignment
  103. Type: Replay Result in Alignment
  104. Type: Event Log
  105. Type: Arx Config
  106. Type: se.redfield.knime.memgraph.memgraphconnector
  107. Type: se.redfield.knime.neo4jextension.neo4jconnector
  108. Type: spaCy pipeline
  109. Type: spaCy pipeline
  110. Type: se.redfield.textprocessing.nodes.port.SpacyModelPortObject
Output (Dynamic Outport)
The output ports. They are only present and editable if an input port type was selected and always have the same type. At least two outputs are required.

Extension

The CASE Switch Start node is part of this extension:

  1. Go to item

KNIME
Open for Innovation

KNIME AG
Talacker 50
8001 Zurich, Switzerland
  • Software
  • Getting started
  • Documentation
  • Courses + Certification
  • Solutions
  • KNIME Hub
  • KNIME Forum
  • Blog
  • Events
  • Partner
  • Developers
  • KNIME Home
  • Careers
  • Contact us
Download KNIME Analytics Platform Read more about KNIME Business Hub
© 2026 KNIME AG. All rights reserved.
  • Trademarks
  • Imprint
  • Privacy
  • Terms & Conditions
  • Data Processing Agreement
  • Credits