Slack Integration Setup Guide

Slack Integration Setup Guide

This guide walks you through connecting Lathe Studio to Slack for notifications and team collaboration.


Prerequisites#

  • Slack workspace
  • Permission to install apps in your workspace
  • Project admin access in Lathe Studio

Overview#

The Slack integration enables:

  • Test Run Notifications: Get notified when test runs are submitted or completed
  • Build Alerts: Receive alerts when builds are ready for testing
  • Release Updates: Track release readiness as testing progresses

Connecting Slack#

Step 1: Create a Slack Incoming Webhook

  1. In Slack, open the channel where notifications should be posted
  2. Click the channel name, then Integrations (or Apps)
  3. Add an Incoming Webhook and give it a name, e.g. "Lathe Studio"
  4. Copy the webhook URL

Step 2: Connect in Lathe Studio

  1. In Lathe Studio, go to Settings β†’ Integrations β†’ Slack
  2. Paste the webhook URL and enter the channel name
  3. Click Save

Step 3: Configure Notifications

After connecting, choose which events trigger notifications:

EventDescriptionDefault
Test Run SubmittedWhen a tester submits resultsEnabled
Test Run CompletedWhen a test run is marked completeEnabled
Build ReadinessWhen a build is ready for testingEnabled

You can also create custom notification rules for other events β€” build received or assigned, test run assigned, test run completed with failures, release readiness (80% and 100%), and Jira events (bugs pushed, issue resolved). Rules can be scoped to a specific project or applied org-wide.

Step 4: Test the Integration

  1. Click Test Connection in Lathe Studio to send a test message
  2. Check the configured Slack channel
  3. You should see a notification confirming the connection

Notification Format#

Test Run Completed

πŸ§ͺ Test Run Completed: Smoke Tests - Build 245

Project: E-commerce Platform
Build: 245 (v2.4.1)
Release: March Sprint

Results:
βœ… Passed: 42
❌ Failed: 3
⚠️ Blocked: 1
⏭️ Skipped: 4

View Run: https://lathe.studio/projects/.../runs/...

Build Ready for Testing

πŸ”¨ New Build Available: Build 246

Project: E-commerce Platform
Branch: main
Commit: a1b2c3d

This build needs to be assigned to a release for testing.

View in Lathe Studio: https://lathe.studio/projects/.../builds/...

Channel Configuration#

Slack supports one incoming webhook connection per organization. The channel is decided by the webhook URL itself (Slack binds each incoming webhook to a channel); the channel name you enter in Lathe Studio is a label shown in Settings and the Integrations hub so your team can see where messages go. It is not sent to Slack.

To notify different groups about different projects, create custom notification rules and scope each rule to the relevant project. All Slack notifications for your organization are delivered to the connected channel.


Troubleshooting#

Notifications not appearing

  1. Verify the incoming webhook URL is correct and active in Slack
  2. Check that the channel still exists and the webhook wasn't removed
  3. Ensure notification settings are enabled for the event type
  4. Click Test Connection in Lathe Studio to confirm delivery

Rate limiting

Slack has rate limits for incoming webhook messages. If you see delays:

  1. Reduce notification frequency
  2. Disable non-critical notifications
  3. Scope rules to the projects that need them

Security#

  • Webhook URLs are stored in the database and scoped by organization; they are encrypted at rest
  • No Slack credentials are stored β€” the webhook URL is the only secret
  • No message content is stored from Slack
  • Users can disconnect at any time
  • Workspace admins can revoke the webhook in Slack at any time

Unlinking Slack#

To disconnect:

In Lathe Studio

  1. Go to Settings β†’ Integrations β†’ Slack
  2. Click Disconnect
  3. Confirm disconnection

In Slack

  1. Open the channel, then Integrations (or Apps)
  2. Find the Lathe Studio incoming webhook
  3. Click Remove

Note: Removing Slack integration stops all notifications. Previously sent messages remain in Slack.


For additional help, contact support.