--- sourceDocument: Australia Workflow Data Fabric sourceDocumentLink: https://www.servicenow.com/docs/r/australia/integrate-applications Release : - australia ft:locale : - en-US ft:publication_title : - Australia Workflow Data Fabric ft:clusterId : - crint bundleId : - crint workflow : - Creator --- # Agent Client Collector Spoke # Agent Client Collector Spoke {#ariaid-title1} Release version: Australia Updated March 12, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Agent Client Collector Spoke The Agent Client Collector (ACC) spoke automates the execution of commands on agents or configuration items (CIs) where the ACC framework is installed. It collects output data and sends it to your ServiceNow instance via the MID Server, enabling remote management and monitoring of endpoints directly from ServiceNow. Show full answer Show less This spoke requires an Integration Hub subscription and supports ACC framework version 2.2.0, with potential compatibility for later versions. It depends on several ServiceNow plugins, including IntegrationHub Runtime, REST action steps, Complex Object, Flow Designer Dynamic Inputs, ITOM Visibility License, and the Agent Client Collector Framework itself. ## Key Features * **Prebuilt Subflows:** Sample workflows help automate common tasks such as managing compliance for remote workers, restarting agents, detecting cyberattacks, and installing the ACC framework on Linux or Windows hosts. These samples can be customized by copying them into new application scopes. * **Spoke Actions:** Automate various ACC framework operations, including checking agent status, retrieving logged-on users, network statistics, running processes, running services (Windows), system details, restarting agents, running commands, running Osquery, and installing the agent on Linux or Windows systems. * **Command Execution Control:** For security, ensure ACCALLOWLIST is set to 0 (Linux) or False (Windows) to enable command execution on agents. * **IP Range Configuration:** When using install agent actions, configure CIDR ranges within the ACC spoke to specify allowed IP addresses or ranges for installations. * **MID Server Requirements:** A properly configured MID Server with PowerShell capability is mandatory to run these actions. Guidance is available for MID Server setup specific to this spoke. ## Practical Benefits for ServiceNow Customers * Centralize and automate remote management of endpoints through ServiceNow workflows without manual intervention on each host. * Improve operational efficiency by automating compliance checks, agent health monitoring, and threat detection. * Reduce risk and improve security posture by integrating cyberattack detection and automated agent restarts. * Streamline agent deployment and maintenance across Linux and Windows environments with out-of-the-box installation flows. Automate the process of executing commands on agents or configuration items (CI) using the ServiceNow Agent Client Collector spoke. Agent Client Collector framework allows you to execute commands on the systems where it is installed and sends output data to the ServiceNow® instance through the MID Server. ## Request apps on the Store {#acc-spoke__section_sz5_jv3_z3b} Visit the [ServiceNow Store](https://store.servicenow.com/sn_appstore_store.do#!/store/home) to view all the available apps, and for information about submitting requests to the store. For cumulative release notes information for all released apps, see the [ServiceNow Store version history release notes](https://www.servicenow.com/docs/r/store-release-notes/sn-store-release-notes.html).{#acc-spoke__inline-send-to-store} ## Integration Hub subscription {#acc-spoke__section_ac2_ryf_p4b} This spoke requires an Integration Hub subscription. For more information, see [Legal schedules - IntegrationHub overview](https://www.servicenow.com/content/dam/servicenow-assets/public/en-us/doc-type/legal/snc-addendum-integrationhub.pdf). ## Spoke version {#acc-spoke__section_rzy_fjr_bsb} Agent Client Collector spoke v1.2.0 is the latest version. For version history of the spoke, see [Agent Client Collector Spoke release notes](https://www.servicenow.com/docs/r/store-release-notes/store-integrationhub-rn-agent-client-collector.html).{#acc-spoke__acc-ver} ## Supported versions {#acc-spoke__section_bc2_ryf_p4b} This spoke was built for Agent Client Collector framework v2.2.0, but may be compatible with later versions. ## Spoke dependencies {#acc-spoke__section_hc2_ryf_p4b} If you're having trouble installing the app, ensure that these dependent plugins are installed: * ServiceNow IntegrationHub Runtime (com.glide.hub.integration.runtime) * ServiceNow IntegrationHub Action Step - REST (com.glide.hub.action_step.rest) * Complex Object (com.glide.cobject) * ServiceNow Flow Designer - Dynamic Inputs (com.glide.hub.dynamic_inputs) * ITOM Visibility License (com.snc.itom.vis.license) * Agent Client Collector Framework v2.2.0 (sn_agent) Note: To enable Agent Client Collector to execute commands, ensure that `ACC_ALLOW_LIST=0` for Linux environments or `ACC_ALLOW_LIST=False` for Windows environments. {#acc-spoke__ul_ic2_ryf_p4b} Note: Some of these plugins are licensable features and require appropriate licenses, if used outside the spoke implementation. ## Spoke subflows {#acc-spoke__section_ld2_ryf_p4b} The Agent Client Collector spoke provides sample subflows to demonstrate automating Agent Client Collector framework tasks. To customize a sample subflow, copy it to a new application scope. Available sample subflows include: {#acc-spoke__table_mdd_ryf_p4b__entry__2} | Subflow | Description | |-|-| | Managing Compliance for Remote Workers | Manages compliance for remote workers and sends an email to the system administrator when one or more specified compliance conditions are violated. | | Restart Agent | Verifies the status of an agent and restarts the agent if the status is down. | | SNH CyberAttack Detection | Applies SigHealth CyberAttack Detection for Windows server and send an email to the system administrator when a threat is detected. | | Install Agent on Linux | Installs Agent Client Collector on a Linux hosts. | | Install Agent on Windows | Installs Agent Client Collector framework on multiple windows hosts. | [ ] {#acc-spoke__table_mdd_ryf_p4b} ## Spoke actions {#acc-spoke__section_nc2_ryf_p4b} The Agent Client Collector spoke provides actions to automate Agent Client Collector tasks when events occurs in your ServiceNow instance. Available actions include: {#acc-spoke__table_oc2_ryf_p4b__entry__2} | Action | Description | |-|-| | Get Agent Status | Get the status of an agent. | | Get Logged on Users | Retrieves the list of all logged-in users and the related metadata for the specified host system. | | Get Network Statistics | Retrieves the list of all network interfaces and the related metadata for the specified host system. | | Get Running Processes | Retrieves the list of all running processes and the related metadata for the specified host system. | | Get Running Services | Retrieves the list of all running services in Windows OS and the related data for the specified host system. | | Get System Details | Retrieves the hardware and software details of the specified agent. | | Restart Agent | Restarts an agent. | | Run Command on Agent | Runs a command on a given agent host. Note: Use caution while executing commands. | | Run Osquery on Agent | Runs the specified Osquery on the specified agent host. | | Install Agent on Linux | Installs Agent Client Collector framework on a Linux host. | | Install Agent on Windows | Installs Agent Client Collector framework on windows host. | [ ] {#acc-spoke__table_oc2_ryf_p4b} Note: To use the Install Agent on Linux and Install Agent on Windows spoke actions, navigate to Agent Client Collector SpokeCIDR Ranges, create a record to specify the required IP address or range of IP addresses. For information about setting up the spoke, see [Set up the Agent Client Collector spoke](https://www.servicenow.com/docs/AToCebA93~AjIpT_RypgrA "Integrate the ServiceNow Agent Client Collector framework and Agent Client Collector spoke."). ## MID Server requirements {#acc-spoke__section_znl_vyt_dfc} To use these actions, your instance must have a MID Server set up and configured to use PowerShell. For more information about running actions on the MID Server, see [Integration steps](https://www.servicenow.com/docs/3HAkBEjCzmcSEOfq7SkGnQ "Enable custom actions to integrate with external systems by activating Integration Hub, which adds integration steps to the Workflow Studio interface."). For more information about the MID Server, see [MID Server](https://www.servicenow.com/docs/access?context=mid-server-landing&version=australia&pubname=australia-servicenow-platform&ft:locale=en-US). To set up the MID Server for this spoke, see [Set up MID Server for a spoke](https://www.servicenow.com/docs/OEkPOX7xORDj2GD6UZwzjg "Configure MID Server settings on your ServiceNow instance that enables it to integrate with a third-party application via MID Server after you have set up the connection record for a spoke."). *[\>]: and then