Skip to the main content.

Web Service Connector

Automation via REST API

The Web Service Connector enhances ScriptRunner with a REST API and thus opens up a variety of automation scenarios. The calling instance in these scenarios is always a web service client that needs to be capable of executing a REST call with a JSON data object.

When a source system calls the Web Service Connector, the connector first checks its IP address and authentication. Given that both are valid, the data is extracted from the JSON object.

Subsequently, the Connector checks whether the Action may be started. Only then are the parameters passed to the Action and it is executed. At the same time, an ID is transferred to the calling system, with which it can retrieve the Action results and reports.


Integrate and Automate your whole Infrastructure


Your monitoring system constantly displays errors and warnings for which you already know what to do next. Automate troubleshooting so that you only have to worry about the exceptions.
Define sensors and errors which ScriptRunner should handle, partially or fully automated.

IT Service Management

There is still too much running manually? With ScriptRunner you can significantly enhance the ITSM. Users start automated ScriptRunner actions in their familiar working environment without knowing it. Nevertheless, with ScriptRunner you have everything under control.

Business Workflows

With ScriptRunner you can combine business workflows with the requirements of IT operations. You start ScriptRunner actions within a workflow and process the results further. This is how you separate the business logic from the technology via PowerShell.


Tasks in business departments can directly affect IT operations. You can automate this by integrating the application with ScriptRunner. The tasks can then be performed directly by the business user. You leave the execution to ScriptRunner.

Technical application of the Web Service Connector

You can call the Web Service Connector from the external system using two methods: direct REST call using URI or using a registered webhook after an event in the external system.

In ScriptRunner Server, an authorization process is run first to verify that the calling system is authorized. If access to ScriptRunner Server is authorized, it is checked whether the use of the called action is allowed by this connector.

The implementation of REST calls on the external system can be done by different means:

  • Using a configurable REST client interface
  • Use of an application-specific, scriptable interface
  • Using an executable program with our call script
05_scriptrunner-web-service-connector (2)