> ## Documentation Index
> Fetch the complete documentation index at: https://docs.trysight.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Slack Integration
> Bring Sight — your AI SEO teammate — into Slack. Ask questions by @mention or DM, approve actions with a tap, and get proactive digests and automation summaries.
## Overview
The **Slack integration** puts Sight AI's agent — a bot named **Sight** — right inside your workspace. Once connected, your team can:
* **@mention Sight** in any channel it's in, or **DM it directly**, to ask about SEO, content, keywords, rankings, and analytics
* **Approve or decline actions** (like generating an article or syncing to your CMS) with **Approve / Decline** buttons — no need to switch to the app
* Get **automation run summaries** posted to channels you choose
* Receive **proactive digests and nudges** about your sites
* See an **App Home** tab that explains what Sight can do
Connect at **Integrations → Slack** (`app.trysight.ai/integrations/slack`).
**Slack is connected once for your entire team — not per site.** A single workspace connection serves every site you choose to expose, with separate controls for which sites are reachable and which channels map to which site.
## Setup
Go to **Integrations → Slack** and click **Connect Slack**, then approve access in Slack's OAuth screen. Only **team owners and admins** can connect, reconnect, or configure Slack.
After connecting, set **site access** to **All sites** (every current and future site) or **Selected sites** (an allowlist). Also pick a **default site for DMs** — the site direct messages answer about.
Invite the bot to any channel where you want it to answer or post (`/invite @Sight` for private channels). Then map channels to sites under **Channel routing** so mentions resolve to the right site.
If you connected Slack before DMs, App Home, or action approvals existed, click **Reconnect** on the Slack settings page to grant the newer permissions.
## Talking to Sight
### @mention in a channel
Mention the bot in any channel it has joined — e.g. *"@Sight what's our top query this week?"* Sight replies **in-thread**, adds a ⏳ reaction while it works, and posts a short, task-specific **"on it"** line that restates what you asked (then updates with progress before settling into the final answer). When it's done, the reaction flips to ✅ (or ❌ if something went wrong). It uses the thread's recent history as context.
### Thread follow-ups — no re-mention needed
Once Sight is part of a thread (you mentioned it, or it replied there), you can keep talking to it **without tagging it again** — *"yes, break that down by page"* just works. Sight reads each new reply in the thread and decides whether it's addressed to it:
* Replies that continue the conversation with Sight (answering its question, follow-up asks, new instructions) get a response.
* Replies aimed at other people — side conversation, or messages @mentioning a teammate — are left alone.
* If it's ambiguous, Sight stays quiet. An explicit **@mention always gets a response**, so tag it whenever you want to be sure.
In threads Sight was **never** part of, and for plain channel messages, only an **@mention** triggers a response. Un-mentioned channel messages are **passively captured** for context — see [Channel awareness](#channel-awareness) — but not answered.
### Direct message
DM the bot to have a private conversation — handy for quick questions that don't belong in a shared channel. DMs use your recent DM history as context and answer about your **default site for DMs** (or your only accessible site).
### Slash commands
Run `/sight` in any channel the bot is in for quick controls (replies are visible only to you):
| Command | What it does |
| ------------------------- | -------------------------------------------------------------------- |
| `/sight` or `/sight help` | Show the command list |
| `/sight status` | Show which site this channel is bound to |
| `/sight workspace` | Bind (or rebind) this channel to one of your sites via a picker |
| `/sight capture` | Show whether Sight is reading this channel for context |
| `/sight capture off` | Stop reading this channel (what was already learned stays available) |
| `/sight capture on` | Resume reading this channel |
| `/sight capture purge` | Delete everything learned from this channel and stop reading |
### Channel awareness
When Sight is added to a channel, it **reads through the recent conversation** to get caught up, and it keeps **passively following** the channel — so it has context on team discussion it was never @mentioned in. Ask things like *"what did the team decide about the blog migration?"* and Sight can recall channel discussion via its conversation memory. Use `/sight capture off` to stop reading a channel, or `/sight capture purge` to wipe what it learned.
Channel awareness is **site-scoped**: a channel is read for the site it's mapped to (or your only accessible site). Map a channel with `/sight workspace` so Sight can learn it.
### App Home tab
Open Sight's **Home** tab in Slack for a quick orientation: what it can help with, example questions, and a **Manage Slack settings** button. Opening the App Home tab doesn't use any AI credits.
## What Sight can do for whom
Sight is a **full agent**, but what each person can do depends on whether their Slack identity is linked to a Sight AI account:
| Who | What they can do |
| --------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Anyone in the workspace** | Ask read-only questions — analytics, rankings, keyword status, visibility, explanations |
| **Linked team members** | Everything above, **plus** propose and run actions that change data (generate/refresh articles, add keywords, sync to CMS, connector actions) — behind an approval step |
Sight links your Slack identity to your Sight AI account automatically by **matching your Slack email to a Sight AI team member**. If your email isn't on the team, Sight stays **read-only** for you.
## Approving actions
When a linked member asks Sight to do something that changes data, it **never runs it silently**. Instead, Sight posts a card with **Approve** and **Decline** buttons and a summary of what it will do:
* **Approve** → Sight runs the action as you and posts the result in-thread.
* **Decline** → nothing happens; the card updates to "Declined."
* Only **linked team members** can approve or decline; the card ignores taps from unlinked users.
* Approval cards **expire after 24 hours** — just ask again if one lapses.
### Progressive autonomy (auto-run)
After you approve the **same kind of action on the same site 3 times**, Sight offers a **"Yes, auto-run it"** button. Accept it and that specific action will run automatically on that site from then on — Sight just notifies you instead of asking. Everything else still goes through the approval step.
## Notifications & proactive updates
### Automation run summaries
Any [automation](/automations/overview) can post a summary to Slack when it finishes — the automation name, whether it completed or failed, and a natural-language recap — with one-click controls right under it:
* **Pause this automation** — stop it from running again until you re-enable it in Sight AI.
* **Retry now** — (on failed runs) re-run the automation immediately.
* **Open in Sight AI** — jump straight to the Automations page.
Choosing a Slack channel for an automation also teaches Sight to associate that channel with the site. Pause/Retry are admin-only actions.
### Proactive system automations
Connecting Slack adds three optional **system automations** to your Automations page. They post to the channel linked to a site and run on a fixed schedule (times are UTC):
| Automation | Schedule | What it posts |
| -------------------------------- | -------------- | --------------------------------------------------------------- |
| **Slack daily digest** | Daily, 13:00 | A short daily recap of search, visibility, and indexing changes |
| **Slack proactive follow-ups** | Mondays, 14:00 | Nudges about stale opportunities, drafts, or visibility drops |
| **Slack automation suggestions** | Mondays, 15:00 | One or two automations worth turning on |
They turn on once a channel is linked to the site, and you can disable any of them from the Automations page. They use read-only tools only.
## Credits
Sight's answers in Slack — channel mentions, thread follow-ups, DMs, and approved actions — use your team's **AI credits**, the same pool as in-app [Agent chat](/ai-content/ai-agents) and automations. If your team runs out of credits, Sight tells you and stops until you top up. App Home, plain notification posts, and the short "on it" acknowledgment don't cost credits.
## Async results
Some actions take a few minutes to finish — notably **article generation**. When you kick off a generation from Slack, Sight posts a "started" reply right away, then **posts the finished article link back into the same thread** when it's ready (or a heads-up if it failed). You don't need to ask "is it done?" — Sight follows up on its own.
## Disconnect
To remove Slack for your whole team, go to **Integrations → Slack** and click **Disconnect**. This revokes the connection and clears channel mappings and site access. Automations with Slack notifications will stop posting until you reconnect.
## Troubleshooting
Slack OAuth isn't configured for this Sight AI deployment, or you're not a team owner/admin. Only owners and admins can connect Slack — ask one to set it up, or contact [support@trysight.ai](mailto:support@trysight.ai).
1. The bot must be a **member of the channel** (`/invite @Sight`).
2. You must **@mention** it to start a conversation — after that, replies in the same thread don't need a re-mention.
3. If you connected Slack a while ago, click **Reconnect** to grant newer permissions (DMs, thread context, identity matching).
Sight only follows threads it's **already part of** (it was mentioned there or replied there), and it deliberately stays quiet when a reply looks aimed at another person or is ambiguous. **@mention it** to guarantee a response.
Channel answers resolve via your **channel → site** mappings. Map the channel to the correct site under **Integrations → Slack → Channel routing**. For DMs, set the **default site for DMs**.
This happens when a channel isn't mapped and your team has more than one accessible site (or multiple Sight teams share the workspace). Map the channel to a site, or ask in a channel that's already linked.
Mutating actions require your Slack email to match a **Sight AI team member**. If it doesn't, Sight stays read-only for you — make sure your Slack account uses the same email as your Sight AI account, then reconnect.
Check, in order: Slack is connected; the site is in the access list; the bot is in the chosen channel; and Slack notifications are enabled on the automation with a channel selected.
## Related
* [Automations overview](/automations/overview)
* [Monitoring & troubleshooting](/automations/monitoring-and-troubleshooting)
* [MCP Connectors](/integrations/mcp-connectors) — Sight can use connector tools in Slack too
* [Custom automations](/automations/custom-automations) — use `getSlackStatus` to check channel availability