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]>
3.7 KiB
seo_title, seo_description
| seo_title | seo_description |
|---|---|
| Wix Connector | Let agents work with your Wix sites. Site selection, why the connector is narrower than the Wix editor, a read test, and troubleshooting. |
Wix
Agents can work with your Wix sites — reading site information and working with the business data Wix exposes, such as CMS collections and store or booking records where your site has them.
Note: The connector is considerably narrower than the Wix editor. Wix's product surface is large, and what an agent gets is what the hosted server exposes for your sites — not every feature you can reach by clicking around in Wix. Read the connection's action list before planning work around it.
Before you connect
- A Wix account with access to the sites you want agents to use.
- The right role on those sites. Wix distinguishes site owner from contributor roles with varying permissions, and the connection inherits whatever the authorizing account has.
Connect Wix
- Open Connectors and select Wix.
- On the Access step, choose the identity and which agents may use the connection.
- Select Sign in with Wix and complete browser sign-in, choosing the site when Wix asks.
Paperclip registers its client automatically, so there is nothing to configure in a developer console.
Choose access
Site reach is the authorizing Wix account's, subject to its role on each site. There is no site picker in Paperclip beyond what Wix asks during authorization.
What the connection can actually do varies by site, because it depends on which Wix business solutions that site uses. A site with Wix Stores exposes commerce data; a plain marketing site does not. Do not assume a capability exists because Wix offers the product — check the connection's action list for the site you connected.
Writes reach a live site's data:
Warning: Content and business-data changes can appear publicly, and commerce or booking records are real business records. Keep writes on Ask first and anything that deletes records Off. Recovery is whatever Wix's own history provides.
Try it
Tell me the name and published status of the connected Wix site, and list its CMS collections if it has any. Do not change anything.
Compare against the Wix dashboard. This confirms the credential and the site, and the collection list tells you what the connection can actually reach for that site.
Note: Illustrative task, not a recorded test result.
Troubleshooting and limitations
| Problem | Likely cause | Fix |
|---|---|---|
| A site is missing | The account lacks a role on it, or it was not chosen during authorization | Get access in Wix, or reconnect and select it |
| An expected capability is absent | The site does not use that Wix business solution, or the server does not expose it | Check which solutions the site has enabled |
| An action is refused | The account's contributor role does not permit it | Adjust the role in Wix |
| A change appeared on the public site | The data is live content | Revert in Wix, then set writes to Ask first |
| A record was deleted | A destructive action was allowed | Check Wix's own history for recovery; set deletions to Off |
| Needs attention | The grant was revoked | Select Reconnect |
Limitations: one Wix account per connection. Capabilities vary by site depending on the business solutions it uses. Narrower than the Wix editor.
Related guides
- Webflow — another website platform connector.
- Shopify — for storefront commerce specifically.
- Set action permissions
- Wix MCP server