Mid-Server requirement for Jenkins V2 Spoke integrationSummaryIntegrating ServiceNow with Jenkins over Jenkins V2 spoke does require a MID Server associated. Regarding the below documentation, actions in the spoke use REST calls, which run on a MID Server. It is suggested to use the connection record associated with the Jenkins alias to configure where actions run as well as set MID Server selection attributes. For more information, see MID server.https://docs.servicenow.com/bundle/newyork-servicenow-platform/page/administer/integrationhub-store-spokes/concept/jenkins-spoke.html These actions use REST calls, which run on a MID Server. Use the connection record associated with the Jenkins alias to configure where actions run as well as set MID Server selection attributes. Mid server is a Java application that runs as a Windows service or UNIX daemon on a server in the local network. https://docs.servicenow.com/bundle/newyork-servicenow-platform/page/product/mid-server/concept/mid-server-landing.html Be aware that Mid Server is behind the firewall and it is good to allow list ServiceNow instance IP's if the mid server will be residing behind the firewall for making calls on the cloud.