Build a clean frontend on top of existing SOAP systems
With WeWeb, you can connect to SOAP endpoints to read and write data from those systems inside the web apps you build:
Send SOAP requests (XML envelopes) to SOAP endpoints
Authenticate with common SOAP patterns (Basic auth, tokens, custom headers)
Trigger SOAP calls from user actions, page load, or workflows
Use SOAP responses to populate tables, forms, and dashboards
Combine SOAP data with other backends (REST APIs, databases, no-code backends)
Handle create, update, and delete operations through SOAP methods
Orchestrate SOAP calls in workflows alongside UI logic and app state
Create role-based experiences (internal teams, customers, partners) with controlled access
Combine multiple data sources in one app, even when some are SOAP-only
What WeWeb supports natively
Category
Feature
What it does
Data source
SOAP data source
Adds a SOAP-specific data source so you can register SOAP services and use them as collections without building everything from scratch.
Collections
SOAP-backed collections
Lets you create collections that call a SOAP operation and expose the parsed result as items or records usable in repeaters and other UI elements.
Endpoint config
WSDL/endpoint configuration
Allows you to configure the SOAP service endpoint and operation details so WeWeb knows how to build and send the XML envelope.
Transport
XML over HTTPS via HTTP layer
Uses the same HTTPS request engine as the REST/HTTP data source to POST XML envelopes to SOAP endpoints.
Headers
SOAP HTTP headers support
Lets you set headers such as Content-Type: text/xml and SOAPAction needed by most SOAP services, just like for other HTTP APIs.
Body templating
Dynamic SOAP XML
Supports using variables in the SOAP payload (e.g. IDs, filters) so envelopes can be built dynamically from user input or application state.
Response handling
Parsed result or raw XML
SOAP collections expose a structured result when possible. For advanced cases, you can also work directly with the raw XML text in variables.
Workflows
Trigger SOAP calls from workflows
Allows invoking SOAP operations from workflows (button click, page load, etc.) and branching logic based on success or parsed values.
Composition
Combine SOAP data with others
SOAP collection results can be joined or combined with other collections (REST, database) using WeWeb’s data-joining and formula tools.
Why use WeWeb with SOAP
WeWeb helps you turn SOAP services into user-friendly web apps without rebuilding the backend.
Perfect for:
A client portal that pulls account, billing, or case data from a SOAP-based system
An internal operations tool that triggers SOAP actions (create orders, update statuses, submit requests)
A dashboard that aggregates SOAP data with modern APIs for reporting
A request workflow app for approvals tied to a SOAP backend (HR, finance, procurement)
A partner portal that reads inventory, shipment, or eligibility information from SOAP services
And more…
Integrating SOAP with WeWeb
Integrating SOAP with WeWeb is straightforward:
Identify the SOAP operation you need and its required XML structure
In WeWeb, create a request configuration that sends the SOAP XML payload to the service endpoint
Add the required headers (commonly Content-Type, SOAPAction, plus any auth headers)
Map your app inputs (form fields, selected rows, user context) into the XML body
Parse the response so you can use it in your UI (tables, dynamic pages, forms, workflows)
Store useful outputs in variables, collections, or your backend as needed
Best practices
Prefer a backend proxy when the SOAP service is not browser-friendly (CORS, network restrictions, or strict auth)
Keep XML templates organized by operation: use consistent naming and reuse patterns
Validate inputs before sending requests to reduce SOAP faults and unclear errors
Normalize SOAP responses into cleaner app-ready data structures when possible
Performance can vary depending on the service: avoid chaining multiple SOAP calls on initial page load
FAQs
1. Can WeWeb integrate with SOAP services natively?
Yes, there is a dedicated SOAP data source plus the generic HTTP capabilities needed to send XML envelopes over HTTPS. You configure the SOAP service, then create collections or workflow calls that use it like any other data source.
2. How do I configure a SOAP service in WeWeb?
You add a SOAP‑type data source and provide the endpoint/operation details the service requires. Under the hood, WeWeb uses its HTTP layer to POST the SOAP XML to that endpoint with the appropriate headers.
3. How do I build SOAP requests with dynamic values (IDs, filters, etc.)?
You define the SOAP envelope template and inject variables into the XML for things like IDs, dates, or filters. Those variables can come from form inputs, page parameters, or other collections, letting you drive SOAP operations from the UI.
4. What does the SOAP response look like inside WeWeb, and how do I use it?
When possible, SOAP collections expose a structured result you can bind directly to repeaters, tables, or detail views. For more complex responses, you may work with the raw XML in variables and then transform it, or have a backend convert it to JSON for WeWeb.
5. When should I wrap SOAP behind a REST/JSON API instead of calling it directly from WeWeb?
For complex WSDLs, strict security policies, or heavy XML parsing, it’s usually better to build a backend adapter (that talks SOAP) and expose a simpler REST/JSON API to WeWeb. Direct SOAP from the frontend is best kept for simpler operations or internal tools where you control the service and contract.
