# Integrate with Other Systems from/to Microflow

### Integrate with Other System from/to Microflow

**Microflow** is one of the core integration tools in ONEWEB, designed to act as a **service‑oriented integration layer**.\
It facilitates both:

* **Internal integration** between ONEWEB components
* **External integration** with third‑party systems and services

Microflow is typically used for **short‑lived, stateless, or service‑based interactions**, making it ideal for API calls, data lookups, and file‑based integrations.

***

### Integrate with SOAP Web Services and REST APIs

Microflow Designer provides a **Web Service Task** that enables integration with both **SOAP web services** and **REST APIs** using a visual configuration approach.

With the Web Service Task:

* Developers configure service endpoints and specifications via UI
* ONEWEB automatically generates:
  * Service methods
  * Request and response data structures
* No manual coding is required to consume the service

From a configuration perspective, there is **almost no difference between REST and SOAP integration**, simplifying service consumption regardless of protocol.

<figure><img src="https://2015371994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMpDjHWFRUtZ5nJcSfVXd%2Fuploads%2FFNwKlSZMD2PQLdNA2yrr%2F0?alt=media" alt=""><figcaption></figcaption></figure>

***

### Integrate with Existing Databases

Microflow also supports integration with **external databases** commonly used in enterprise environments.

Supported databases include (but are not limited to):

* SQL Server
* Oracle
* MySQL
* PostgreSQL
* IBM DB2

Microflow Designer provides a **Database Task** that allows connections and database operations to be configured visually.

Two database connection approaches are supported:

* **JNDI** – recommended for managed, application‑server environments
* **JDBC** – suitable for custom or external database connections

Database integration through Microflow is commonly used for:

* Legacy system integration
* External data lookup and synchronization
* Service‑level data access

<figure><img src="https://2015371994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMpDjHWFRUtZ5nJcSfVXd%2Fuploads%2FSkeHPGnwpvxgGwx2hmet%2F1?alt=media" alt=""><figcaption></figcaption></figure>

***

### Integrate with Excel, CSV, XML, or Fixed‑Width Files

Microflow supports integration with **structured file formats**, including:

* Microsoft Excel files
* Delimited (CSV) files
* XML files
* Fixed‑width files

The **File Read Task** allows Microflows to:

* Read structured data from files
* Create data models automatically
* Populate business objects for further processing

Files can be accessed from:

* Local file systems
* FTP
* SFTP
* FTPS

This type of integration is commonly used for:

* Data import and batch processing
* File‑based system integration
* Legacy data exchange

<figure><img src="https://2015371994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMpDjHWFRUtZ5nJcSfVXd%2Fuploads%2FaZsz4rFPPWTJnyp7lewU%2Fimage.png?alt=media&#x26;token=7cc56658-8cd4-42d6-a418-4d53a85bdfb8" alt=""><figcaption></figcaption></figure>

***

### When to Use Microflow for Integration

Microflow is best suited for integration scenarios that are:

* Service‑oriented
* Stateless or short‑running
* Triggered by UI components or external calls
* Focused on data retrieval or transformation

For **long‑running, stateful, or workflow‑based integration**, ONEWEB recommends using **Process Designer** instead.

***

### Summary

**Microflow‑based integration** enables ONEWEB applications to connect with external systems using a flexible, low‑code, and service‑oriented approach.

Using Microflow, applications can:

* Consume REST and SOAP services visually
* Integrate with external databases via JNDI or JDBC
* Process Excel, CSV, XML, and fixed‑width files
* Act as reusable backend services

Microflow plays a key role in ONEWEB’s integration architecture by providing **fast, scalable, and low‑complexity connectivity** between systems.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.onewebstack.com/building-apps/integrations/what-is-oneweb-integration/integrate-with-other-systems-from-to-microflow.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.