# Integration Nodes

Microflow Designer provides a set of **built‑in Integration Nodes** that enable ONEWEB applications to connect with **databases, web services, file systems, and reusable logic components**.\
These nodes allow developers to implement integration and system interaction logic **visually**, without requiring low‑level integration coding.

Each Integration Node is designed for a **specific category of system interaction** and can be combined within a Microflow to construct complete end‑to‑end integration scenarios.

***

### Database Node

The **Database Node** allows a Microflow to communicate directly with a relational database as part of backend logic execution.\
It can be used to **retrieve, insert, update, or delete data** during Microflow execution.

<figure><img src="/files/WjVJkuyOr6cn0G2gB8oT" alt=""><figcaption></figcaption></figure>

#### Supported Connection Types

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

#### Supported SQL Operations

* **SELECT** – Retrieve data
* **INSERT** – Create new records
* **UPDATE** – Modify existing records
* **DELETE** – Remove records

SQL commands can be defined directly to specify:

* Target tables
* Fields and columns
* Conditions and parameters

#### Typical Use Cases

* Integration with legacy databases
* Fetching reference or master data from external systems
* Synchronizing records between systems

***

### Sub Process Node

The **Sub Process Node** allows a Microflow to invoke another **Microflow or Process** as a reusable subroutine.

This node supports **modular and maintainable design** by enabling logic reuse rather than duplication.

<figure><img src="/files/VLpzaSII4SMQaRmEIuIo" alt=""><figcaption></figcaption></figure>

#### Suitable Scenarios

* Integration logic repeated across multiple Microflows
* Complex logic that should be broken down into smaller, focused units
* Large Microflows that need to remain readable and manageable

#### Best Practices

* Encapsulate reusable integration or validation logic into separate Microflows
* Keep parent Microflows focused on **orchestration**, not implementation details

***

### Web Service Node

The **Web Service Node** enables Microflows to integrate with **external web services** and system APIs.

Supported service types include:

* **SOAP Web Services**

<figure><img src="/files/OFXE9qugs7MN8N7Y7qrV" alt=""><figcaption></figcaption></figure>

* **REST APIs**

<figure><img src="/files/W8vLFSY5cf9SWn6ip6iq" alt=""><figcaption></figcaption></figure>

Service configuration is performed visually, and ONEWEB automatically handles:

* Service method generation
* Request and response data structure creation
* Invocation and communication logic

From a design perspective, **SOAP and REST services are configured in a similar manner**, reducing complexity when integrating heterogeneous APIs.

#### Typical Use Cases

* System‑to‑system integration
* External service invocation
* Enterprise API consumption

***

### File Read Node

The **File Read Node** allows Microflows to read and process structured data from files stored across various sources.

#### Supported File Types

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

#### Supported File Sources

* Local file system
* FTP
* SFTP
* FTPS

<figure><img src="/files/gfmS1db7JMm7QXgL3zOn" alt=""><figcaption></figcaption></figure>

#### Capabilities

* Automatically derive data models from file structures
* Populate business objects with file content
* Configure success and failure handling paths

#### Common Use Cases

* Batch data imports
* File‑based system integration
* Legacy data and offline data processing

***

### Summary

Integration Nodes form the **core building blocks** of integration logic in Microflow Designer.

Using Integration Nodes, developers can:

* Integrate with databases using SQL operations
* Invoke external SOAP and REST services
* Process Excel, XML, CSV, and fixed‑width files
* Reuse logic via Sub Process Nodes
* Compose complete integration flows visually

Together, these capabilities make Microflow Designer a **powerful low‑code integration layer**, enabling ONEWEB applications to interact seamlessly with both internal systems and external services in enterprise environments.


---

# 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/oneweb-platform-th/designer-reference/microflow-designer/integration-nodes.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.