Skip to main content

​
Slack Integration

​
Overview

Connect your team’s Slack workspace to receive production deploy notifications, error alerts, and direct coaching from SupaSherpa - all in the tool you already use daily. Fiftyknots routes communication to the channel that fits your geography: founders in the US, Canada, and UK default to Slack, while other regions default to WhatsApp. You can override this preference anytime.

​
Step-by-Step Guide

​
Receiving Deploy Notifications

  1. Configure your webhook URL - Add SLACK_WEBHOOK_URL_DEPLOYS to your environment variables with your Slack incoming webhook URL
  2. Deploy your application - When the deploy-production workflow completes, a formatted message appears in your configured Slack channel
  3. Review the deploy summary - The message includes version string, commit SHA, job statuses, deployment URLs, and total pipeline duration
  4. Check for failures - Failed deploys show a red sidebar, include the failure reason, and tag the commit author

​
Getting SupaSherpa Messages in Slack

  1. Verify your location - If your profile country is US, CA, or GB, Slack becomes your default channel
  2. Connect your Slack account - Visit the SupaSherpa settings and link your Slack user ID to your Fiftyknots profile
  3. Send a DM to the Fiftyknots bot - Start a conversation directly in Slack
  4. Receive formatted responses - SupaSherpa replies appear as Block Kit messages with four beats (route, momentum, next cairn, savings) and action buttons for next steps
  5. Override if needed - Use PUT /api/v1/supasherpa/channel-preference with { "channel": "slack" } to force Slack as your preferred channel regardless of location

​
Setting Up Claude Code Integration

  1. Configure your bot token - Add SLACK_BOT_TOKEN to your environment variables
  2. Register the MCP server - Add the Slack MCP server to .claude/settings.local.json
  3. Restart Claude Code - Four tools become available: post_message, post_session_summary, post_changelog, and list_channels
  4. Post session summaries - Invoke post_session_summary with summary text and channel name to share code changes with your team
  5. Review the formatted message - The tool posts a Block Kit message with session date, summary, files changed count, and a divider

​
Monitoring Sentry Errors in Slack

  1. Configure the same webhook URL - Use the SLACK_WEBHOOK_URL_DEPLOYS variable set for deploy notifications
  2. Trigger a Sentry event - When errors occur in production, Sentry webhooks fire automatically
  3. Check your Slack channel - Error alerts appear with severity color coding (red, orange, yellow, blue), error title, project name, occurrence count, users affected, and a “View in Sentry” button

​
Common Questions

Q: What happens if I’m not in the US, Canada, or UK?
A: The system defaults to WhatsApp for founders in South Africa, Brazil, and India. If you prefer Slack anyway, set your explicit channel preference to override the geographic default. Q: Can I still receive messages in multiple channels?
A: Yes. Deploy notifications and error alerts go to configured Slack webhooks regardless of your SupaSherpa channel preference. Your personal coaching messages follow your channel preference setting. Q: What if my Slack webhook fails?
A: Deploy and error notification failures are logged but don’t affect other channels. Teams and email notifications continue working. Check your webhook URL configuration if messages stop arriving. Q: Do I need to configure anything for SupaSherpa to work in Slack?
A: You need a verified Slack channel mapping in the supasherpa_channel_mappings table. If you send a DM to the Fiftyknots bot without this, you’ll receive an onboarding message with a link to connect your account at https://platform.fiftyknots.com. Q: Can I disable Slack for SupaSherpa but keep deploy notifications?
A: Yes. Set SLACK_SUPASHERPA_ENABLED to false. The webhook still accepts and acknowledges events but doesn’t process SupaSherpa messages. Deploy and error notifications work independently.

​
Troubleshooting

Issue: Claude Code tools return “SLACK_BOT_TOKEN not configured”
Solution: Add SLACK_BOT_TOKEN to your environment variables. The MCP server requires this token to authenticate with Slack’s API. Restart Claude Code after adding the variable. Issue: SupaSherpa responds with an onboarding message instead of answering
Solution: Your Slack user ID isn’t linked to your Fiftyknots profile. Visit https://platform.fiftyknots.com and complete the Slack account connection flow in SupaSherpa settings. Issue: Deploy notifications aren’t appearing in Slack
Solution: Verify SLACK_WEBHOOK_URL_DEPLOYS is set correctly. Test the webhook URL manually with a curl command. Check that the workflow summary job completed successfully in GitHub Actions. Issue: Messages appear as plain text instead of formatted blocks
Solution: Slack’s Block Kit requires the message payload to use the correct structure. If you’re seeing plain text, the adapter may be falling back to legacy formatting. Check logs for Block Kit validation errors and verify your bot token has the necessary scopes. WhatsApp Integration - If Slack doesn’t fit your workflow, WhatsApp offers the same SupaSherpa coaching experience optimized for mobile-first founders. Geographic routing automatically selects WhatsApp for South Africa, Brazil, and India. SupaSherpa Channel Preferences - Control where you receive coaching messages across Slack, WhatsApp, and websocket. Set explicit preferences to override geographic defaults and view your nudge history to understand communication patterns. Microsoft Teams Integration - Teams receives the same deploy notifications and Sentry error alerts as Slack. Configure a separate Teams webhook to route alerts to both platforms simultaneously.