Connect to Google Drive

The Google Drive connection in Taskie ties changes to Drive files to work you can track. Once a Google push channel is registered for your workspace, file change notifications are received, and if the file's details include a task ID, that file is linked to the task.

Scope of the current version: this version focuses on receiving push notifications securely and linking enriched files to tasks automatically. Personal OAuth connections, a file picker, attaching files directly, creating Docs/Sheets/Slides, Connected Search, link previews, Super Agent search, Drive automations and automatic management of Google Drive channels are coming in later phases.

Before you start

• Only a workspace owner or admin can create or disconnect the workspace Google Drive connection.
• In the Google Drive API, you need to create a watch channel for changes or files and enter Taskie's endpoint as the address.
• The channel ID is stored in the Channel ID field and the channel token in the Channel Token field.
• Official Google Drive notifications usually don't include the full file body. For automatic linking, a later processing step or an enriched source has to pass the file's name or description to Taskie.
• Personal connections and direct access to users' private files aren't available in the current version.

Create a workspace connection

1. In the Google Drive API, create a watch request for the change source you want.
2. Keep the channel's id value. This same value is sent in the X-Goog-Channel-ID header.
3. Create a non-sensitive token for the channel. Google returns it in the X-Goog-Channel-Token header, and Taskie uses it to verify the request.
4. In the Taskie App Center, open Google Drive and choose the Workspace tab.
5. Enter the Channel ID, Channel Token, optional access token and a label for the connection.

Channel Token security: Taskie compares X-Goog-Channel-Token with the connection's encrypted value. This header isn't stored in the webhook delivery record and shouldn't contain an OAuth token or other sensitive data.

Automatically link files to tasks

For automatic linking, write the task ID in the file's name, path or description. These forms are supported:

• TASK-12 — the ID on its own.
• #TASK-12 — with a # prefix.
• CU-TASK-12 — with a CU- prefix.
• #9fq2b1 — the task's hashed ID, only with a # or CU- prefix.

For example, the file TASK-61 launch brief is linked to task TASK-61 and appears in the task's Linked items section.

Task status and status commands

In the current version, Google Drive doesn't change task status. If you write TASK-61[Done] in a file's name or description, the file is linked to the task, but the task's status doesn't change. Automatic status changes are currently available for GitHub and GitLab events.

Manage and disconnect

The connection status and the time of the latest event appear in the Integrations tab of your workspace settings. An owner or admin can disconnect it from Taskie. To stop notifications completely, also stop the watch channel in the Google Drive API or let it expire.

Common mistakes

• Entering a Drive ID or File ID instead of the Channel ID. The connection value must be the watch channel's id.
• Putting an OAuth token in the Channel Token. Google recommends that the channel token not contain sensitive data.
• Expecting full file details inside Google's official notification. A push notification may only send change headers.
• Expecting direct file attachments, a file picker or Drive search. These features aren't available in the current version yet.
• Expecting a status change from status brackets. Google Drive only links; it doesn't change the status.

Next step: for a read-only feed of your tasks in a calendar, see iCal calendar sync. To connect Dropbox files, review Connect to Dropbox.