# Microflow vs. Process Flow

Both **Microflow Designer** and **Process Designer** are integration tools in ONEWEB that enable applications to interact with **other modules or external systems**.\
While they share similar configuration concepts and execution nodes, they are designed for **different types of integration scenarios**.

The key distinction lies in their **intended usage and execution model**.

***

#### Microflow

**Microflow** is primarily designed to implement **micro‑services and service‑oriented integration logic**.

It is typically used for:

* Backend services invoked by UI components
* API‑style integrations
* Fast data retrieval, validation, or transformation
* Short‑lived integration tasks

Microflows are lightweight and focused, making them ideal for real‑time or near real‑time interactions.

***

#### Process Flow

**Process Flow**, created using **Process Designer**, is used to model and execute **business processes or workflows**.

It is best suited for:

* Workflow‑driven integration
* Multi‑step, stateful processes
* Long‑running interactions that may span hours, days, or weeks
* Business logic involving approvals, decisions, or user participation

Processes provide orchestration and state management across multiple integration steps.

***

#### Key Differences

| Aspect            | **Microflow**                                 | **Process Flow**                             |
| ----------------- | --------------------------------------------- | -------------------------------------------- |
| Primary Purpose   | Create micro‑services and service logic       | Create business processes or workflows       |
| Execution Model   | Single‑shot execution                         | Executed in multiple stages                  |
| Duration          | Short‑running                                 | Long‑running (can extend to days or weeks)   |
| Interaction Style | Suited for synchronous and asynchronous calls | Better suited for workflow‑driven execution  |
| Typical Use Case  | API calls, backend services, UI integration   | Business processes, approvals, orchestration |
| Deployment Mode   | Embedded mode and standalone server           | Standalone server only                       |

***

#### How to Choose the Right Tool

Use **Microflow** when:

* Integration logic is stateless and short‑lived
* The interaction behaves like a service or API
* The integration is triggered by UI events or external calls
* Performance and simplicity are key considerations

Use **Process Flow** when:

* Integration is part of a business workflow
* The process spans multiple steps or states
* Human interaction or approvals are involved
* Long‑running orchestration is required

Choosing the appropriate integration tool improves performance, maintainability, and clarity of the application architecture.

***

#### Summary

Both **Microflow** and **Process Flow** play essential roles in ONEWEB’s integration architecture:

* **Microflow** provides fast, service‑oriented integration for real‑time interactions
* **Process Flow** enables structured, long‑running, workflow‑driven integration

Understanding their differences ensures that integrations are implemented using the **right abstraction for the right scenario**, resulting in more scalable and maintainable 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/building-apps/integrations/microflow-vs.-process-flow.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.