Google Tasks Spoke
Summarize
Summary of Google Tasks Spoke
The Google Tasks Spoke allows ServiceNow users to manage Google Tasks and lists directly from their ServiceNow instance. This integration enhances task management efficiency by automating interactions between ServiceNow and Google Tasks.
Show less
Key Features
- Integration Hub Subscription: Requires an Integration Hub subscription for full functionality.
- Supported Versions: API version v1; current spoke version is 1.3.1.
- Sample Subflows: Includes draft state subflows for automating Google Tasks, such as moving ServiceNow attachments to Google Tasks.
- Spoke Actions: Automate task management with actions like creating, updating, deleting tasks and task lists, and retrieving task details.
- Account Requirements: A custom app must be created in the Google Developers Console for integration.
- Connection Management: Uses connection and credential aliases to streamline configuration across different environments.
- MID Server Options: Actions can run on an instance or through a MID Server, depending on connection configuration.
Key Outcomes
By implementing the Google Tasks Spoke, ServiceNow customers can expect improved task management capabilities, a streamlined integration process with Google Tasks, and reduced overhead in managing connection settings across multiple environments. The ability to automate task-related actions enhances productivity and ensures seamless collaboration between ServiceNow and Google Tasks.
Manage Google tasks and list from your ServiceNow instance.
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.
Supported versions
API version v1.
Spoke version
Google Tasks spoke v1.3.1 is the latest version.
Spoke subflows
The Google Tasks spoke provides sample subflows in the draft state to demonstrate automating Google Tasks. To customize a sample subflow, copy it to a new application scope. Available sample subflows include:
| Subflow | Description |
|---|---|
| Move a ServiceNow attachment to Google Tasks | Copies an attachment from ServiceNow to Google Tasks. |
Spoke actions
The Google Tasks spoke provides actions to automate Google Tasks when events occur in ServiceNow. Available actions include:
| Category | Action | Description |
|---|---|---|
| Task Management | Complete Task | Mark a task complete in a task list. |
| Create Task | Create a task in a task list. | |
| Delete Task | Delete a task from a task list. | |
| Get Task | Retrieve details of a specified task from a task list. | |
| Look Up Tasks | Retrieve details of specified tasks from a task list. | |
| Update Task | Update details of the specified task in a task list. | |
| Task List Management | Create Task List | Create a task list in your Google Tasks account. |
| Delete Task List | Delete the specified task list. | |
| Get All Task Lists | Retrieve the details of all task lists in your Google Tasks account. | |
| Get Task List | Retrieve details of a specified task list. | |
| Update Task List | Update details of a specified task list. |
Google Tasks spoke account requirements
The Google Tasks spoke requires a custom app that you create in the Google Developers Console.
Connection and credential alias requirements
Integration Hub uses aliases to manage connection and credential information, and OAuth credentials. 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 information about setting up the spoke, see Set up Google Tasks spoke.
MID Server requirements
These actions use REST calls that can run either on an instance or, optionally, through a MID Server. Use the connection record associated with the Google Tasks alias to configure where actions run and, if needed, specify MID Server selection attributes. For more information, see MID server.
To set up the MID Server for this spoke, see Set up MID Server for a spoke.