Connectors
Protocols & Custom Connectors
SOAP Service
Generic SOAP web services: call operations on any WSDL-described endpoint
API checked August 18, 2026
- Signs in with
- Username and password
- Runs on
- Cloud or On-Prem Worker
- Operations
- 1
- Ready-made triggers
- 0
Connect SOAP Service
- In Neblex open Connect › Connections and click New Connection.
- Search for SOAP Service and give the connection a clear name.
- Fill in the fields. Secret values are encrypted and never shown again.
- Click Test, then Create Connection.
| Field | What to enter |
|---|---|
| Service endpoint (host + path, without https://)Required | HTTPS service authority and path, without the scheme. Query parameters are permitted; userinfo and fragments are rejected. |
| Username (optional, HTTP Basic)Optional | Supply together with Password to use HTTP Basic. Leave both empty for anonymous transport or SOAP-header authentication. |
| Password (optional, HTTP Basic)OptionalSecret | Supply together with Username. The password is sealed and never exposed as an operation input. |
Use it in a flow
- Open a flow, open the node library and search for SOAP Service.
- Drag it onto the canvas and choose an Operation and your connection.
- Map the operation's fields from earlier steps, or click Map with Matt.
- Use Test this step to see what it returns, then save.
To start a flow from SOAP Service without a ready-made trigger: a Poll for changes trigger can check one of its list operations on a schedule and pass on only what is new; if SOAP Service can send webhooks, a Webhook trigger receives them at its own URL.
Operations
1 operations in 1 groups. Each one is a step you can add to a flow.
SOAP1
Call a SOAP operationcall | Send one synchronous body-bearing SOAP 1.1 or 1.2 HTTPS POST and return its decoded SOAP Body. |