Web services connector

<< Click to Display Table of Contents >>

Navigation:  Application integration >

Web services connector


Bizagi features a generic SOAP Web service connector (the "WS Connector"), which is easily configured by means of graphical mapping for inputs and outputs (without the need of programming).

This feature is designed to allow you to configure application integration in your business processes, as described at Application integration.


About the WS Connector

This feature is accessible from the step #6 of the Process Wizard in Bizagi Studio (Define integration interfaces).




When moving into the step #6 of the Process Wizard, you may easily configure invocation to web services in integration points of your processes:




Graphical interface

Upon selecting an integration point of a process, the WS Connector presents a guided 4-step configuration.

Through these 4 steps, you will be able to input the service's URL and rely on auto-discovery capabilities to further configure the invocation of a given web method.




Notice that graphical configuration allows you to easily configure mapping for inputs, outputs, any transformations, and optional error handling.




Standards supported by the Web service connector

The Web service connector is a powerful generic connector which consumes any Web service, be it set in the corporate ESB, in the cloud, or as an external application.

For SOAP Web services, the following are supported:

SOAP 1.1 compliant Web services.

SOAP 1.2 compliant Web services



Consider these notes as well:

When invoking SOAP Web services, it is required to use POST as the Web method.

When invoking REST services, XML format must be used in the sent and received information.

WSDL version 1.0. is supported.

Its version 2.0 is not supported.


Additional Web services extensions (WS-*) supported as well:





WS-Security: Authentication by Username tokens, and by Binary security token (version 1.1 spec).

For authentication through Binary security tokens, message protection (encryption) requires that the service publishes a public key in its WSDL.


If you need to invoke a SOAP Web service which uses definitions from a standard not listed above (e.g, WS-Discovery), or to consider a requirement not supported by the connector (such as X invocations of a service, say once per each record of a table), then you will need to use either Bizagi Connectors (preferred), or the Component Library feature in Bizagi.

The same applies if you want to invoke a RESTful service which uses OAuth in its authentication.

For more information, refer to Integrating APIs or custom code.


Further information

For more information about this feature, refer to its comprehensive documentation at Web services connector.