What Slack adds to Halo
Slack is the most common notification destination in Halo, plus a channel for AI agents to operate in:| Mode | What it does |
|---|---|
| Ingest | Channel conversations and team context can be pulled in for the AI to learn from. |
| Actions | Agents can post into Slack channels via the post_message tool. |
| Notifications | Slack is the central sink for Halo notifications — new tickets, escalations, sentiment alerts, integration events, digests. |
Setup
Connecting
Click Connect Slack. You’ll be redirected to Slack’s OAuth consent screen. The required scopes include:chat:write— post messageschannels:read,channels:join,channels:history— read public channelsgroups:read,groups:history— read private channelsapp_mentions:read— react to @halo mentionsusers:read,users:read.email— identify Slack usersreactions:write— add reactions
Mapping channels
To have a Halo agent answer in a Slack channel:- Go to AI Agents > [Your Agent] > Channels > Slack
- Map the channels where the agent should respond
- The agent only answers in mapped channels — DMs are blocked by design
#support to the support agent, #sales-questions to the sales agent).
Ingest mode
When ingest is on:- Channel conversations — messages in mapped channels feed the AI’s awareness of team context
- Channel history — on initial mapping, Halo can pull up to 500 historical messages from a channel, summarize them, and add as customer-scoped knowledge
Actions: post_message
The single Slack action lets an agent post messages into Slack channels. Configuration on the agent action card:- Default channel — the channel the agent posts to when not specified
- Allowed channels — optional whitelist of channels the agent can post to
- Customer-facing agent posts a summary into
#customer-successafter every escalation - Sales agent posts new lead alerts into
#new-deals - Support agent posts known-issue alerts into
#engineering
Notifications
Slack is the central notification sink in Halo. Configure notification routing on the Slack integration page:| Notification type | When it fires |
|---|---|
| New ticket | Any new ticket arrives |
| High-priority ticket | New ticket matches priority filters |
| Escalation | AI agent escalates a conversation |
| Negative sentiment | Conversation sentiment turns negative |
| Feedback alert | A user leaves negative or low-rated feedback |
| Knowledge gap | AI repeatedly fails to answer the same question |
| Health score drop | A company’s health score drops a tier |
| Daily/weekly digest | Periodic summary of activity |
| HubSpot engagement | New engagement processed (if HubSpot notifications mode on) |
| Stripe event | Customer created, subscription cancelled, payment failed, etc. |
| Contract event | PandaDoc contract state changed |
AI-enriched vs simple notifications
Halo notifications come in two flavors:- Simple — fire as-is (e.g. “New ticket #1234 from Jane Doe”)
- AI-enriched — Halo runs a summarization pass before posting, so the message includes context, root cause hypothesis, suggested response, etc.
Testing notifications
Click Send test notification on the Slack integration page to verify wiring. A test message goes to your default notifications channel.Slack DMs
DMs to the Halo app are intentionally not processed. The agent only responds in channels where it’s been explicitly mapped. This prevents accidental cross-customer leakage in shared workspaces.Where to go next
Agent Channels
Map Slack channels to specific agents.
Agent Actions
Enable post_message per agent.
Modes
Slack as notification sink for HubSpot, Stripe, PandaDoc, and more.