page for an interactive demo of some of the pack functionality.
Use Formulas to view your tasks and task lists.
Use Actions to edit and manage your tasks.
Use Sync Tables to sync your tasks and task lists in the doc.
This pack enhances the experience of Google Tasks users by enabling them to view and manage their Google Tasks related data from within their own Coda docs, as they would in native Google clients such as Google Calendar or Gmail on web or mobile.
This pack requests access to Google user data when you choose to connect a Google account. The pack requests access to two scopes in order to view, create, edit, organise, and delete your Google Tasks. Since this pack uses OAuth 2.0 to get permission to access Google user data, scopes are used to specify the type of data to access and how much access is needed. Granting access to these scopes enables the pack to fulfill the functionality of its building blocks which enable viewing and managing your Google Tasks related data from within your Coda docs.
Identity and Intent
Who is requesting Google user data?
The Google Tasks Pack is requesting access to Google user data, for the intent expressed in the
for details about the role of this pack and Coda in requesting Google user data.
What data is being requested?
This pack requests access to two Google API scopes to view, create, edit, organise, and delete the user’s Google Tasks, and Google Tasks related data (e.g. task lists).
Why is Google user data being requested?
This pack intends to provide a client to enable users to view, create, edit, and delete their tasks. This pack uses the Google API scopes to enable mutating and showing a user's Google Tasks data within Coda docs where they choose to install this pack. This is so that users can manage their tasks through their own Coda docs where my app is installed as a plugin and sync the changes with their Google tasks.
The security features Coda has built into the Packs platform ensure the authorized client credentials to access Google API Services are kept confidential:
Coda handles credentials on behalf of the Pack, stores them encrypted at rest, and applies them to outgoing requests such that neither Pack code, Pack makers, nor other users of a doc ever have access to them.
The security features Coda has built into the Packs platform ensure that all packs, including those that make use of Google API Services, are protected against unauthorized or unlawful access, use, destruction, loss, alteration, or disclosure:
Packs run in a dedicated, secure server. We execute Packs in a secure sandbox environment that isolates Pack executions from Coda’s broader infrastructure and data and from other executions of Packs. The infrastructure receives an annual professional penetration test and receives constant evaluation via Coda’s
This pack, as an application built using the SDK provided by Coda, and executed within a environment managed by Coda, characterizes the request for Google user data as an intent supplied to the aforementioned SDK, which ultimately manages the execution and implementation of such requests. The user granting access to the Google user data request results in authorized client credentials to access Google API Services being issued to the pack, which enables the pack to make authorized requests to Google APIs for such data.
Documentation for the pack including its various Formulas, Actions and Sync Table can be found in the
and in the formula editor and various other Coda interfaces, as you use the pack building blocks in your doc.
Most of the discussion surrounding this pack and its development can be found on the Coda Maker forum under the topic here:
Feel free to join in on the conversation, or share your use cases elsewhere in the community. Additionally, if one of your doc makes use of the pack and can be showcased publicly, please make sure to publish it so that it can be highlighted in the pack listing for others to see!
Source code is made open source and is hosted as a GitHub repository here:
Pack development is largely bound by limitations in the API Google exposes for interacting with Google Tasks, and so development is not expected to resume until the API is upgraded to cover additional functionality. Please see
for further details. At this time, development is focused on supporting existing functionality. Please get in touch if you have a use case that is presently not supported by this pack.
If you have any questions, concerns, or problems while using the pack, feel free to comment with your situation on the