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

3.7 KiB

Raw Blame History

seo_title, seo_description

seo_title	seo_description
Todoist Connector	Let agents read and update Todoist tasks. Account and project reach, shared project behaviour, restricting writes, a read test, and troubleshooting.

Todoist

Agents can work with your Todoist tasks — finding them, reading details, and creating or completing them.

Before you connect

A Todoist account with the projects you want agents to use.

That is all. This is one of the simplest connectors to set up.

Connect Todoist

Open Connectors and select Todoist.
On the Access step, choose the identity and which agents may use the connection.
Select Sign in with Todoist 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 authorizing Todoist account's: its own projects, plus any shared projects it has joined. There is no project picker in Paperclip.

Shared projects are worth pausing on. A personal Todoist account often belongs to shared projects with a partner, a team, or a client. An agent with this connection can read and change tasks in all of them, and those changes appear to the other members as coming from you.

If that matters, either connect an account that belongs to fewer shared projects, or keep writes restricted.

To restrict writes, set the create, update, and complete actions on the connection's Permissions tab, leaving reads Allowed. The two settings are not equivalent, and the difference matters here:

Off is read-only. The agent cannot change your tasks at all.
Ask first is not read-only. The agent can still change your tasks; it just has to wait for a person to approve each call. If you approve, the edit happens.

Choose Off if you want an agent that consults your task list and never edits it. Choose Ask first if you want it to propose edits you sign off on. See Set action permissions.

Note: Completing a task in Todoist is a write, and for a recurring task it advances the recurrence. Treat completion as a change rather than a harmless acknowledgement.

Try it

What Todoist tasks are due today? List them with their projects. Do not complete or change anything.

Compare against Todoist. Reading today's tasks confirms the credential and the agent's permission without touching your task list.

Note: Illustrative task, not a recorded test result.

Troubleshooting and limitations

Problem	Likely cause	Fix
A project's tasks are missing	The authorizing account has not joined that shared project	Join it in Todoist; no reconnect needed
An agent changed a task in a shared project	Reach includes shared projects, and writes were allowed	Set writes to Ask first, or connect a more limited account
A recurring task moved unexpectedly	Completing a recurring task advances its recurrence	Adjust it in Todoist and restrict the completion action
A write is rejected	The account's role in a shared project does not permit it	Check the project's sharing settings in Todoist
Some fields are unavailable	Certain Todoist features are plan-gated	Check your Todoist plan
Needs attention	The grant was revoked	Select Reconnect

Limitations: one Todoist account per connection. No project filter inside Paperclip. Shared projects come with the account.

Linear, Jira, Asana — team work tracking rather than personal tasks.
Set action permissions
How connector access works
Todoist developer documentation

3.7 KiB Raw Blame History