# What Is ONEWEB Integration?

**ONEWEB Integration** refers to the capability of the ONEWEB platform to **connect and interact with external systems** using a **visual, low‑code approach**, without requiring extensive manual coding.

Through ONEWEB’s integration tools, developers can integrate with:

* **REST APIs**
* **SOAP web services**
* **External databases**
* **File‑based systems**

using **drag‑and‑drop configuration** and guided UI screens. From a user’s perspective, there is **minimal difference between integrating with a REST API or a SOAP API**, as both follow the same visual configuration principles.

***

#### **Visual, Low‑Code Integration Approach**

ONEWEB abstracts integration complexity by providing:

* Visual designers instead of handwritten integration code
* Configurable nodes and connectors
* UI‑driven definition of endpoints, data mapping, and execution logic

This approach:

* Reduces development time
* Minimizes implementation errors
* Makes integration accessible beyond traditional backend specialists

As a result, integration logic can be designed, maintained, and evolved more efficiently.

***

#### **Integration Tools in ONEWEB**

ONEWEB provides **two primary tools** for building integrations:

* **Microflow Designer**
* **Process Designer**

Both tools share similar configuration concepts but are designed for **different integration purposes**. Choosing the right tool depends on how the integration is intended to be used within the application.

***

#### **Process Designer – Workflow‑Driven Integration**

**Process Designer** is used to create **business processes**, which are typically:

* **Long‑running**
* **State‑driven**
* **Workflow‑oriented**

In integration scenarios, Process Designer is suitable for:

* Orchestrating multiple system interactions
* Managing approvals or user‑driven steps
* Coordinating integration logic across time

Process‑based integrations are commonly used when integration is part of a broader business workflow.

***

#### **Microflow – Service‑Oriented Integration**

**Microflow** represents **lightweight, service‑oriented logic**, often functioning as microservices.

Microflow is commonly used for:

* Asynchronous or synchronous service calls
* Backend services invoked from UI components
* Fast, stateless integrations
* API‑like interactions with external systems

Microflows are typically tightly integrated with Pages, Smart Forms, or external clients.

***

#### **Choosing Between Process and Microflow**

Although Microflow Designer and Process Designer are similar in configuration style, they differ in **intent and usage pattern**:

* Use **Process Designer** for long‑running, workflow‑centric integrations
* Use **Microflow** for short‑lived, service‑oriented integrations

> For a detailed comparison, refer to:\
> **Microflow vs Process Flow**\
> <https://docs.oneweb.tech/oneweb/design-and-develop-oneweb-apps/integration-with-other-systems/microflow-vs.-process-flow>

***

#### **Summary**

**ONEWEB Integration** provides a flexible and visual way to connect applications with external systems.

Key characteristics include:

* Visual, low‑code integration design
* Support for REST, SOAP, databases, and files
* Two complementary integration tools:
  * **Microflow** for service‑style integrations
  * **Process Designer** for workflow‑driven integrations

This integration model allows applications built on ONEWEB to act as **connected, orchestration‑capable systems** without the complexity of traditional integration frameworks.


---

# 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.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.