dynamic insight (DI) can always poll data via REST, GraphQL or SOAP APIs. However, enterprises have applications and systems that are not accessible (protected via firewalls) from the outside world. There are two primary ways to exchange data if there is now API or direct data base access on an on-premise system.

1. File exchange using (S)FTP or cloud drives

Many on-premise software systems can automatically export data into a file storage e.g. (S)FTP or a cloud drive. These can be accessed via dynamic insight and then the data be processed in a flow. In this case, dynamic insight acts as a middleware (proxy) between the systems. As file formats, CSV, XLSX, JSON or XML can be used.

To ensure data quality, the validation helper can be added to ensure data is consistant and as expected.

2. Local script (agent) sends data from the database of a system to dynamic insight (https call)

A local script, also called agent, can be configured on-premise that either exports data or accesses a database and sends data to a dynamic insight Flow via a Webhook encrypted through https. dynamic insight can then e.g. connect to other systems, process the data and finally return data as a response to the on-premise system. This way two data can be sent and polled:

2.1 Sending data: The above method can send data from an on-premise system to another cloud service via dynamic insight as a middleware (proxy).

2.2 Polling data: The above method can poll data from a cloud service to an on-premise system via dynamic insight as a middleware (proxy).