Microservice Input Processor

Modified on Tue, 30 Nov 2021 at 10:51 AM


This processor is used to import data from exposed Workflows that serve as Microservices.

It can also be used to "push" data into ONE DATA and trigger a Workflow execution.


In real world applications, it is very common that data can be collected from different sources. It would be easier to track this dynamic data and apply some defined transformations to it in order to extract some values.

The Microservice Input Processor acts as an "endpoint" to which requests can be sent, so whenever new data is collected, it is sent via HTTP request, this processor collects the data and executes the triggered Workflow.


The configuration menu of this processor looks the following:

NOTE THAT: Since the first field is used to identify the processor, every Microservice Input must have a unique identifier within a Workflow.
The Bearer Token Key must be included in the Authorization when making the POST request. More information on how to retrieve the token can be found here.

Test Input: this is used to show the schema of the data that comes from the Microservice call and it should contain at least one row which includes sample values for each Column.

And if the provided schema and the schema in the POST request do not match, an error occurs.


This processor will receive the data coming from the HTTP call of the Microservice and will output it so it can be used by other processors of the Workflow.


In this example we will use Postman software to send the HTTP requests to the Workflow to test the functionality of our processor of interest.

First we create a new Workflow and import the Microservice Input & output processors.

Open Postman to configure the POST request. After including the Bearer token into the Authorization field, go to the Body Tab and configure the data to send:

Then the Configuration of the Microservice Input Table

For the Microservice Output Table, provide the Id of the result table:

After running the POST request, the Workflow will indicate that a newer version exists. When updating it, the result of the Workflow execution is displayed, along with data from the query

Data collected from different sensors can be combined by a specific tool, which then sends it to the Workflow in for Pre-processing and Transformation and finally extract relevant values.

This can be used in IoT-based industries.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article