# Web service

The Web Service Connector can be used to consume SOAP based web services. It can also be used to consume WCF services that are not based on SOAP, such as net.pipe and net.tcp bindings.

#### Configuration <a href="#configuration" id="configuration"></a>

* Create/update Connector\
  &#x20;In this section the WSDL that describes the web service is specified and there is also a button for creating the actual connector. Before a connector can be created it must have a *Name* specified. You must provide a valid URI to a WSDL and start *Create/update* before the connector configuration can be saved.\
  \
  The URI can refer to a file if there are no external references in the WSDL. Note that the file path is relative to Flow Server.\
  \
  &#x20;If the URI refers to an http endpoint (typically it is) you can, if needed, provide user and password (and optionally domain) before starting *Create/update*.\
  \
  Do not update the connector unless the remote service has changed.\ <br>
* Runtime configuration\
  &#x20;After the connector has been created a basic configuration is stored in this section.
* Client credentials\
  &#x20;Setups the client credentials to use when communicating with remote service.

#### Example <a href="#example" id="example"></a>

[Creating a connector to AX Document Services](https://home.novacuraflow.com/Help/latest/?help_root_connectors_communication_webservice_example_ax)


---

# 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://help.novacuraflow.com/6.12/development/flow-studio/connectors/communication/web-service.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.