39633c2217
Connector catalog, setup guides, and shared access documentation, followed by a final code-accuracy repair pass. This PR does not change application behavior. ## Final accuracy pass Checked against shipped Paperclip `v2026.916.0`, commit `dffc2b3ca1b9e88fa21cb17493083e682dffd1ca`, rather than the dirty local checkout or the earlier canary baseline. - Corrects connector/method-specific identity choices, human audiences, and managed GitHub versus PAT scope and verification. - Explains that **Always allow** covers different arguments for the same agent/action/connection, with project scope when present; uses actual button labels and removes the test-panel control from review instructions. - Qualifies new-action quarantine, including safe-default read exceptions. Removes unconditional approval guarantees. - Separates provider channel/repository reach from Paperclip sender authorization. - Completes sandbox sign-in and model credential-selection instructions from the current UI implementation. - Repairs Notion's hub summary, removes incomplete optional Notion/Sentry client-registration procedures, and corrects Linear's provider-versus-Paperclip attribution. - Removes unsupported Postman tier claims, contradictory Cloudinary/Mem0 verification assertions, API-equivalence claims, and overbroad successful-test assurances. - Retains Supabase's required project reference: both released method definitions explicitly require it. An earlier review suggested otherwise; release code is authoritative here. - Updates the release baseline and removes draft commit chronology from the public introduction. ## Availability and remaining runtime gates - **Google:** Verification is pending. Per the product-owner clarification, authorization can continue where Google offers an Advanced option; this is not available for every account and does not override Workspace policy or other Google prerequisites. Notices on the hub and all Google guides now distinguish an unverified-app warning from blocked authorization. - **Slack is available but not yet fully functional; follow-up fixes are planned.** For agent tools, the released OAuth endpoint/scope defaults differ from Slack's documented MCP contract. The page now warns against treating that route as production-ready and removes the misleading bot-scope walkthrough. Chat-channel bot setup remains separate. Engineering must reconcile the integration and run OAuth plus one read before removing this warning. Source: https://docs.slack.dev/ai/slack-mcp-server/ - No credentialed connector run was performed in this pass. Code consistency, provider documentation, UI rendering, and successful live execution are separate evidence levels. No claim of runtime certification for all connectors. ## Validation - Root build: 253 crawlable documentation pages. - Full `docs:test`: all eight suites passed locally, including root/subpath routes, sitemap history, fingerprints, navigation, skill source blocks, crawlable links, doc-link resolution, and SEO metadata. - Internal-link lint: 258 Markdown files; no broken internal links. - Latest cleanup: full build, all eight docs:test suites, internal-link lint and diff whitespace checks passed; 1,878 link-resolution checks. - Fixed the Calendar MCP reference URL; browser-checked the five inconclusive external destinations (Miro article loads; Asana, Google Cloud, OpenAI and xAI reach sign-in/console screens). Authenticated destinations were not tested beyond those screens. - Replaced the Sandbox providers editorial TODO with a scope note and removed the CLI overview's unfinished-guide announcement. - Browser client navigation: 687 checks passed using installed Chrome. Initial launch lacked the downloaded Playwright browser; rerun used `DOCS_CHROMIUM_PATH` without changing the tests. - Nine representative connector/shared pages at 1440px and 390px: HTTP 200, one article H1, no page-level horizontal overflow. Mobile screenshot inspected; approval page opened in the Codex browser. - Navigation audit reports three existing non-connector orphan files; this patch does not alter those files or their navigation. The previous revision's provider-page expansion, Google shared setup guide, navigation additions, and accidental node_modules-symlink cleanup remain in this PR. Internal review ledgers remain outside the publication branch. No merge or production deployment authorized. --------- Co-authored-by: DevRel Gemini <[email protected]> Co-authored-by: Paperclip <[email protected]> Co-authored-by: Claude Opus 5 (1M context) <[email protected]> Co-authored-by: Michael Nguyen <[email protected]>
6.9 KiB
seo_title, seo_description
| seo_title | seo_description |
|---|---|
| Google Chat Connector | Let agents search and read Google Chat conversations, and optionally send messages. This is a tool connector, not a way for people to chat with an agent. |
Google Chat
Warning: Google verification pending. Paperclip has not yet completed Google app verification. You may see an unverified-app warning during authorization. If Google offers an Advanced option to continue to Paperclip, you can choose to proceed after reviewing the requested access. This option is not available for every account; Workspace administrator restrictions and other Google access requirements still apply. Contact [email protected] if you cannot connect.
Agents can search Google Chat conversations and read messages, and on a sending connection post messages to spaces the authorizing account belongs to.
This is a tool connector: an agent reads and writes Chat using your Google account. It is not a channel for people to start work by messaging an agent — Google Chat is not one of Paperclip's conversation channels. If that is what you want, see Slack, Discord, Microsoft Teams, or Telegram.
Warning: Google Chat needs Google Workspace Developer Preview registration before it will authorize. Google must register the Workspace email that signs in, and the Cloud project that owns the OAuth client if you bring your own. Apply first at Google Workspace Developer Preview.
Before you connect
- A Google Workspace account that already belongs to the spaces you want agents to read, with Developer Preview registration confirmed.
- Personal Google accounts do not have Google Chat spaces in the Workspace sense; this connector expects a Workspace account.
Decide your setup path now
This is the gate worth checking before anything else, because the two paths cost very different amounts of work:
| Path | What it takes | Offered when |
|---|---|---|
| Connect with Paperclip | Sign-in only, no Cloud console work | Only when the instance is enrolled with Paperclip Cloud and Cloud advertises the Chat profile. If it is not on the setup screen, it is unavailable to you |
| Use your own Google OAuth app | A Cloud project with the Chat API and Chat MCP API enabled, a registered callback URI, and a configured Chat app | Always |
Chat is the one Google connector that needs a configured Chat app, not merely an enabled API. In the Cloud console, open Chat API → Configuration and complete the app's identity — app name, avatar URL, and description — then set its functionality and visibility. Google will not authorize against a Chat API with no configured app, and the failure appears at the consent screen rather than earlier.
Set up your own Google OAuth app is the full procedure, including this step.
Pick a capability group
| Group | What agents can do | Scopes requested |
|---|---|---|
| Read only | Search conversations, list and search messages | chat.spaces.readonly, chat.memberships.readonly, chat.messages.readonly, chat.users.readstate.readonly |
| Read & send | The above, plus send a message | the read scopes, plus chat.messages.create |
The group is fixed for the life of the connection.
Connect Google Chat
- Open Connectors and select Google Chat.
- On the Access step, choose the identity and which agents may use the connection.
- Choose the capability group, then the path you settled above — Connect with Paperclip, or Use your own Google OAuth app with the client ID and secret from Set up your own Google OAuth app.
- Complete Google's consent screen with the registered Workspace account.
Choose access
Which conversations an agent can reach is decided by Google: the spaces and direct messages the authorizing account is a member of. Paperclip has no space picker. To narrow it, authorize with an account that belongs to fewer spaces.
Reviewed operations:
| Operation | Group |
|---|---|
search-conversations, list-messages, search-messages |
Both |
send-message |
Read & send only |
Warning: A sent message is visible to everyone in the space and arrives under the authorizing account's name, not an agent's. The connector's guidance is that sending should be approved — leave
send-messageon Ask first.
How connector access works covers identity and agent selection.
Try it
Pick a space the authorizing account belongs to and a recent message in it whose sender and wording you can see for yourself. Then:
In the Google Chat space "deploys", find the most recent message and tell me who
sent it and when. Do not send a message.
Expect the sender and timestamp you can already see in Chat. Matching a specific known message is the point — a plausible-sounding summary is not evidence the agent read anything.
If you must confirm sending, post to a space created for the purpose that contains only you. A direct message "with yourself" is ambiguous in Chat and a poor test target; a scratch space is unambiguous and equally harmless.
Note: Illustrative task, not a recorded test result.
Troubleshooting and limitations
| Problem | Likely cause | Fix |
|---|---|---|
| Google refuses before the consent screen | Developer Preview registration is incomplete | Finish registration and retry |
| Authorization fails on a self-managed client | No Google Chat app is configured in the Cloud project | Configure the Chat app, then retry |
| Connect with Paperclip is not offered | The instance is not enrolled with Paperclip Cloud, or Cloud is not advertising the Chat profile | Use your own Google OAuth app |
| A space is missing from results | The authorizing account is not a member of it | Join the space in Google Chat; no reconnect needed |
send-message is absent |
The connection was made with Read only | Make a connection with Read & send |
| People expect to message an agent and get no reply | Google Chat is not a Paperclip conversation channel | Use a supported channel instead |
| Needs attention | The Google token expired or was revoked | Select Reconnect |
Limitations: one connection covers one Google account. Creating, joining, or leaving spaces and changing memberships are not exposed. Reactions, message editing, and deletion are not available. Developer Preview applies.
Related guides
- Slack, Discord, Microsoft Teams, Telegram — channels people can use to reach an agent.
- Google Workspace Search — one read-only search across Gmail, Drive, Calendar, and Chat.
- How connector access works
- Google Chat API MCP reference