How to Connect Multiple Slack Workspaces to Perplexity
Perplexity’s Connector for Slack takes one Slack authorization and is worded in the singular throughout, so searching your own Slack and two clients’ from one session runs through Carly. Authorize each workspace in Carly, add Carly to Perplexity once, and every result names the workspace it came from. Carly holds your Gmail and Outlook mailboxes and every calendar on both sides in the same place.
What one chat can do afterwards
- Search your own Slack and a client’s in the same question.
- Show the source workspace and channel on every matching message.
- Post or reply in the workspace you name, not the one that happens to be connected.
- Reach a workspace you joined as a guest, with no admin install to request.
- Produce a daily brief grouped by workspace.
- Route a Slack thread into email, a task and a calendar hold in one pass.
Nothing is merged. Each workspace keeps its own authorization, and every one stays individually addressable.
One correction before anything else
The connector is not Enterprise-only. Perplexity’s help centre article on using the Connector for Slack, updated on 14 August 2026, states that it is available to Perplexity Pro, Perplexity Max, Enterprise Pro and Enterprise Max users. Free is the only tier left out. Plenty of write-ups say otherwise.
Two integrations, pointing opposite ways
The connector page carries a comparison table separating the two, which is worth reading before you install anything.
The Connector for Slack brings your Slack data into Perplexity. Once enabled you can select Slack as a source when running queries in Perplexity sessions, under Settings then Connectors, then Slack under “Set sources for search”. Organization admins can enable or disable it for all users.
The Perplexity Computer Slack app goes the other way and puts Perplexity into Slack, where members DM it or @mention it. It answers a different question from the one on this page: it does not bring several workspaces into one chat, it puts a bot in each workspace separately.
Multiple channels is not multiple workspaces
Every “supports multiple” sentence in Perplexity’s Slack documentation is about channels. The Slack app doc says it supports multiple channels, allowing your organization to integrate Perplexity with several Slack channels simultaneously. That is one workspace with many channels in it, which needs no extra setup at all.
The connector’s scopes cover public channels, private channels, direct messages and group direct messages, plus workspace files, users and canvases. Access is bounded by your own Slack account: Perplexity states the connector respects Slack’s user permissions, so only channels a user can reach in Slack can be reached through Perplexity. Perplexity also says it accesses Slack messages in real time, does not permanently store your Slack data, and deletes context after each query is processed.
The wall: the connector is worded in the singular
No Perplexity page states whether one account can hold two Slack workspaces on the connector. Activation is described in the singular, as being prompted to log in to Slack and grant permissions in the Slack workspace. There is no workspace picker, no “add another account” step, and no multi-account note anywhere in the article. Undocumented is the honest answer, not “no”, and the practical planning assumption is one Slack authorization per Perplexity account.
Writes are real on that one workspace, and they are documented. Perplexity’s connector documentation says it can post findings back to any connected Slack channel, and gives the worked example of creating a Slack post in one channel summarizing what a team did yesterday in another. The listed actions include sending messages on your behalf and creating, editing and removing canvases.
1. Sort your workspaces
| What you have | Native path in Perplexity |
|---|---|
| Several channels in one workspace | Yes, one authorization covers them |
| A second company’s workspace in the same session | Undocumented on the connector |
| A workspace you joined as a guest | No install path without an admin |
| Posting into a named workspace among several | Undocumented beyond one |
| Starting when a Slack message arrives | No, hourly polling at best |
2. Connect every workspace to Carly
- Sign in at carlyassistant.com.
- Open carlyassistant.com/integrations.
- Find Slack and click Connect.
- Authorize the first workspace, checking the name at the top of Slack’s consent screen.
- Return to the integrations page and click Connect on Slack again for the next workspace.
- Repeat for every remaining workspace, including client workspaces you joined as a guest.
Each workspace keeps its own authorization, and Carly reaches only the channels that account can already open. If a workspace restricts app installation, a Slack owner or admin approves Carly once.
3. Add Carly as a custom remote connector
Perplexity shipped Bring Your Own Connector for Pro, Max and Enterprise subscribers in March 2026, which is how Perplexity reaches the workspaces you just authorized:
- Open Settings → Connectors.
- Select + Custom connector.
- Choose Remote.
- Enter a name and
https://carlyassistant.com/mcp/as the MCP server URL. - Choose the authentication option and acknowledge the third-party connector risk.
- Add the connector and finish authorization.
Perplexity’s remote connector guide supports HTTPS servers over Streamable HTTP or SSE. Enterprise administrators can share a connector across the organization and decide whether members may add their own; that member permission is disabled by default. If you are weighing hosted connectors against running a server yourself, the Slack MCP route is a separate decision.
4. Test each workspace read-only
One workspace per prompt until you trust the routing:
In the Databricks client workspace, list the five most recent messages in #project-updates with sender and timestamp. Do not post anything.
In my own workspace, find the newest thread mentioning the renewal date. Give me the channel and the link, and do not reply.
Then the question that a single authorization cannot answer:
Search my workspace, the Databricks workspace and the Adobe workspace for “scope change” in the last 14 days. Show the source workspace and channel on every row.
5. Reuse this routing prompt
Treat my own Slack as Internal, the Databricks workspace as Client, and the founders community as Community. Name the source workspace on every result you return. Never post in a Client workspace without showing me the draft first.
Then name the target on each action:
Post the release note in Internal, channel #announcements. Reply in the Databricks thread only, and do not cross-post.
Where the Slack app helps, and where it stops
If what you want is Perplexity answering questions inside Slack rather than Slack data inside Perplexity, its Slack app is the supported route and it installs per workspace. Three prerequisites gate each install: a Perplexity plan with Perplexity Computer, Slack admin permissions in that workspace, and a paid Slack plan, which Perplexity notes is Slack’s requirement rather than its own.
Both of those last two sit outside your control if you are a guest or a contractor in someone else’s Slack, which is exactly the workspace you most often need to search. Usage also counts against each person’s Perplexity Computer limits, so a busy workspace can run a user out mid-month. If the bot stays silent after an install, Perplexity’s guidance is that installs from before 13 March 2026 may be running an outdated version, and reinstalling fixes it.
The trigger that is really a poll
Scheduled Tasks support any recurring cadence as long as it runs no more often than once per hour, and sub-hourly cadences are listed as not supported. The canonical example is time-based: every Monday at 9am, pull the sales pipeline from Salesforce and post a summary to #revenue in Slack.
Read the wording on the example that sounds like a trigger. “Check my Gmail every hour and notify me when one arrives” is an hourly poll wearing a notification’s clothes. Nothing in Perplexity starts because a Slack message landed.
Perplexity’s Slack integrations versus Carly
| Need | Perplexity | Carly |
|---|---|---|
| Search one workspace deeply from a chat assistant | Yes | Yes |
| Post findings back to a Slack channel | Yes, documented | Yes |
| Canvases and Slack-native message tooling | Yes | Not all of them |
| Hold several workspaces in one session | Undocumented | Yes |
| Reach a workspace you are only a guest in | Needs an admin install | Yes, your own authorization |
| Start when a Slack message arrives | No, hourly at best | Yes |
Carly holds several Slack workspaces at once on your own authorization, names the source workspace on every answer, and acts when the message arrives rather than on an hourly poll: a client posts in a channel, and the follow-up runs then, matched against the email and calendar accounts connected alongside it.
Free Zapier-style workflows; AI agents from $35/month. Connect the workspaces at carlyassistant.com/integrations, then point Perplexity at carlyassistant.com/mcp.
Quick fixes
| Problem | Fix |
|---|---|
| No Slack option in Perplexity | The connector starts at Pro, so a Free account will not show it |
| Installed the wrong one | The connector puts Slack in Perplexity; the Slack app puts Perplexity in Slack |
| The second workspace never appears | Undocumented on the connector; connect both to Carly instead |
| An admin has to install the Slack app | It needs Slack admin rights and a paid Slack plan, which a member cannot self-serve |
| The bot cannot see a channel | Invite it, and remember it still cannot exceed the asking user’s own Slack access |
| No + Custom connector button | On Enterprise, the member permission for custom connectors is off by default |
Frequently asked questions
Is Perplexity’s Slack connector Enterprise-only?
No. Perplexity’s help centre, updated on 14 August 2026, lists the Connector for Slack as available to Perplexity Pro, Perplexity Max, Enterprise Pro and Enterprise Max users. Only the Free tier is excluded.
Can Perplexity connect two Slack workspaces?
Not on the connector, where activation is worded in the singular with no workspace picker and no multi-account note. Authorize each workspace in Carly and add Carly once as a custom remote connector, and one session searches all of them.
Can Perplexity post to Slack, or only read?
It posts. Perplexity’s connector documentation describes posting findings back to any connected Slack channel, lists sending messages on your behalf among its actions, and gives a scheduled task example that posts a summary into a #revenue channel.
Does Perplexity run when a Slack message arrives?
No. Scheduled Tasks run no more often than once per hour and sub-hourly cadences are explicitly unsupported, so even the “notify me when a reply arrives” example is polling underneath. Carly triggers on the message.
Related: Multiple Gmail accounts in Perplexity · Best AI assistants for Slack · Slack MCP · Carly’s Slack integration
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
