Hub
NodeNode / Other

Call Workflow Service

KNIME Labs Workflow Abstraction
Drag & drop
Like
Copy short link

Calls another workflow and obtains the results for further processing in this workflow. The workflow can receive inputs via Workflow Service Input nodes and return outputs using Workflow Service Output nodes.

Each Workflow Service Input node in the workflow to be called will create an input port on this node when finishing the configuration of the Call Workflow Service node. Similarly, each Workflow Service Output node will create an output port on the node.

The called workflow can be located on a KNIME Server or in the Local Workspace. If the workflow is located on a KNIME Server, the execution will take place on the server. In contrast, when using the Workflow Executor node, the execution will always be performed in the workflow containing the Workflow Executor node.

The difference between this node and the Call Workflow (Table Based) node is the set of supported workflow input and output nodes. This node supports the Workflow Service Input and Workflow Service Output nodes, which support arbitrary port types and are more efficient than the various Container Input and Container Output nodes. The container input and output nodes on the other hand expect and produce data in a format that can easily be produced by third-party software, whereas Workflow Service Input and Workflow Service Output nodes are designed exclusively to be used by other KNIME workflows.

To define which Workflow Service Input node receives data from which of this node's input ports, each input node defines a parameter identifier. The parameter identifier is supposed to be unique, but it might happen that a workflow has multiple input nodes defining the same parameter name. In this case, KNIME will make the parameter names unique by appending the input node's node ID to the parameter name, e.g., "input-table" becomes "input-table-7".

Node details

Input ports
  1. Type: File System
    KNIME server connection
    Optional connection to a KNIME Server where the workflow to be executed is located. If connected, the execution of the workflow will be performed on that server.
Inputs (Dynamic Inport)
One output port for each Workflow Service Input node in the workflow to be executed. The ports are automatically created when finishing the configuration of the node.
  1. Type: Google Sheets
  2. Type: Cluster Tree
  3. Type: Spark Context Legacy
  4. Type: se.redfield.bert.nodes.port.BertModelPortObject
  5. Type: Correlation
  6. Type: Distance Measure
  7. Type: Weka 3.6 Classifier
  8. Type: DLPythonNetworkPortObject
  9. Type: de.tarent.cumulocity.connector.CumulocityPortObject.TYPE
  10. Type: PDB Advanced Query Port
  11. Type: JChem Database Connection
  12. Type: URI Object
  13. Type: Salesforce OAuth2 Connection
  14. Type: se.redfield.knime.neo4jextension.neo4jconnector
  15. Type: Rowset Filter
  16. Type: GNE SDF Port
  17. Type: H2O Context
  18. Type: OPTICS Clustering Port
  19. Type: Weka Classifier
  20. Type: H2O Driverless AI Dataset Connection
  21. Type: MOJO
  22. Type: Event Log
  23. Type: Binning Port Object
  24. Type: Tree Ensembles
  25. Type: DirectAccessTablePortObject (for testing)
  26. Type: TensorFlow 2 Model
  27. Type: VectorHashingPortObject
  28. Type: File System
  29. Type: Twitter
  30. Type: org.knime.mongodb.connection.port.MongoDBConnectionPortObject
  31. Type: Normalizer
  32. Type: Spark Context
  33. Type: se.redfield.bert.nodes.port.BertClassifierPortObject
  34. Type: Semantic Web Connection
  35. Type: MOE Model
  36. Type: PCA
  37. Type: Remote Connection
  38. Type: Spark Data
  39. Type: DLNetworkPortObject
  40. Type: Weka 3.7 Cluster
  41. Type: H2O Frame
  42. Type: Radial Basis Function
  43. Type: Google API
  44. Type: XGBoostModel
  45. Type: SP_Conn
  46. Type: de.mpicbg.knime.scripting.r.port.RPortType2
  47. Type: Weak Label Model
  48. Type: Spark MLlib Model
  49. Type: H2O Model
  50. Type: Table
  51. Type: Keras Deep Learning Network
  52. Type: Naive Bayes
  53. Type: Weka 3.7 Cluster
  54. Type: Transformation
  55. Type: Weka 3.7 Classifier
  56. Type: Workflow Port Object
  57. Type: PortObject
  58. Type: Google Drive
  59. Type: se.redfield.bert.nodes.port.BertPortObjectBase
  60. Type: Size
  61. Type: Database Connection
  62. Type: Lucene
  63. Type: Feature Elimination
  64. Type: DocumentVectorPortObject
  65. Type: Network
  66. Type: Large Filestore
  67. Type: Spark Data (legacy com)
  68. Type: PMML
  69. Type: RPortObject
  70. Type: OpenNlpNerTaggerModelPortObject
  71. Type: LibSVM
  72. Type: Density Scorer Model
  73. Type: URI Object
  74. Type: Universe
  75. Type: KnimeConnection
  76. Type: com.schrodinger.knime.port.connection
  77. Type: Moz API Connection
  78. Type: DB Session
  79. Type: KafkaConnection
  80. Type: Arx Config
  81. Type: FilterDefinition
  82. Type: Directly Follows Model
  83. Type: AWSConnection
  84. Type: DB Data
  85. Type: Inactive branch
  86. Type: Tree Ensembles
  87. Type: DL4J Model
  88. Type: FileStoreURIPort
  89. Type: StanfordNERModelPortObject
  90. Type: FileStoreReferenceURIPort
  91. Type: Weka Cluster
  92. Type: Spark Data Legacy
  93. Type: AWS Comprehend Connection
  94. Type: Google Analytics
  95. Type: FileStorePrefixURIPort
  96. Type: AzureConnection
  97. Type: Weka 3.7 Classifier
  98. Type: Feature Selection Model
  99. Type: Spark Context (legacy com)
  100. Type: Ligand-Set
  101. Type: Spark Model (legacy com)
  102. Type: Petri Net
  103. Type: Neighbourgram
  104. Type: Microsoft Credential
  105. Type: Fuzzy Basis Function
  106. Type: Regression Tree
  107. Type: Word Vector Model
  108. Type: KNFST Model
  109. Type: Outlier
  110. Type: Compiled PMML
  111. Type: KnoxHdfsConnection
  112. Type: Database Query
  113. Type: se.redfield.node.port.orientdb.connection
  114. Type: PMML Discretization
  115. Type: Replay Result in Alignment
  116. Type: Sota
  117. Type: Weka 3.6 Cluster
  118. Type: Google Cloud Storage Connection
  119. Type: PMML Preprocessing
  120. Type: Spark Model Legacy
  121. Type: Weka 3.7 Classifier
  122. Type: URIPortObject managed by FileStore
  123. Type: H2O Driverless AI MOJO
  124. Type: Fingerprint Bayes
  125. Type: Spark ML Model
  126. Type: SeleniumFirefoxPort
  127. Type: Word Vector Model (deprecated)
  128. Type: Keras Deep Learning Network
  129. Type: Image
  130. Type: Regression Tree
  131. Type: Flow Variable
  132. Type: Gradient Boosting Model
  133. Type: Python
  134. Type: R Workspace
  135. Type: Arima
  136. Type: ONNX Deep Learning Network
  137. Type: Portable Format for Analytics
  138. Type: Shape
  139. Type: Python
  140. Type: TensorFlow Deep Learning Network
  141. Type: Weka 3.7 Cluster
  142. Type: CAIM
  143. Type: Python (deprecated)
  144. Type: XLS Formatter
  145. Type: Keras Deep Learning Network
  146. Type: Color
  147. Type: Process Tree
