Does sn_ws.RESTMessageV2() inside Flow Designer Script Step count as Integration hub

[Prassadh_P]

Background

Our main end-to-end alert flow is built in Flow Designer. The flow performs alert enrichment and then sends outbound alert notifications to external systems, including:

1. Netcool
2. A separate SaaS solution

Currently, some of our custom Actions use the standard IntegrationHub REST step to perform outbound REST calls.

 ITOM Flow Designer implementation is consuming a high number of REST / IntegrationHub transactions, and therefore may be contributing to IntegrationHub license utilization.

To reduce or avoid this usage, we created new custom Actions where we removed the direct REST step and replaced it with a Script step.

New Design

For the outbound call to Netcool, the new design is as follows:

1. Flow Designer calls a custom Action.
2. The custom Action uses a Script step, not a REST step.
3. The Script step calls a custom Script Include.
4. The Script Include performs the outbound REST call using:

var request = new sn_ws.RESTMessageV2(); request.setEndpoint('https://example-endpoint'); request.setHttpMethod('POST'); request.setRequestHeader('Content-Type', 'application/json'); request.setRequestBody(payload); var response = request.execute();

So technically, the REST call is no longer configured as an Action Designer REST step.
However, the outbound call is still being initiated from a Flow Designer / Action Designer execution context.

Question

Can someone from ServiceNow or the community confirm the correct licensing / transaction behavior?

Specifically:

If we use a Script Include with sn_ws.RESTMessageV2() instead of the Action Designer REST step, but the Script Include is invoked from a Flow Designer Action Script step, will the outbound REST call still be counted as IntegrationHub usage / IntegrationHub transaction?

Why We Need Clarification

We need to understand whether IntegrationHub usage is determined by:

1. The specific step type used, for example, REST step vs Script step,
   or
2. The execution context, for example, outbound calls originating from Flow Designer / Action Designer / IntegrationHub, regardless of whether the REST call is made through a REST step or scripted using sn_ws.RESTMessageV2().

Based on ServiceNow documentation, it appears that IntegrationHub includes the ability to call external systems from an Action Designer Script step, not only through REST/SOAP protocol steps. ServiceNow documentation states that IntegrationHub can be used to call external systems using integration APIs from an Action Designer Script step, and can also activate protocol steps such as REST, SOAP, and PowerShell. (servicenow.com)

Also, ServiceNow Support documentation describes an IntegrationHub transaction as an outbound call originating from Integration Hub, Flow Designer, Remote Tables, and/or Orchestration, including operations, actions, or orchestrations that result in outbound calls. (support.servicenow.com)

This suggests that simply replacing the REST step with a Script step may not avoid IntegrationHub transaction counting if the outbound call still originates from Flow Designer / Action Designer.