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]>
7.4 KiB
seo_title: Slack Connector seo_description: Two independent Slack setups: Slack as an agent tool, or as a channel people use to reach an agent. Which to pick, how to set up each, and fixes.
Slack
Slack does two unrelated jobs in Paperclip, and they are separate connections with separate credentials.
Warning: Slack is available, but it is not yet fully functional. Follow-up fixes are planned. Review the agent-tool limitations below before relying on it for production work; the separate chat-channel route is experimental.
Which do you want?
| If you want | Set up | What it gives you |
|---|---|---|
| Agents to search Slack and post messages as part of their own work | Use this connection as an agent tool | Slack actions an agent can call, governed by action permissions |
| People to start and continue work by talking to an agent in Slack | Chat with an agent | A Slack app that turns mentions and DMs into Paperclip tasks |
Connecting one does not connect the other. They need different credentials and prerequisites. Check the agent-tool compatibility notice before planning to use both.
Slack as an agent tool
An agent uses a Slack workspace credential to search messages, read channel lists, and post — on its own initiative, inside its own task.
Agent-tool compatibility notice
The Slack agent-tool route is available but has known compatibility limitations in v2026.916.0. That release configures OAuth endpoints and scopes that differ from Slack's current hosted MCP requirements. A successful bot installation does not verify an MCP connection.
Slack MCP requires a registered internal or marketplace-published app, user-token OAuth endpoints, and the user scopes for the intended tools. See Slack's MCP authentication requirements. Bot-token setup is for the separate chat-channel path below.
Wait for a release with verified Slack MCP compatibility, or contact [email protected] before attempting this route. The access notes below explain the intended tool behavior; they are not a record of successful setup on this release.
Access and actions
Channel reach is Slack's decision: the authorized token sees what its scopes and the workspace allow, and private channels require the authorizing user or bot to be a member. Paperclip does not have a channel picker, so narrow access on the Slack side.
Slack's server supplies the action list. Posting is classified as a write, so leave it on Ask first unless you want an agent posting to a shared workspace unprompted. Open the connection's Permissions tab for the live list. See Set action permissions.
Try it
Search Slack for the most recent message mentioning "deploy" and tell me which channel it was in. Do not post anything.
A read confirms the credential without putting a message in front of colleagues.
Note: Illustrative task, not a recorded test result.
Slack as a channel
People mention the agent in a channel or send it a direct message, and Paperclip creates a task. Replies come back in the thread.
Before you connect
- Chat connectors must be switched on for the instance. It is an experimental setting, off by default, enabled by an instance administrator under experimental settings.
- A publicly reachable HTTPS address for the instance. Slack delivers events by calling Paperclip; this route does not use Slack's socket mode.
- Permission to create and install a Slack app in the workspace.
- The agent that will answer.
Connect it
- Open Connectors, select Slack, then Chat with an agent.
- On the Access step, choose the identity and which agents may use the connection.
- Paperclip generates a Slack app manifest containing exactly the scopes, events, and request URL this route needs. Copy it.
- At Slack API apps, create an app from the manifest rather than configuring scopes by hand, then install it in the workspace.
- Back in Paperclip, paste the Bot User OAuth Token (it starts with
xoxb-) and the Signing Secret. - Choose the agent that will answer, and finish.
Use the generated manifest. It is the supported configuration, and hand-picking scopes is the most common reason a channel setup half-works.
Danger: The bot token and signing secret are full credentials for the app. Paste them only into Paperclip. If either leaks, rotate it in Slack and reconnect.
How a conversation becomes work
| In Slack | In Paperclip |
|---|---|
| Someone mentions the agent in a channel | One task per new mentioned thread |
| Someone sends the agent a direct message | The agent replies in the DM |
| The conversation continues in the thread | It continues on the same task |
Paperclip acknowledges with a reaction so people can see a message was picked up before the agent has finished thinking.
Access
Provider channel or repository access determines where a message can reach the integration; it does not by itself authorize agent work. Paperclip also checks the sender's linked identity and company membership. Linked users must be active non-viewer members. Unlinked senders depend on the connection's Allow unlinked people setting and any sponsor requirements. Review these controls before inviting people to use the agent.
Try it
- Invite the app to a private channel you control.
- Mention it:
@YourAgent hello, can you confirm you are connected? - Expect a reaction, then a threaded reply, and a matching task in Paperclip.
Note: Procedure, not a recorded test result. Use a private channel for the first attempt.
Troubleshooting
| Problem | Likely cause | Fix |
|---|---|---|
| Chat with an agent is not offered | Chat connectors is off for the instance | Ask an administrator to enable it |
| The tool route asks for a client ID and secret | Expected — Slack requires your own OAuth app on this route | Register the app in Slack's console |
| Slack refuses to install the app | The workspace restricts app installation or requires approval | Ask a workspace administrator |
| The channel app is installed but silent | Slack cannot reach the instance, or the app was not created from Paperclip's manifest | Confirm the public HTTPS address, then recreate the app from the manifest |
| A mention in a channel does nothing | The app is not a member of that channel | Invite it to the channel |
| Private channel content is missing on the tool route | The authorizing identity is not a member | Add it to the channel in Slack |
| Signature verification failures | The signing secret does not match the installed app | Copy the current signing secret and reconnect |
| Connecting the channel did not give agents Slack actions | The two routes are independent | Set up the tool connection as well |
Limitations
One workspace per connection on either route. No channel picker in Paperclip on either route. The channel route needs public ingress and does not support socket mode. Private channels require explicit membership.
Related guides
- Discord, Microsoft Teams, Telegram — other conversation channels.
- GitHub — the other mixed-purpose connector, with the same tool-versus-channel split.
- How connector access works
- Set action permissions
- Slack app quickstart