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]>
5.6 KiB
seo_title, seo_description
| seo_title | seo_description |
|---|---|
| Google Workspace Search Connector | One read-only search across Gmail, Drive, Calendar, and Chat. When to use it instead of the single-app connectors, what it requests, and a test. |
Google Workspace Search
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.
One read-only search that spans Gmail, Drive, Calendar, and Chat together, so an agent can answer "where did we discuss this?" without knowing which app holds the answer.
It searches all four. There is no way to connect it for a subset.
Warning: This connection requests read access to Gmail, Drive, Calendar, and Chat at once. That is broader than any single-app connector. If an agent only needs one app, connect that app instead.
When to use this instead of an app connector
| You want | Use |
|---|---|
| To find something without knowing which app it is in | This connector |
| To read, edit, or create in one specific app | Gmail, Google Drive, Google Calendar, or Google Chat |
| The narrowest possible access | The single-app connector, with its read-only group |
This connector only searches. It returns results with links; it does not read a full document, create a draft, or change an event. Agents that need to act on what they find also need the relevant app connector.
Before you connect
- A Google Workspace account whose mail, files, calendar, and chat you are willing to make searchable.
- Google Workspace Developer Preview registration for that account, confirmed by Google. Apply at Google Workspace Developer Preview.
- Without Paperclip Cloud enrollment, your own Google OAuth client with the Gmail API, Drive API, Calendar API, Chat API, and Workspace MCP API enabled — five APIs, more than any single-app connector needs. Set up your own Google OAuth app is the complete procedure.
Connect Google Workspace Search
- Open Connectors and select Google Workspace Search.
- On the Access step, choose the identity and which agents may use the connection.
- Select Connect with Paperclip, or Use your own Google OAuth app — the latter needs the client ID and secret from Set up your own Google OAuth app.
- Complete Google's consent screen with the registered Workspace account.
One capability group, Search Workspace, requesting gmail.readonly, drive.readonly, calendar.readonly, and chat.messages.readonly. There is a single operation, search-corpus.
Choose access
What the search covers is what the authorizing account can already see across those four apps — its own mail, files shared with it, calendars on its list, and spaces it belongs to. Paperclip does not narrow it, and there is no per-app or per-folder filter.
Because the scope is wide, the agent-selection choice matters more than usual. Prefer Just agents I pick. An Organization identity here lets eligible agents search the connected account on runs whose responsible person is in the credential's human audience — rarely what you want.
How connector access works covers identity and agent selection.
Try it
Search for something you know exists and can recognize in the results:
Search my Google Workspace for "renewal contract" and tell me which app each result came from.
Expect a handful of results, each identifying its source app with a link. Compare each result with a known item and inspect the connector calls. One query verifies only the returned results; it does not establish that all four services were searched successfully.
Note: Illustrative task, not a recorded test result. Use a phrase you know appears in your own mail or files.
Troubleshooting and limitations
| Problem | Likely cause | Fix |
|---|---|---|
| Google refuses before the consent screen | Developer Preview registration is incomplete | Finish registration and retry |
| Connect with Paperclip is not offered | The instance is not enrolled with Paperclip Cloud, or Cloud is not advertising the search profile | Use your own Google OAuth app |
| Results only ever come from one app | The query matches in one corpus, or the account has little content in the others | Try a phrase you know appears elsewhere |
| A result is found but the agent cannot read the whole item | Expected — this connector searches, it does not read | Add the relevant app connector |
| You need a connection dedicated to Drive | This connection requests access across multiple Workspace services | Use Google Drive and review its scopes and actions |
| Needs attention | The Google token expired or was revoked | Select Reconnect |
Limitations: read-only and search-only, using one authorized account. Results depend on Google's search tools and that account's access. Developer Preview applies.