Service Graph Connector for GCP
Use the Service Graph Connector for GCP to ingest CMDB data from a Google Cloud Platform (GCP) project using the REST APIs.
Request apps on the Store
Visit the ServiceNow Store website 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.
Key features
- Get started quickly with a streamlined onboarding process.
- Use only the credentials you need.
- No MID Server required.
- Get end-to-end data coverage.
- No agents or individual scanning needed.
- Performant at scale.
Supported versions
| GCP | ServiceNow |
|---|---|
| Last tested on July 16, 2025 |
|
Use cases
You can use the Service Graph Connector for GCP to get visibility into cloud resource identities, relationships, and state in real-time.
Important information for upgrading Service Graph Connector for GCP
After you've installed the latest version of the Service Graph Connector for GCP, you must synchronize the newly added data sources. Use the Advanced Setup section in the guided setup to synchronize data sources. For more information, see Configure Service Graph Connector for GCP.
Configuring a connection for the connector
CMDB integrations dashboard
The Integration Commons for CMDB store app provides a dashboard with a central view of the status, processing results, and processing errors of all installed integrations. You can see metrics for all integration runs. You can filter the view to a specific CMDB integration, a specific time duration, or a specific integration run. For more details about monitoring GCP integrations in the CMDB Integrations Dashboard, see Using the CMDB Integrations Dashboard.
Data mapping
Data from the GCP data sources is mapped and transformed into the ServiceNow CMDB Configuration Item (CI) class definitions using the Robust Transform Engine (RTE). Data is inserted into the ServiceNow CMDB using the Identification and Reconciliation Engine (IRE).
When you complete setting up the connection, you can configure the integration to periodically pull data from the GCP application.
| Data source | Staging table | CMDB CI classes | Resource types |
|---|---|---|---|
| SG-GCP Organization | SG-GCP Organization [sn_gcp_integ_sg_gcp_organization] | Cloud Organizations | Organization |
| SG-GCP Folder | SG-GCP Folder [sn_gcp_integ_sg_gcp_folder] | Google Organization Folder | Folder |
| SG-GCP Project | SG-GCP Project [sn_gcp_integ_sg_gcp_project] | Google Organization Project | Project |
| SG-GCP Network | SG-GCP Network [sn_gcp_integ_sg_gcp_network] | Cloud Network | Network |
| SG-GCP Machine Image | SG-GCP Machine Image [sn_gcp_integ_sg_gcp_machine_image] | Image | MachineImage |
| SG-GCP Subnet | SG-GCP Subnet [sn_gcp_integ_sg_gcp_subnet] | Cloud Subnet | Subnetwork |
| SG-GCP Storage Volume | SG-GCP Storage Volume [sn_gcp_integ_sg_gcp_storage_volume] | Storage Volume | Disk |
| SG-GCP Storage Volume Snapshot | SG-GCP Storage Volume Snapshot [sn_gcp_integ_sg_gcp_storage_vol_snapshot] | Storage Volume Snapshot | Snapshot |
| SG-GCP Security Group | SG-GCP Security Group [sn_gcp_integ_sg_gcp_security_group] | Compute Security Group | Firewall |
| SG-GCP Software Inventory | SG-GCP Software Inventory [sn_gcp_integ_sg_gcp_software_inventory] |
When the Software Asset Management (SAM) application isn't installed: When the SAM application is installed: Software Installation |
Instance |
| SG-GCP VM Instance | SG-GCP VM Instance [sn_gcp_integ_sg_gcp_vm_instance] | Virtual Machine Instance | Instance |
| SG-GCP Execute Patch Job | SG-GCP Execute Patch Job [sn_gcp_integ_sg_gcp_execute_patch_job] | Not applicable | Not applicable |
| SG-GCP Hardware Type | SG-GCP Hardware Type [sn_gcp_integ_sg_gcp_hardware_type] | Hardware Type | MachineType |
| SG-GCP VM Hw Consolidation | SG-GCP VM Hw Consolidation [sn_gcp_integ_sg_gcp_vm_hw_consolidation] | Virtual Machine Instance | None |
| SG-GCP Load Balancer Pool | SG-GCP Load Balancer Pool [sn_gcp_integ_sg_gcp_load_balancer_pool] | Load Balancer Pool | TargetPool |
| SG-GCP Load Balancer Pool Member | SG-GCP Load Balancer Pool Member [sn_gcp_integ_sg_gcp_load_balancer_pool_member] | Load Balancer Pool Member | TargetPool |
| SG-GCP Load Balancer Health Service | SG-GCP Load Balancer Health Service[sn_gcp_integ_sg_gcp_load_balancer_health_service] | Cloud Load Balancer Health Service | HealthCheck |
| SG-GCP Load Balancer | SG-GCP Load Balancer [sn_gcp_integ_sg_gcp_load_balancer] | Cloud Load Balancer | BackendService |
| SG-GCP Load Balancer Service | SG-GCP Load Balancer Service [sn_gcp_integ_sg_gcp_load_balancer_service] | Load Balancer Service | ForwardingRule |
| SG-GCP Cloud Database | SG-GCP Cloud Database [sn_gcp_integ_sg_gcp_cloud_database] | Cloud DataBase | Instance |
| SG-GCP Cloud Function | SG-GCP Cloud Function [sn_gcp_integ_sg_gcp_cloud_function] | Cloud Function | Function |
| SG-GCP Cloud Object Storage | SG-GCP Cloud Object Storage [sn_gcp_integ_sg_gcp_cloud_object_storage] | Cloud Object Storage | Buckets |
| SG-GCP Kubernetes Cluster | SG-GCP Kubernetes Cluster [sn_gcp_integ_sg_gcp_kubernetes_cluster] | Kubernetes Cluster | Cluster |
| SG-GCP Kubernetes Node | SG-GCP Kubernetes Node [sn_gcp_integ_sg_gcp_kubernetes_node] | Kubernetes Node | Node |
| SG-GCP Kubernetes Pod | SG-GCP Kubernetes Pod [sn_gcp_integ_sg_gcp_kubernetes_pod] | Kubernetes Pod | Pod |
| SG-GCP Kubernetes Service | SG-GCP Kubernetes Service [sn_gcp_integ_sg_gcp_kubernetes_service] | Kubernetes Service | Service |
| SG-GCP Kubernetes Namespace | SG-GCP Kubernetes Namespace [sn_gcp_integ_sg_gcp_kubernetes_namespace] | Kubernetes Namespace | Namespace |
| SG-GCP Kubernetes Deployment | SG-GCP Kubernetes Deployment [sn_gcp_integ_sg_gcp_kubernetes_deployment] | Kubernetes Deployment | Deployment |
| SG-GCP Kubernetes Replicaset | SG-GCP Kubernetes Replicaset [sn_gcp_integ_sg_gcp_kubernetes_replicaset] | Kubernetes ReplicaSet | ReplicaSet |
| SG-GCP Kubernetes Cluster Roles | SG-GCP Kubernetes Cluster Roles [sn_gcp_integ_sg_gcp_kubernetes_cluster_role] | Kubernetes Cluster Role | ClusterRole |
| SG-GCP Kubernetes Cluster Role Binding | SG-GCP Kubernetes Cluster Role Binding [sn_gcp_integ_sg_gcp_kubernetes_cluster_role_binding] | Kubernetes Cluster Role Binding | ClusterRoleBinding |
| SG-GCP Kubernetes Node Pool | SG-GCP Kubernetes Node Pool [sn_gcp_integ_sg_gcp_kubernetes_node_pool] | Kubernetes Node Pool | NodePool |
| SG-GCP Generic Resource | SG-GCP Generic Resource [sn_gcp_integ_sg_gcp_generic_resource] Note: The SG-GCP Generic Resource data source only works with a service account that has organization-level access. |
Cloud Resource | Resource |
| SG-GCP Annotation | SG-GCP Annotation [sn_gcp_integ_sg_gcp_annotation] | Key Value | Annotation |
| SG-GCP Get Patch Job | SG-GCP Get Patch Job [sn_gcp_integ_sg_gcp_get_patch_job] | Not applicable | Not applicable |
| SG-GCP Generic Resource Annotation | SG-GCP Generic Resource Annotation [sn_gcp_integ_sg_gcp_generic_resource_annotation] | Key Value | Annotation |
- The SG-GCP Annotation data source populates all labels and tags associated with GCP supported resources to the Key Value table.
- Starting with the Service Graph Connector for GCP 1.10 version, the SG-GCP Generic Resource Annotation data source populates the tags and labels for Generic resources to the Key Value table.
- The basic information about a GCP resource is stored in the SG-GCP Extension Attributes [sn_gcp_integ_extension_attributes] table.
- After all the data sources are executed, the Server [cmdb_ci_server] class is updated with the class entry, and then based on the Windows or Linux class, the records are created in the Windows Server [cmdb_ci_win_server] and Linux Server [cmdb_ci_linux_server] classes, respectively.
- The SG-GCP Generic Resource data source imports data for generic resources not tracked by other data sources. The connector utilizes the Service Graph Resource Inclusion Whitelist
[sn_cmdb_int_util_service_graph_resource_inclusion_whitelist] table to differentiate between generic and other supported resource types.
The connector first populates all supported resources in the Service Graph Resource Inclusion Whitelist [sn_cmdb_int_util_service_graph_resource_inclusion_whitelist] table. These resources, categorized under their respective supported resource types, have specific data sources designated for ingestion within the connector. When the SG-GCP Generic Resource data source is executed and retrieves unsupported resource types, they are added to the Service Graph Resource Inclusion Whitelist [sn_cmdb_int_util_service_graph_resource_inclusion_whitelist] table and categorized as generic.
- For any discovered resources deleted later after pulling data, the Service Graph Connector for GCP automatically updates the Install Status field of the associated CMDB CI classes to indicate any retired or deleted records. For more information, see Life cycle management of records in Service Graph Connector for GCP and Record removal process in Service Graph Connector for GCP.
- Starting with the Service Graph Connector for GCP 1.9.0 version, when the sn_itom_pattern.use a single hardware type for cloud data centers system property is set to
true, hardware type data is added to the Cloud Hardware Type [cmdb_ci_cloud_hardware_type] table, instead of being added to the Hardware Type [cmdb_ci_compute_template] table. For more information, see the Service Graph Connector For GCP - Migrating to a new hardware type model [KB1899584] article in the Now Support Knowledge Base. - Starting with the Service Graph Connector for GCP 1.9.0 version, when the sn_cmdb_ci_class.use_single_cloud_os_image system property is set to
true, image type data is added to the Cloud Image [cmdb_ci_cloud_os_image] table, instead of being added to the Image [cmdb_ci_os_template] table. For more information, see the Service Graph Connector For GCP - Migrating to a new Cloud OS Image model [KB1983751] article in the Now Support Knowledge Base. - Starting with the Service Graph Connector for GCP 1.9.0 version, list API calls return only the information that is required to make batch calls and not the entire resource response.
- Starting with the Service Graph Connector for GCP 1.10 version, parallel data loading is enabled for the SG-GCP Annotation and SG-GCP Generic Resource Annotation data sources.
- Starting with the Service Graph Connector for GCP 1.10 version, you can configure the AppScript Folder IDs connection property to exclude AppScript folder information from imports. Automations are run on AppScript
folders, which contain multiple projects that include meta information. AppScript folders don't contain any resources such as networks, subnets, and VMs.
Specify the AppScript folder IDs as a comma-separated list in the
Valuefield of the AppScript Folder IDs connection property to exclude the AppScript folders and projects information from being added to the CMDB during import. - Starting with the Service Graph Connector for GCP 1.10 version, the SG-GCP Software Inventory scheduled import runs before the SG-GCP VM Instance scheduled import. The SG-GCP Software Inventory scheduled job populates the operating system information for the Server records, which determines the script that needs to be run for deep discovery (Shell script for Linux VMs or PowerShell script for Windows VMs).
- Starting with the Service Graph Connector for GCP 1.10 version, the SG-GCP Get Patch Job scheduled import supports deep discovery by running commands on VMs. For information about deep discovery for the Service Graph Connector for GCP, see the Enabling deep discovery for Service Graph Connector for GCP article in the Now Support Knowledge Base.
For more information on where data is saved when pulling data from a GCP project, see CMDB classes targeted in Service Graph Connector for GCP.
You can use the IntegrationHub ETL app to view the data maps. See IntegrationHub ETL for more information.
BYOL and BYOS support
Bringing your own licenses (BYOL) or bringing your own subscriptions (BYOS) is the process of bringing previously purchased on-premises licenses or subscriptions to Google Cloud. The connector supports the BYOL and BYOS of the Image CIs for the Red Hat Enterprise Linux (RHEL) and SUSE Linux Enterprise Server (SLES) services on Google Cloud. The connector populates the Key Value [cmdb_key_value] table with the licensing information. Depending on the platform usage, the key is set to either
Windows_OS_License_Type_automatic or Linux_OS_License_Type_automatic, and the key value is set to either BYOL or BYOS.