Google Cloud VPC Access Spoke
Manage connector and operations in your Google Cloud VPC Access account from ServiceNow instance.
Request apps on the Store
Visit the ServiceNow Store 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.
Integration Hub subscription
This spoke requires an Integration Hub subscription. For more information, see Legal schedules - IntegrationHub overview.
Spoke version
The current Google Cloud VPC Access spoke version is 1.0.1.
Supported versions
This spoke was built for the Google Cloud VPC Access API version v1, but may be compatible with later versions.
Google Cloud VPC Access spoke requirements
The Google Cloud VPC Access spoke requires a custom app that you create in Google Cloud Platform.
Spoke dependencies
- Google Identity and Access Spoke
- Google Cloud Virtual Network Spoke
- ServiceNow Flow Designer - Dynamic Inputs (com.glide.hub.dynamic_inputs)
- ServiceNow IntegrationHub Action Step - REST (com.glide.hub.action_step.rest)
- ServiceNow IntegrationHub Runtime (com.glide.hub.integration.runtime)
- Complex Object (com.glide.cobject)
- ServiceNow IntegrationHub Action Template - Data Stream (com.glide.hub.action_type.datastream)
Spoke actions
| Category | Action | Description |
|---|---|---|
| Connector Management | Create Connector | Creates a connector in the specified project. |
| Delete Connector | Deletes the specified VPC Access connector. | |
| Get Connector | Retrieves the specified VPC Access connector. | |
| Look up Connectors | Retrieves the list of VPC Access connectors available in the specified location. | |
| Location Management | Look up Locations | Retrieves the list of locations available in the specified project. |
| Operation Management | Get Operation | Retrieves details of the specified operation. |
| Look up Operations | Retrieves a list of operations available with in the specified location. |
Connection and credential alias requirements
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.
For information about setting up the spoke, see Set up the Google Cloud VPC Access spoke.