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]>
4.4 KiB
seo_title, seo_description
| seo_title | seo_description |
|---|---|
| Resend Connector | Let agents work with Resend email delivery — domains, audiences, and delivery status. Why sending is not a setup test, domain scope, and troubleshooting. |
Resend
Agents can work with your Resend account — checking delivery status, inspecting domains and audiences, and, where you permit it, sending email.
Warning: This connector can reach a real sending pipeline. Mail sent from Resend goes to real inboxes, counts against your plan, and affects your domain's sending reputation. Do not verify this connector by sending a message.
Resend is for programmatic email from your own domains. If you want an agent to have its own inbox and treat conversations as tasks, that is AgentMail. If you want an agent to read your personal mailbox, that is Gmail.
Before you connect
- A Resend account with access to the domains you want agents to work with.
- Verified sending domains, if sending is in scope. Resend requires domain verification through DNS before it will send from an address, and this connector does not change that.
Connect Resend
- Open Connectors and select Resend.
- On the Access step, choose the identity and which agents may use the connection.
- Select Sign in with Resend 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 Resend account's: its domains, audiences, and delivery history.
Separate the operations clearly, because they differ enormously in consequence:
| Operation | Consequence |
|---|---|
| Reading delivery status, domains, audiences | Nothing leaves the building |
| Managing audiences and contacts | Changes who is on a mailing list |
| Sending email | Real mail to real people, immediately and irreversibly |
Danger: Keep send actions Off, or Ask first at the very least. An agent that can send mail unsupervised can email your customers. There is no recall, and a mistake affects your domain reputation as well as the recipients.
Audience changes deserve care too — removing a contact loses a subscription record, and adding one may have consent implications. See Set action permissions.
Try it
Verify with a read:
List the verified sending domains on the Resend account and tell me the delivery status of the most recent email. Do not send anything.
Compare against the Resend dashboard. This confirms the credential and shows you the domain configuration at the same time, with nothing delivered.
Note: A verified domain means Resend has confirmed its DNS, not that this credential may send from it. Whether an agent can actually send depends on the API key's own permissions and on the send action's setting in Paperclip — listing domains tells you neither. Keep those three things separate when you reason about what this connection can do.
If you eventually need to confirm sending, send to an address you personally control, from a domain you own, and only once you have decided the agent should have that capability.
Note: Illustrative task, not a recorded test result.
Troubleshooting and limitations
| Problem | Likely cause | Fix |
|---|---|---|
| No domains are listed | The account has none, or none are verified | Add and verify a domain in Resend |
| Sending is refused | The domain is not verified, or the send action is Off | Verify the domain in Resend; check the Permissions tab |
| Mail sends but does not arrive | Recipient filtering, or domain reputation and DNS records | Check Resend's delivery logs and your SPF, DKIM, and DMARC records |
| An agent emailed someone unexpectedly | A send action was set to Allowed | Set it to Off, and review what was sent in Resend's logs |
| Sends are throttled | Resend's plan rate limits | Check your plan limits |
| Needs attention | The grant was revoked | Select Reconnect |
Limitations: one Resend account per connection. Domain verification is Resend's and cannot be bypassed. Paperclip cannot recall sent mail.
Related guides
- AgentMail — give an agent its own inbox and turn email into tasks.
- Gmail — read an existing mailbox.
- Set action permissions
- Resend remote MCP server