---
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


---

# Google Cloud Datastore Spoke

# Google Cloud Datastore Spoke {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 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 Google Cloud Datastore Spoke

The Google Cloud Datastore Spoke enables ServiceNow customers to manage NoSQL database services within Google Cloud Datastore directly from their ServiceNow instance.
It integrates database task automation with ServiceNow workflows, streamlining operations and management.
Show full answer Show less  
This integration requires an active Integration Hub subscription and is compatible primarily with Google Cloud Datastore v1, with potential compatibility for later versions.

## Key Features

* **Entity Management:** Automate exporting and importing entities to and from Google Cloud Datastore.
* **Index Management:** Create, delete, retrieve, and look up indexes to optimize database queries.
* **Operation Management:** Manage long-running operations by canceling, deleting, retrieving status, or listing operations matching specific filters.
* **Connection and Credential Management:** Uses aliases within Integration Hub to centrally manage connection and credential information, reducing the need for repetitive updates across multiple environments.

## Practical Considerations

* An active Google Cloud Datastore account is required to use the spoke.
* Dependent plugins such as IntegrationHub must be installed and properly licensed, especially if used beyond the scope of this spoke.
* The spoke version 1.0.2 is the latest and includes updates relevant to managing Google Cloud Datastore tasks efficiently.
* Setup involves configuring connections and credentials via Integration Hub aliases, facilitating seamless integration without manual action updates when credentials change.

## What to Expect

By implementing the Google Cloud Datastore Spoke, ServiceNow customers can expect streamlined automation of database tasks, improved operational efficiency through centralized management, and reduced administrative overhead in maintaining credentials and connection configurations.  
Manage the NoSQL database services in Google Cloud Datastore from your ServiceNow instance.

## Request apps on the Store {#gcloud-datastore-spoke__section_xcf_3df_mjb}

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).{#gcloud-datastore-spoke__inline-send-to-store}

## Integration Hub subscription {#gcloud-datastore-spoke__section_rsf_yvb_l3b}

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 {#gcloud-datastore-spoke__section_id4_b3v_bsb}

Google Cloud Datastore spoke v1.0.2 is the latest version. For version history of the spoke, see [Google Cloud Datastore spoke release notes](https://www.servicenow.com/docs/r/store-release-notes/store-integrationhub-rn-google-cloud-datastore.html).{#gcloud-datastore-spoke__gcloud-datastore}

## Supported versions {#gcloud-datastore-spoke__section_zjt_sh4_zgb}

This spoke was built for Google Cloud Datastore
v1, but may be compatible with later versions.

## Spoke requirements {#gcloud-datastore-spoke__section_cqn_msx_qlb}

Google Cloud Datastore account.

## Spoke dependencies {#gcloud-datastore-spoke__section_tmn_vsx_qlb}

If
you're having trouble installing the app, ensure that these dependent plugins are installed:

IntegrationHub (com.glide.hub.integrations)  
Note:  
Some of these plugins are licensable features and require appropriate licenses, if used outside the spoke implementation.

## Spoke actions {#gcloud-datastore-spoke__section_b43_3h2_hfb}

The Google Cloud Datastore spoke provides actions to automate Google Cloud Datastore tasks when events occurs in your ServiceNow instance.
Available actions include:  
{#gcloud-datastore-spoke__table_u1p_kh2_hfb__entry__3}

| Category | Action | Description |
|-|-|-|
| Entity Management | Entity Export | Exports a copy of all or a subset of entities from Google Cloud Datastore to another storage system. |
| Entity Management | Entity Import | Imports entities into Google Cloud Datastore. |
| Index Management | Create Index | Creates the specified index. |
| Index Management | Delete Index | Deletes an existing index. |
| Index Management | Get Index | Gets an index. |
| Index Management | Look up Index | Retrieves the list of indexes that match the specified filters. |
| Operation Management | Cancel Operation | Starts asynchronous cancellation on a long-running operation. |
| Operation Management | Delete Operation | Deletes a long-running operation. |
| Operation Management | Get Operation | Gets the latest state of a long-running operation. |
| Operation Management | Look up Operation | Retrieves the list of operations that match the specified filter in the request. |
[ ]

{#gcloud-datastore-spoke__table_u1p_kh2_hfb}

## Connection and credential alias requirements {#gcloud-datastore-spoke__section_ibn_pj2_hfb}

Integration Hub uses aliases to manage connection
and credential information. Using an alias eliminates the need to configure multiple
credentials and connection information profiles when using multiple environments. If the
connection or credential information changes, you don't need to update any actions that
use the connection. For more information, see [Connections and Credentials](https://www.servicenow.com/docs/access?context=r-credentials&version=australia&pubname=australia-platform-security&ft:locale=en-US).

For information about setting up the spoke, see
[Set up the Google Cloud Datastore spoke](https://www.servicenow.com/docs/_qCRaxmOD5ve8e_LQAAKcQ#setup-gcloud-datastore "Integrate the ServiceNow instance and Google Cloud Datastore spoke using Google Cloud Platform credentials to authenticate ServiceNow requests.").

