Slack Integration¶
Overview¶
The Slack integration delivers real-time notifications, slash commands, and initiative updates directly into your workspaces. It reduces context switching and keeps teams aligned.
Who this is for¶
- Admin
- End User
- Developer
Prerequisites¶
- Slack workspace admin permission to install apps.
- ValuePact Organization Admin role.
- A dedicated channel for ValuePact notifications (recommended).
Step-by-step instructions¶
1. Install the Slack app¶
- In ValuePact, go to Administration > Integrations > Slack.
- Click Add to Slack.
- Select your workspace and approve the OAuth scopes.
- Choose or create a channel for notifications, e.g.,
#valuepact-alerts.
2. Configure notifications¶
- In ValuePact, open Administration > Configuration > Notifications > Slack.
- Select event types:
- Initiative status changes
- Approval requests
- Weekly digest
- @mentions
- Map each event type to a channel or DM.
- Save.
3. Use slash commands¶
| Command | Description |
|---|---|
/valuepact search [term] | Search initiatives |
/valuepact status [initiative-id] | Show initiative health |
/valuepact actuals [initiative-id] | List latest actuals |
/valuepact help | Show command reference |
4. Set up channel-specific alerts¶
- Invite the ValuePact bot to a project channel.
- Type
/valuepact subscribe [initiative-id]. - The bot confirms the subscription.
- All status changes for that initiative now post to the channel.
5. Verify delivery¶
- Create a test initiative.
- Change its status to At Risk.
- Confirm the alert appears in the configured channel within 30 seconds.
Permissions required¶
| Role | Permission | Scope |
|---|---|---|
| Admin | Configure Slack integration | Organization |
| Admin | Manage notification rules | Organization |
| User | Use slash commands | Own tenant |
Limits and guardrails¶
- Limit Slash command response time: 3 seconds.
- Limit Subscriptions per channel: 20 initiatives.
- Limit Messages per minute: 100 per workspace.
Troubleshooting¶
Issue: Bot is not responding to slash commands
Cause: The Slack app was removed, or the command request URL is unreachable. Resolution: 1. Reinstall the app from Integrations > Slack. 2. Verify the request URL is whitelisted in your firewall. 3. Re-authorize the bot.
Issue: Notifications stopped after renaming a channel
Cause: Slack channel IDs persist, but the bot membership is tied to the name. Resolution: 1. Re-invite the ValuePact bot to the renamed channel. 2. In ValuePact, click Refresh Channels. 3. Re-select the channel in notification rules.
Issue: Duplicate notifications in multiple channels
Cause: Overlapping subscriptions or duplicate notification rules. Resolution: 1. Audit Notifications > Slack rules. 2. Remove redundant rules. 3. Consolidate subscriptions into one channel per initiative type.
Related pages¶
Escalation path¶
| Severity | Condition | Contact |
|---|---|---|
| P3 | Command or notification questions | #valuepact-support Slack |
| P2 | Bot unresponsive workspace-wide | support@valuepact.ai |
| P1 | Suspected data leakage through Slack | security@valuepact.ai |