Skip to main content

​
Slack Integration

​
1. Overview

Your platform now sends critical updates through Slack - the communication tool you already use daily. Production deploys, error alerts, and SupaSherpa coaching land directly in your workspace, so you stay informed without switching tools. If you’re in the US, Canada, or UK, Slack becomes your default channel for SupaSherpa conversations, keeping momentum updates and next actions where you work.

​
2. Step-by-Step Guide

Setting Up Slack Notifications
  1. Navigate to your platform settings and locate the Integrations section
  2. Click “Connect Slack” and authorize the Fiftyknots app for your workspace
  3. Select which channel receives deploy notifications (typically #engineering or #updates)
  4. Choose whether to receive error alerts in the same channel or a dedicated #alerts channel
  5. Click “Save Settings” to activate notifications
Messaging SupaSherpa in Slack
  1. Open Slack and find the Fiftyknots bot in your Direct Messages
  2. Send your first message - ask about momentum, next actions, or specific questions about your venture
  3. SupaSherpa responds with formatted messages showing your four beats: route, momentum, next cairn, and savings
  4. Click action buttons in the response to jump directly to recommended tasks or resources
  5. Continue the conversation naturally - SupaSherpa maintains context across messages
Changing Your Preferred Channel
  1. Go to SupaSherpa settings on the platform
  2. Click “Channel Preferences”
  3. Select Slack, WhatsApp, or Web based on your preference
  4. Save your selection - future proactive messages use your chosen channel
Using Claude Code with Slack
  1. Open .claude/settings.local.json in your project
  2. Verify the Slack MCP server is registered in your configuration
  3. In Claude Code, use tools like post_session_summary or post_changelog to share updates
  4. Specify your team channel when posting - summaries appear with session details and files changed
  5. Team members see formatted updates without manual copying

​
3. Common Questions

Q: Why am I getting SupaSherpa messages in Slack instead of WhatsApp? A: The platform automatically selects your channel based on country. US, Canada, and UK users default to Slack since that’s where most business communication happens in those markets. You can override this by setting your preference in SupaSherpa settings. Brazil, South Africa, and India default to WhatsApp but can switch to Slack anytime. Q: What happens if I send a Slack DM but my account isn’t connected? A: The bot responds with an onboarding message linking to the platform. You’ll need to visit that link and connect your Slack account to your Fiftyknots profile. Once connected, you can message SupaSherpa directly in Slack without additional setup. Q: Do I get notified about every deploy and error? A: Deploy notifications post once per production deployment with a summary of all changes. Error alerts only fire for new issues or significant increases in occurrence count - you won’t see repeat notifications for the same error unless user impact changes. Both notification types include direct links to view details in GitHub or Sentry. Q: Can I turn off Slack notifications without disconnecting? A: Yes. The SLACK_SUPASHERPA_ENABLED flag controls SupaSherpa DMs separately from deploy and error notifications. Your platform admin can disable specific notification types while keeping others active. If you need this, reach out through the support system. Q: What information does SupaSherpa share in Slack messages? A: Every SupaSherpa response includes your four beats: current route (stage), momentum score, next cairn (recommended action), and savings (time/money saved). Messages format automatically with sections for readability and action buttons for one-click navigation to relevant platform pages.

​
4. Troubleshooting

Issue: Slack bot doesn’t respond to my messages Check that your Slack account is connected in platform settings under Integrations. If connected, verify your workspace hasn’t blocked the Fiftyknots app - workspace admins can see approved apps in Slack settings. Still not working? The SLACK_SUPASHERPA_ENABLED feature flag might be off for your account. Contact support to verify your configuration. Issue: Deploy notifications aren’t appearing in my channel Confirm the webhook URL is configured correctly - go to Integrations settings and verify the connected channel. If the channel was deleted or renamed in Slack, notifications fail silently. Reconnect the integration to select a new channel. Check that the workflow includes the SLACK_WEBHOOK_URL_DEPLOYS environment variable in your repository settings. Issue: Claude Code tools return “SLACK_BOT_TOKEN not configured” The MCP server requires a bot token in your environment variables. Add SLACK_BOT_TOKEN to your .env file with the token from your Slack app configuration. Restart Claude Code after adding the token. If you don’t have a token, your platform admin needs to create one in the Slack App Management console. Issue: Error alerts have the wrong severity color Severity colors map automatically from Sentry levels: critical/fatal show red, error shows orange, warning shows yellow, info shows blue. If colors seem incorrect, check the error level in Sentry - the platform displays exactly what Sentry reports. You can adjust Sentry’s severity classification rules in your project settings if needed. SupaSherpa - Your AI coach that delivers momentum updates, next actions, and strategic guidance through multiple channels including Slack, WhatsApp, and web chat. Slack integration makes SupaSherpa accessible in your primary work tool without context switching. Sentry Error Alerts - Production error monitoring that posts critical issues to your team channels. Slack integration surfaces these alerts alongside deploy notifications, so you see the full picture of system health in one place. Deploy Notifications - Automated summaries of production deployments with commit details, pipeline status, and deployment URLs. These notifications keep your entire team informed about releases without manual status updates or checking GitHub Actions directly.