Slack is where a startup's day actually happens, so it's the first tool most founders want an agent to touch. It's also the one where a mistake is most visible. A wrong message in a 40-person channel is read before you can delete it.
That's why this connection is worth setting up carefully. It's an agent connection from the catalog, one of the four featured tools with Linear, Notion and GitHub. It doesn't change a module. It gives agents actions they can call in Slack when you ask, and only after you allow it.
Two switches before an agent touches Slack
Connecting Slack stores the authorization so Nautis can talk to it. That's all. An agent still can't read a channel or post a word until someone turns on Agent access for Slack, which is a second, deliberate step.
Right after you connect, a dialog asks Allow agents to use Slack? You can choose Enable for agents or Not now. Choosing Not now is a perfectly good answer if you want to look at the action list first. Tools enabled for agents show a shield icon in the connected rail.
Connect Slack, step by step
- Click your avatar in the top-right corner and choose Integrations. Slack is in the featured row.
- Hover the Slack card and click Connect. Slack's own sign-in and consent screen opens, where you can also check which workspace you're installing into.
- Approve access. You return to Nautis with a Slack connected toast and Slack's detail pane open.
- Pick Enable for agents in the dialog, or come back to it later from the tool's page.
- Open Available actions and switch off anything you don't want agents doing yet.
Only owners and admins can do this. Everyone with read access to Integrations can see that Slack is connected, but the buttons are disabled for them.
Can the Nautis Slack integration post without asking?
Not by default. Each action under Available actions is tagged Read or Write. The exact list comes from Slack's side, and admins can see and toggle each action there. Here's how the rules apply.
| Kind of action | Default | What changes it |
|---|---|---|
| Read, such as reading a channel | Runs without a prompt | Switch that action off under Available actions |
| Posting a message people will read | Waits in the Approval Center with the exact text | Both Connected app actions (Integrations) and AI Copilot external sends (email & social) set to Run without asking |
| Any other write | Waits for approval | Connected app actions (Integrations) set to Run without asking |
| A delete in Slack, if one is listed | Counts as a write | Turn the action off. Deleting always asks covers Nautis records, not connected apps |
The autonomy setting has no per-tool version. Switch connected-app actions to Run without asking for Slack and you've done it for every tool enabled for agents. That's the strongest reason to use the per-action toggles instead.
What Slack controls on its side
Slack apps get access through scopes. Slack's OAuth guide explains that bot scopes give an app its own identity, user scopes let it act as a person, and the installing user approves every scope requested. Scopes granted on later installs add to the earlier ones.
Two scope descriptions explain most surprises. Slack describes chat:write as sending messages as your Slack app. It describes channels:history as viewing messages in public channels that your Slack app has been added to. So if an agent can't read a channel, the app may simply not be in it. Which scopes this connection uses is shown under Permissions it can request on the tool's page.
Your Slack workspace can also block the install. Slack's app approval settings let workspace owners pre-approve or restrict apps, and send requests for review to owners by default.
Workflows that suit Slack
Nudging a blocker
Your 7:00 am Chief of Staff briefing flags a task blocked for four days. You ask the Chief of Staff to post a short nudge in the engineering channel. The card shows the channel and the full text. You soften one word and approve.
Catching up before a call
Before a customer call, ask for a summary of their shared channel. Reading runs without a prompt, and nothing from Slack is stored as a Nautis record unless you save it.
Two workspaces
Some startups run an internal workspace and a separate community one. Add both with Add account. Agents always act through the account marked Primary, so switch it with Make primary before asking for a post in the other one, and rename each account label so nobody guesses.
Troubleshooting Slack
- Slack is connected, but the agent ignores it. Turn on Agent access on the tool's page.
- The agent can't see a channel. Check the action is on, and that the Slack app has been added to that channel.
- The post went to the wrong workspace. Check which account is Primary.
- Status shows Expired. Click Reconnect and sign in again.
- External tools aren't available yet. The integration service isn't configured for your workspace. Contact support.
- A banner says it's showing featured tools. The full catalog is briefly unreachable. Slack still works.
- You asked from WhatsApp. Connected-app actions aren't on WhatsApp yet. Use the app.
Limits
- Nautis doesn't sync or copy Slack. Agents call actions on demand.
- One connection serves the whole organization. Nobody connects a personal Slack for themselves.
- Disconnecting removes Nautis's access and deletes nothing in Slack.
- Approvals take attention. Someone has to review each post in the Approval Center, which is the point and also the cost.
- Every write, automatic or approved, appears in AI Activity. Plain reads don't add entries.
For the full settings, see the Integrations guide and AI Governance.
FAQ
Does Nautis store our Slack messages?
No. Nautis doesn't sync or mirror connected tools. An agent reads what it needs when you ask, and nothing from Slack becomes a Nautis record unless you save it.
Can I let agents read Slack but never post?
Yes. Open Slack under Integrations, go to Available actions and switch off the write actions. A per-action setting overrides the master switch, so reading keeps working.
Who can connect the Nautis Slack integration?
Organization owners and admins. Other members can see the connection and its status, but the Connect button and switches are disabled for them.
Do I need Slack admin rights to connect?
Not always. If your Slack workspace has app approval turned on, a workspace owner or an appointed reviewer has to approve the app first. Otherwise the person installing approves the requested scopes on Slack's consent screen.