paperclipai/paperclip-docs

0 Fork 0

mirror of https://github.com/paperclipai/paperclip-docs.git synced 2026-11-07 06:16:07 -10:00

Files

T

39633c2217 docs: connectors catalog, operator-first third revision (#124 )

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]>

2026-09-16 22:19:14 -10:00

4.2 KiB

Raw Permalink Blame History

seo_title, seo_description

seo_title	seo_description
Netlify Connector	Let agents work with Netlify teams and sites. Reading deploy status versus starting a deploy, team scope, a read test, and troubleshooting.

Netlify

Agents can work with your Netlify teams and sites — checking deploy status, inspecting configuration, and investigating build failures.

Before you connect

A Netlify account with access to the team and sites you want agents to use.
If you belong to several Netlify teams, know which one you want. Reach follows the account, and there is no team picker in Paperclip.

Connect Netlify

Open Connectors and select Netlify.
On the Access step, choose the identity and which agents may use the connection.
Select Sign in with Netlify and complete browser sign-in.

Paperclip registers its client with Netlify automatically, so there is nothing to set up in a developer console.

Choose access

Reach is the authorizing Netlify account's: the teams it belongs to and the sites within them, subject to Netlify's own role permissions.

The distinction that matters here is between observing a deploy and causing one:

What an agent does	Consequence
Reads deploy status, logs, and build history	Nothing changes. Safe to leave Allowed
Reads site and environment configuration	May expose environment variable names, and sometimes values
Starts a deploy	Depends on the target — see below
Changes site configuration	Can change how the production site builds and behaves

Not every deploy is a production deploy. Netlify distinguishes production deploys from deploy previews and branch deploys, and only the first replaces what visitors see. Treat that as a reason to be careful about which deploy an agent can trigger, not a reason to assume every deploy is safe or that every deploy is live — check what a given action targets before allowing it.

Warning: A production deploy puts code in front of real users, and a configuration change can break a site. Keep deploy and configuration actions on Ask first or Off. Reading build logs to diagnose a failure is the common, safe use of this connector; triggering the rebuild is the part a person should approve.

Netlify environment variables frequently hold API keys. An agent that can read site configuration may surface them, so prefer Just agents I pick for a connection with configuration access. See Set action permissions.

Try it

List the Netlify sites this account can see, and tell me the status and time of the most recent deploy for one of them. Do not start a deploy.

Compare against the Netlify dashboard. A deploy-status read is the natural first check because it is also the connector's most common real use.

Note: Illustrative task, not a recorded test result.

Troubleshooting and limitations

Problem	Likely cause	Fix
A site is missing	The authorizing account is not a member of that team	Add it to the team in Netlify; no reconnect needed
An action is refused	The account's Netlify role does not permit it	Adjust the role in Netlify, or leave the capability off
A deploy started unexpectedly	A deploy action was set to Allowed	Set it to Ask first. Recovery is yours to do in Netlify — cancel the running build, or publish a previous deploy. Paperclip does not roll anything back
Build logs are truncated	Netlify's own log retention and size limits	Check the full log in the Netlify dashboard
An expected capability is absent	Netlify's server does not expose it	Use Refresh actions; otherwise it is unavailable
Needs attention	The grant expired or was revoked	Select Reconnect

Limitations: one Netlify account per connection. No team or site filter inside Paperclip. Paperclip cannot roll back a deploy — do that in Netlify.

Cloudflare — another hosting and infrastructure connector.
GitHub — the repository side of a deploy workflow.
Set action permissions
Netlify agent setup guides

4.2 KiB Raw Permalink Blame History