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

Table 1. Versions
GCP ServiceNow
Last tested on April 08, 2025
  • Washington DC
  • Xanadu
  • Yokohama

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

You can configure a connection for the connector by using the SGC Central view in the CMDB Workspace. The view enables you to discover and install connectors, and then effectively manage the full life cycle of creating, editing, monitoring, and debugging connections. To configure the connector using SGC Central, see Configure Service Graph Connector for GCP using SGC Central.
Important: Unless there are configuration issues, use the SGC Central view in the CMDB Workspace to configure the connection for the connector, as the guided setup method is being deprecated.

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.

The following table lists the data sources, the staging tables, the target tables as the CMDB CI classes, and the resource types imported for a GCP project.
Note:
  • All labels and tags associated with a GCP resource, except those for the Cloud Resource [cmdb_ci_cmp_resource] table, are added 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.

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.