Chat Triggers
Run analyses directly from Slack, Microsoft Teams, Discord, or Google Chat using slash commands
Chat triggers let your team kick off analyses without leaving their chat tool. After connecting a chat workspace and authorizing a specific channel, anyone with access can run:
/sigsentry analyze checkout returning 500s last 30 minutesA few seconds later, the diagnosis posts back as a threaded reply in the same channel. Follow-up questions in the thread continue the same analysis.
This section covers inbound triggers (running analyses from chat). For outbound notifications (delivering analysis results to a chat channel), see Notification Channels.
Supported platforms
Slack
Slash commands and threaded follow-ups.
Microsoft Teams
Bot install and command syntax.
Discord
Bot install and slash interactions.
Google Chat
Service-account authenticated bot.
Two related but separate concepts
A chat trigger is different from a chat channel even though both involve chat:
| Concept | Direction | What it does |
|---|---|---|
| Chat trigger | Inbound | Runs analyses from chat slash commands |
| Notification channel | Outbound | Delivers analysis results to a chat channel |
You can have one without the other. Most teams set up both — install the trigger to run analyses from chat, and configure a notification channel so unrelated analyses (from watchdog, support desk) post into chat too.
How to use chat triggers
After installation, the basic command shape is:
/sigsentry analyze <description> <time-expression>Examples:
| Command | What it does |
|---|---|
/sigsentry analyze checkout returning 500s last 30 minutes | Standard analysis |
/sigsentry analyze db timeouts since 9am | Time-of-day expression |
/sigsentry analyze high error rate last 4 hours --project=billing | Override project |
See Command grammar for the full grammar.
After the diagnosis posts in the thread, anyone in the thread can ask follow-up questions in plain English — the bot will respond using the context of the original analysis:
What changed in the last hour that could've caused this?
Is this related to PR #482?Permissions and access control
Two layers control who can use chat triggers:
| Layer | What it controls |
|---|---|
| Workspace binding | Which chat workspace is connected to your tenant |
| Project access list | Which users can trigger analyses on which project from chat |
By default, all team members in a connected workspace can trigger analyses on any of your projects. To restrict, see Access control.
Identity mapping
When a Slack/Teams/Discord user runs /sigsentry analyze, SigSentry
maps that chat identity to a SigSentry user via email match. So
the user must:
- Have a SigSentry account in your tenant
- Use the same email in their chat profile as in their SigSentry account
If the chat-side email isn't visible (Discord, for example, often hides email), the user is mapped as anonymous and the analysis runs under the workspace's installer identity. See Identity mapping for the full rules.
Plan requirements
Chat triggers are gated by plan:
| Plan | Chat integrations allowed |
|---|---|
| Starter | 0 |
| Pro | 1 |
| Business | Unlimited |
| Enterprise | Unlimited |
A "chat integration" is one workspace binding — connecting Slack counts as one, Teams as another, regardless of how many channels you authorize within each.