# Develop Integration with ONEWEB Microflow

**Microflow** is one of the core components of ONEWEB, designed specifically to **facilitate integration with other systems** in a lightweight and service‑oriented manner.

Microflow can be used to implement:

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

It plays the role of an **integration service layer**, enabling applications to exchange data and invoke services efficiently at runtime.

***

#### Purpose of Microflow in Integration

Microflow is primarily intended for:

* Service‑style integration logic
* Short‑running, stateless executions
* Backend services invoked by UI components or external callers
* Data transformation and validation
* API‑based communication between systems

Because of its execution model, Microflow is well suited for integrations that behave like **micro‑services** rather than business workflows.

***

#### Integrating with REST and SOAP APIs

ONEWEB Microflow supports integration with **external web services** using:

* **REST APIs**
* **SOAP web services**

Through the Microflow Designer, developers can configure service integration visually by defining:

* Endpoint URLs
* Request and response structures
* Authentication parameters
* Input and output mappings

ONEWEB automatically generates the necessary methods and data models required to invoke the service.\
This allows developers to integrate with external APIs **without writing custom integration code**.

From a design perspective, integrating with REST and SOAP services follows a similar visual configuration pattern inside Microflow.

***

#### Internal Integration Using Microflow

In addition to external systems, Microflow also enables **internal integration** within ONEWEB, such as:

* Connecting UI components (Pages or Smart Forms) to backend logic
* Sharing reusable integration logic across modules
* Acting as a common service layer for multiple application components

This internal reuse reduces duplication and promotes cleaner application architecture.

***

#### When to Use Microflow for Integration

Microflow should be used when:

* Integration logic is **service‑oriented**
* Execution is short‑lived and stateless
* Integration is triggered from UI actions or external API calls
* Real‑time or near real‑time response is required

For **long‑running, stateful, or workflow‑driven integrations**, **Process Designer** is a more appropriate tool.

***

#### Summary

**Develop Integration with ONEWEB Microflow** enables applications to connect with internal and external systems using a fast, flexible, and low‑code approach.

With Microflow, developers can:

* Build service‑style integrations
* Connect to REST and SOAP APIs
* Reuse integration logic across components
* Avoid manual integration coding
* Keep integration logic clean and maintainable

Microflow is a foundational building block in ONEWEB’s integration architecture, providing **efficient connectivity and service orchestration** for modern applications.


---

# 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/building-apps/integrations/develop-integration-with-oneweb-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.