paperclipai/paperclip-docs

0 Fork 0

mirror of https://github.com/paperclipai/paperclip-docs.git synced 2026-11-07 14:21:18 -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.0 KiB

Raw Permalink Blame History

seo_title, seo_description

seo_title	seo_description
Cloudinary Connector	Let agents search and manage Cloudinary assets. What the asset-management connection covers, role-based limits, billing-relevant actions, and troubleshooting.

Cloudinary

Agents can search and manage the media assets in your Cloudinary product environment — finding images and video, reading metadata, and working with your asset library.

This connection is Cloudinary's asset-management surface. It is about finding and organizing assets, not a general interface to every Cloudinary feature.

Before you connect

A Cloudinary account with access to the product environment you want agents to use.
The roles on the signing-in user matter: Cloudinary limits what the connection can do to what that user's roles permit. Decide which user authorizes before you connect.

Connect Cloudinary

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

Paperclip registers its client automatically, so there is nothing to configure in a developer console.

Choose access

Reach is the signed-in user's product environment, and authorization is limited by that user's Cloudinary roles. A read-only Cloudinary role is the cleanest way to give an agent search without change.

Separate three kinds of operation when you set permissions:

Operation	Consequence
Searching and reading asset metadata	Changes nothing in your library
Uploading or modifying assets	Changes your asset library
Deleting assets	Removes media that live sites may reference

Warning: Deleting an asset can break every page that embeds it, and deletions are not reversible from Paperclip. Keep deletion Off. Uploads and transformations consume storage and transformation quota, which has a billing effect on your Cloudinary plan.

Note: Reads change nothing, but do not assume they are free. API calls count against your Cloudinary plan's own rate and usage limits, and how those are metered is Cloudinary's business, not Paperclip's. Check your plan if an agent will be reading at volume.

See Set action permissions.

Try it

Search Cloudinary for assets tagged "product-hero" and tell me how many there are and the public ID of the newest one. Do not upload, transform, or delete anything.

Compare against the Cloudinary media library. Check the returned IDs against known assets and inspect the task's connector activity. Searches do not change assets, but still consume provider requests and may count toward usage limits.

Note: Illustrative task, not a recorded test result. Substitute a tag from your own library.

Troubleshooting and limitations

Problem	Likely cause	Fix
Authorization succeeds but little is available	The signed-in user's roles are limited	Check the user's roles in Cloudinary
The wrong assets appear	The account has several product environments and another was selected	Reconnect with the intended environment
An action is refused	The user's role does not permit it	Adjust the role in Cloudinary, or leave the capability off
An asset disappeared from a live site	A delete action was allowed and ran	Restore from Cloudinary backups if enabled, then set deletion to Off
Quota or billing rose unexpectedly	Uploads or transformations consumed plan resources	Review usage in Cloudinary and restrict those actions
Needs attention	The grant was revoked	Select Reconnect

Limitations: one product environment per connection. Role-based limits are Cloudinary's, not Paperclip's. Deletion is not recoverable from Paperclip.

Google Drive, Box — general file storage rather than media assets.
Set action permissions
How connector access works
Cloudinary MCP documentation

4.0 KiB Raw Permalink Blame History