Automating with the WebService connector via REST enables you to implement complex use cases in a variety of ways. There is always a calling instance, the web service client. This can be found in different forms on the source system.
In ScriptRunner, first configure the address of the calling source system with the web service client. Only REST calls from this address are accepted by connector. A separate connector is required for each system. For authentication, you specify which authorized account is to be used to call the web service connector in ScriptRunner. Then define which of the configured actions can be started via this connector. Only assigned actions can be started with a REST call.
Now configure the web service client on the source system so that a valid and authorized REST call can be executed with a JSON data object.
If the source system executes a REST call to the web service connector, connector first checks for source address. If this is valid, the authentication check is run afterwards. If the authentication is valid, the transmitted data is extracted. Before the action is started, it is determined whether it can be started by the connector. If so, the valid parameters are passed to the action and it starts. At the same time, an ID is transferred to the source system, with which the system can retrieve the results and reports of the action.