Outputs (Dynamic Outport)
One output port for each Workflow Service Output node in the workflow to be executed. The ports are automatically created when finishing the configuration of the node.
  1. Type: Google Sheets
  2. Type: Cluster Tree
  3. Type: Spark Context Legacy
  4. Type: se.redfield.bert.nodes.port.BertModelPortObject
  5. Type: Correlation
  6. Type: Distance Measure
  7. Type: Weka 3.6 Classifier
  8. Type: DLPythonNetworkPortObject
  9. Type: de.tarent.cumulocity.connector.CumulocityPortObject.TYPE
  10. Type: PDB Advanced Query Port
  11. Type: JChem Database Connection
  12. Type: URI Object
  13. Type: Salesforce OAuth2 Connection
  14. Type: se.redfield.knime.neo4jextension.neo4jconnector
  15. Type: Rowset Filter
  16. Type: GNE SDF Port
  17. Type: H2O Context
  18. Type: OPTICS Clustering Port
  19. Type: Weka Classifier
  20. Type: H2O Driverless AI Dataset Connection
  21. Type: MOJO
  22. Type: Event Log
  23. Type: Binning Port Object
  24. Type: Tree Ensembles
  25. Type: DirectAccessTablePortObject (for testing)
  26. Type: TensorFlow 2 Model
  27. Type: VectorHashingPortObject
  28. Type: File System
  29. Type: Twitter
  30. Type: org.knime.mongodb.connection.port.MongoDBConnectionPortObject
  31. Type: Normalizer
  32. Type: Spark Context
  33. Type: se.redfield.bert.nodes.port.BertClassifierPortObject
  34. Type: Semantic Web Connection
  35. Type: MOE Model
  36. Type: PCA
  37. Type: Remote Connection
  38. Type: Spark Data
  39. Type: DLNetworkPortObject
  40. Type: Weka 3.7 Cluster
  41. Type: H2O Frame
  42. Type: Radial Basis Function
  43. Type: Google API
  44. Type: XGBoostModel
  45. Type: SP_Conn
  46. Type: de.mpicbg.knime.scripting.r.port.RPortType2
  47. Type: Weak Label Model
  48. Type: Spark MLlib Model
  49. Type: H2O Model
  50. Type: Table
  51. Type: Keras Deep Learning Network
  52. Type: Naive Bayes
  53. Type: Weka 3.7 Cluster
  54. Type: Transformation
  55. Type: Weka 3.7 Classifier
  56. Type: Workflow Port Object
  57. Type: PortObject
  58. Type: Google Drive
  59. Type: se.redfield.bert.nodes.port.BertPortObjectBase
  60. Type: Size
  61. Type: Database Connection
  62. Type: Lucene
  63. Type: Feature Elimination
  64. Type: DocumentVectorPortObject
  65. Type: Network
  66. Type: Large Filestore
  67. Type: Spark Data (legacy com)
  68. Type: PMML
  69. Type: RPortObject
  70. Type: OpenNlpNerTaggerModelPortObject
  71. Type: LibSVM
  72. Type: Density Scorer Model
  73. Type: URI Object
  74. Type: Universe
  75. Type: KnimeConnection
  76. Type: com.schrodinger.knime.port.connection
  77. Type: Moz API Connection
  78. Type: DB Session
  79. Type: KafkaConnection
  80. Type: Arx Config
  81. Type: FilterDefinition
  82. Type: Directly Follows Model
  83. Type: AWSConnection
  84. Type: DB Data
  85. Type: Inactive branch
  86. Type: Tree Ensembles
  87. Type: DL4J Model
  88. Type: FileStoreURIPort
  89. Type: StanfordNERModelPortObject
  90. Type: FileStoreReferenceURIPort
  91. Type: Weka Cluster
  92. Type: Spark Data Legacy
  93. Type: AWS Comprehend Connection
  94. Type: Google Analytics
  95. Type: FileStorePrefixURIPort
  96. Type: AzureConnection
  97. Type: Weka 3.7 Classifier
  98. Type: Feature Selection Model
  99. Type: Spark Context (legacy com)
  100. Type: Ligand-Set
  101. Type: Spark Model (legacy com)
  102. Type: Petri Net
  103. Type: Neighbourgram
  104. Type: Microsoft Credential
  105. Type: Fuzzy Basis Function
  106. Type: Regression Tree
  107. Type: Word Vector Model
  108. Type: KNFST Model
  109. Type: Outlier
  110. Type: Compiled PMML
  111. Type: KnoxHdfsConnection
  112. Type: Database Query
  113. Type: se.redfield.node.port.orientdb.connection
  114. Type: PMML Discretization
  115. Type: Replay Result in Alignment
  116. Type: Sota
  117. Type: Weka 3.6 Cluster
  118. Type: Google Cloud Storage Connection
  119. Type: PMML Preprocessing
  120. Type: Spark Model Legacy
  121. Type: Weka 3.7 Classifier
  122. Type: URIPortObject managed by FileStore
  123. Type: H2O Driverless AI MOJO
  124. Type: Fingerprint Bayes
  125. Type: Spark ML Model
  126. Type: SeleniumFirefoxPort
  127. Type: Word Vector Model (deprecated)
  128. Type: Keras Deep Learning Network
  129. Type: Image
  130. Type: Regression Tree
  131. Type: Flow Variable
  132. Type: Gradient Boosting Model
  133. Type: Python
  134. Type: R Workspace
  135. Type: Arima
  136. Type: ONNX Deep Learning Network
  137. Type: Portable Format for Analytics
  138. Type: Shape
  139. Type: Python
  140. Type: TensorFlow Deep Learning Network
  141. Type: Weka 3.7 Cluster
  142. Type: CAIM
  143. Type: Python (deprecated)
  144. Type: XLS Formatter
  145. Type: Keras Deep Learning Network
  146. Type: Color
  147. Type: Process Tree

Extension

The Call Workflow Service node is part of this extension:

Related workflows & nodes

  1. Consumer of Anonymization Workflow Service
    Integrated Deployment Call Workflow Workflow Service
    This workflow makes use of the workflow 01_Anonymizer. It sends a SQL query and a workflo…
    knime > Examples > 06_Control_Structures > 07_Workflow_Orchestration > 03_Process_Anonymized_Data > 02_Consumer
  2. Prediction Service Consumer
    Workflow Service Random Forest
    This workflow calls a workflow service which applies a model to data. Data are generated …
    knime > Examples > 06_Control_Structures > 07_Workflow_Orchestration > 04_Call_Workflow_Service > 02_Prediction_Service_Consumer
  3. Prediction Service Consumer
    carlwitt > Public > Call Workflow > Prediction Service Consumer