# Integrations Integrating applications with **external systems and databases** is often complex, time‑consuming, and prone to implementation errors.\ Traditional integration approaches usually require custom code, specialized expertise, and extensive maintenance effort. ONEWEB simplifies this challenge by providing a **low‑code, visually configured integration platform** that enables reliable and reusable integrations across the application landscape. *** #### **Visual Configuration** ONEWEB provides **visual UI‑based tools** for configuring integrations, eliminating the need for extensive manual coding. With visual configuration: * Integration flows can be designed and managed through graphical interfaces * Developers and designers can collaborate on integration logic * Configuration errors are reduced compared to handwritten code * Changes can be made quickly without deep technical dependencies This approach significantly shortens development time and lowers the barrier to building integrations. *** #### **Shared Integration Units** ONEWEB supports the concept of **shared integration units**, allowing integrations to be designed once and reused across the application. For example: * If an application integrates with an external **currency conversion service** * The integration logic can be defined as a reusable unit * The same integration can be invoked from **multiple pages, processes, or microflows** This promotes consistency, reduces duplication, and simplifies long‑term maintenance. *** #### **Quick Deployment** ONEWEB enables **fast deployment of integration changes**. * When integration logic is updated within a **Process**, changes can be deployed directly to the runtime environment * Applications can start using the updated integration immediately after deployment > **Note**:\ > In the current version, **Microflow integrations** require exporting and manually deploying the Microflow artifact. This deployment model allows teams to respond quickly to integration changes or external system updates. *** #### **Built‑in Monitoring & Logging** ONEWEB provides **built‑in monitoring and logging capabilities** for integrations. These features allow users to: * Track execution of integration flows * Monitor success and failure of external calls * Inspect logs for debugging and troubleshooting * Improve observability without additional tooling Integrated monitoring ensures better visibility and control over system‑to‑system interactions. *** #### **Summary** **Integration with Other Systems** in ONEWEB is designed to be: * Visual and low‑code * Reusable across application components * Fast to deploy and iterate * Observable through built‑in monitoring and logging By combining visual configuration, shared integration logic, and operational visibility, ONEWEB enables teams to build and manage integrations **more efficiently and reliably** as part of the application development lifecycle. --- # 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.md?ask= ``` 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.