Manage subscriptions for Looker by analyzing usage based on last login time and activity sessions to determine which licenses are stale so that you can reclaim these licenses and realize your potential savings.

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.

Integration Hub subscription

This spoke requires an Integration Hub subscription. For more information, see Legal schedules - IntegrationHub overview.

Spoke version

Looker spoke v1.0.0 is the latest version.

Spoke requirements

Looker account with an admin role.

Spoke dependencies

If you’re having trouble installing the app, ensure that these dependent plugins are installed:
  • ServiceNow Integration Hub Runtime (com.glide.hub.integration.runtime)
  • ServiceNow Integration Hub Action Step - REST (com.glide.hub.action_step.rest)
  • ServiceNow Integration Hub Action Template - Data Stream Inputs (com.glide.hub.action_type.datastream)
  • ServiceNow Workflow Studio - Dynamic Inputs (com.glide.hub.dynamic_inputs)
  • Complex Object (com.glide.cobject)
Note: Some of these plugins are licensable features and require appropriate licenses if used outside the spoke implementation.

Spoke actions

The Looker spoke provides actions to automate Looker tasks when events occur in your ServiceNow instance. Available actions include:

Category Action Description
Role Management Look up Roles Retrieves all roles in an account.
User Management Look up Users Stream Retrieves all users in an account.
Update User Modifies the specified user’s details.
Delete User Deletes the specified user and associated records from the account.
User Inputs - Dynamic Retrieves the list of fields to be used as dynamic input.
Note: This spoke has a Look up User action and Software Asset Management related actions only.

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 Setting up the Looker spoke.