Skip to content
threada Docs

Google Workspace setup and support

Threada for Google Workspace starts with a runtime-bound Google Chat intake path for creating governed Threada WorkItems from Google Chat. The first reviewable app is intentionally narrow: it supports a Google Chat slash command, a Help quick command, setup-required feedback, and safe links back to Threada. It does not read Gmail, Drive, Calendar, Admin SDK data, broad Google Chat message history, or execute third-party actions directly from Google Chat.

This guide supports private Google reviewer testing once a review package is available and public Google Workspace users after Google approves and lists the app. Until the Google Workspace Marketplace app is approved, the Google Chat runtime path remains a tenant-bound integration and should not be treated as the public Google Workspace Marketplace app.

Start Threada-side runtime setup from https://studio.threada.ai/integrations/google-workspace/install when a reviewer or tenant admin needs to bind the Google Workspace runtime integration record to a pack. This setup handoff does not replace Google Workspace Marketplace installation, Google Cloud app configuration, OAuth consent review, or Marketplace approval.

Requirements

Before installing or testing the Google Chat app, make sure you have:

  • An active Threada tenant.
  • Studio or Admin access for the Threada workspace that should receive Google Chat WorkItems.
  • Permission to install Google Chat apps in the target Google Workspace domain, or a Google Workspace administrator approval path.
  • For private reviewer testing, the exact Google Chat app configuration and setup notes provided through the approved Google review channel.
  • A configured Google Workspace domain, Chat space, or user mapping in Threada for the reviewed app package.

Do not use production customer Google Workspace domains, customer messages, raw Chat exports, or screenshots containing private tenant data for Marketplace review evidence.

Install the Google Chat app

After Google approves the public app, install Threada from the Google Workspace Marketplace or the Google Chat app install surface. During private review, use only the Google Cloud, Marketplace SDK, or reviewer instructions provided in the approved review notes.

  1. In Google Chat, open the app install surface or the direct Marketplace install link provided for the reviewed app.
  2. Search for Threada, or use the private reviewer install path when testing an unpublished package.
  3. Add the app to a direct message or to the intended Chat space.
  4. If Google Workspace says administrator approval is required, complete the admin approval or allowlist flow before testing.
  5. Confirm the app sends a welcome message after it is added.

If a private app cannot be installed, stop and fix the Google Cloud project, Google Chat API configuration, Marketplace SDK settings, OAuth consent posture, or domain install policy before continuing.

Connect Google Chat to Threada

The Google Chat app must be mapped to a Threada tenant and receiving workspace before Chat users can create WorkItems.

  1. Sign in to Threada Studio with an admin or builder account.
  2. Start from https://studio.threada.ai/integrations/google-workspace/install, or open the workspace or pack that should receive Google Chat-created WorkItems.
  3. Open the integration or channel setup area for Google Workspace.
  4. Bind the installed Google Workspace domain, Chat space, or user context to the Threada workspace or pack.
  5. Select the receiving queue or routing policy.
  6. Save the mapping and run the connection test if one is available.

If the reviewed build does not yet expose a self-service Studio mapping UI, follow the reviewer setup notes for the exact domain, Chat space, Threada workspace, and queue prepared for review. Do not infer tenant mappings from domain names, Chat space display names, or user emails alone.

Create a WorkItem from Google Chat

The v1 app exposes two WorkItem intake paths:

  • Slash command: use /create followed by a short request.
  • Help quick command: choose Help from the command menu to see setup, support, and WorkItem creation guidance.

For reviewer testing, use a short request such as:

/create Need vendor security review for ExampleCo before Friday.

In spaces, mention Threada when sending a message to the app. Threada should not respond to every ordinary space message.

After a successful request, Google Chat should show a clear success response and a safe Threada Work link when available. Open the WorkItem in Threada and confirm the source context is preserved, routing is correct, and the audit timeline records the intake event.

Setup-required responses

If the Google Chat app is installed but not connected to a Threada tenant or workspace, the app should show a setup-required response instead of silently dropping the request.

Common setup issues:

  • The Google Chat app was installed in a domain, direct message, or space that is not mapped in Threada.
  • The mapped Threada workspace or pack was disabled.
  • The receiving queue or routing policy is missing.
  • The app package still uses placeholder Google Cloud project, endpoint, avatar, or Marketplace listing values.
  • The Google Chat API endpoint is unavailable, not reachable over HTTPS, or points to a development or staging environment.
  • OAuth consent or Marketplace SDK scope settings do not match the reviewed app.

For review builds, include the Google Workspace domain, Chat space, command time, and sanitized error text in support requests. Do not send OAuth client secrets, service-account keys, access tokens, cookies, raw Chat event payloads, or private message content.

Disconnect or uninstall

To stop Google Chat-created WorkItems:

  1. In Threada Studio, disable or remove the Google Workspace mapping for the workspace, pack, domain, space, or user context.
  2. In Google Chat, remove the Threada app from the relevant direct message or space if it is no longer needed.
  3. Run a test command and confirm Google Chat returns setup-required feedback rather than creating a new WorkItem.

For public installs, use the Google Workspace Marketplace or Google Chat uninstall controls available to your domain or user account. Threada should preserve audit history for WorkItems already created before disconnect.

Data handling

The v1 Google Chat app should send Threada only the Chat context needed to create and route a WorkItem. Threada should store Google Chat provenance as source metadata, channel IDs, tags, or equivalent audit context rather than raw Google exports.

The v1 app does not request Gmail, Drive, Calendar, Admin SDK, domain-wide delegation, broad Chat message history, or restricted Google scopes. If a future version adds a Workspace add-on or requests sensitive or restricted Google scopes, Threada must update this guide, explain the exact scope use, complete Google’s OAuth verification or security assessment where required, and submit the updated app for review before marketing the new capability.

Support

For setup help, contact support@threada.ai. For security concerns, use the security contact listed on Threada’s public security page or privacy policy.

Include the Threada tenant, Google Workspace domain, Chat space or direct message context, approximate command time, and sanitized error text. Do not send secrets, tokens, cookies, raw event payloads, customer exports, or private message content.