Generic Velosimo Process
Velosimo is an open iPaaS system where, among others functionalities, flow integrations are the most utilized.
The following diagram shows a basic integration flow in Velosimo.
In a basic integration you need to send data from system A to system B. Data needs to be obtained in system A and B, then A mapped to B which will then be saved in Velosimo.
To implement the integration in Velosimo, each process is defined and is introduced in Velosimo as a Flow component.
Before making any flows, the API's connection or authorization should be done in Velosimo to have the ability to make requests.
The operations/webhooks will need to be defined for each each endpoint as well.
See more information in Gateway > Webhooks section
Process A
In general:
- You will obtain the data from A via API.
- The data obtained will be saved in Velosimo. The information that you need stored or what should be sent to system B.
As the image indicates, this Import flow will need the creation of the elements listed.
See more information on how to create a flow in the Workflow > Flows.
Process B
In general:
- In this process you will transform or convert the data from A to B. A flow will need to be created with a converter translator. This flow does not require a webhook or operation.
See more information on how to create a flow in the Workflow > Flows.
Process C
In general:
- The data saved in Velosimo will be sent to system B via API. You should configure this flow with a template translator.
See more information on how to create a flow in the Workflow > Flows.