Factories > Integrations
Connect a factory to Slack
# Connect a factory to Slack Connect a factory to Slack so conversations become work in a dedicated app that preserves source-thread context and posts results back. ## Prerequisites and authorization You need permission to update the factory and install apps in the target Slack workspace. Workspace policy can require administrator approval. Installation grants the Slack access shown during authorization. Automation filters route received events; they do not reduce app permissions. For workspace installation and removal behavior, see the [Slack platform integration](../../platform/integrations/slack). ## Connect the factory When you connect Slack during factory creation, Warp attempts to install the dedicated app after creation when the required user and workspace authorization are available. If installation cannot complete, factory creation still succeeds; use **Add to Slack** to finish setup. 1. In factory setup, go to **Add your Factory to your team**. 2. In the **Slack** row, click **Add to Slack**. 3. Choose the target workspace and approve access. If Slack requires administrator approval, finish installation after approval. 4. Return to factory setup and confirm that **Slack** shows **Connected**. 5. Invite the factory's app to each channel where it will receive requests. Private channels require an invitation. Mention the app in a channel or send it a direct message. An eyes reaction acknowledges accepted requests. ## Slack intake and continuity | Slack activity | Context used by the factory | Slack output | | -------------------------------------- | ----------------------------------------------------------------------- | -------------------------------------------------------------------------------------- | | Mention the app in a channel or thread | Triggering message, available thread history, and supported attachments | Acknowledgment, status, final summary, and available run, issue, or pull request links | | Send the app a direct message | Direct-message conversation and supported attachments | Acknowledgment, status, and available artifact links | | Reply in an existing factory thread | Existing work item and the new reply | A follow-up on the same workstream rather than a new work item | | Match a Slack automation | Event details plus the automation's agent and instructions | A configured factory run with results returned to the source when supported | A plain thread reply continues work only after the thread has an existing factory work item. Start a new channel request by mentioning the app. When Slack files are supported, the factory includes them with the initial request or follow-up; files that cannot be included do not prevent the text request from continuing. ## Requester and execution identity People who start work through a mention or direct message must link their Slack identity to an active member of the factory's Warp team. Without that link, the app prompts the requester to connect an account instead of starting work. Background event automations run as the factory agent selected under **Agents**. Conversation and author filters admit matching events; they do not change the Slack app's authorization or execution credential scope. ## Configure Slack automations Use an automation when Slack activity must start work without someone explicitly mentioning the app. 1. In the factory's control room, open **Automations**, then create or edit an automation. 2. Under **Triggers**, click **Add trigger** > **Slack**, then choose an event. 3. Select the conversations and people that the event must match. Click **More filters** to add the event's available content filters. 4. Choose the receiving agent under **Agents**, add any **Additional instructions**, then click **Save**. Slack automations support these events: - **App mentioned** - Filter by joined conversations, authors, and keywords. - **Direct message received** - Filter by direct-message conversations, authors, and keywords. - **Message posted in channel** - Filter by joined conversations, authors, and keywords. - **Reaction added** - Filter by conversations, reactors, keywords, emoji, and reacted-message authors. - **Member joined channel** - Filter by conversations and members. Only conversations the factory's app has joined appear in the **Conversations** picker. Invite the app to a missing channel, or message it to establish a direct-message conversation, then refresh the automation editor. Avoid overlapping **App mentioned** and **Message posted in channel** triggers for the same conversations. A mentioned channel message can match both triggers and start two runs. ## Follow work and review outputs The Slack thread remains the continuity point for the work item. Reply in the thread to add information or supported attachments while work is active or to continue the same workstream later. The factory posts progress and the final response into that thread. Open the app's **Home** tab to view your factory tasks. App Home groups tasks by Factory task stage — Triage, Planning, Building, Reviewing, Completed, and Cancelled — and supports stage and date filters. Each task links back to the Slack thread, factory run, issue, or pull request when the link is available. A factory can create an issue, branch, or pull request, but repository policy still controls review and merge. Slack installation permissions and factory routing do not replace required human review. ## Troubleshooting and reconnection - **The app does not acknowledge a request** - Confirm the Slack row shows **Connected**, mention the correct factory app, and invite it to the channel. - **A channel is missing from an automation** - Invite the app to that channel, then reload the **Conversations** picker. - **Installation is pending** - Ask a Slack workspace administrator to approve the app, then finish the installation. - **Two runs start for one mention** - Remove or narrow overlapping app-mention and channel-message triggers. Removing the app in Slack stops new Slack intake for that factory. Return to factory setup and use **Add to Slack** to reconnect it. Deleting the factory also removes its dedicated Slack connection. Next, review other intake paths in [Connect your factory](../connect-your-factory).Tell me about this feature: https://docs.warp.dev/factories/integrations/slack/Connect a factory to Slack so mentions, direct messages, and automation events create work and return results to the source conversation.
Connect a factory to Slack so conversations become work in a dedicated app that preserves source-thread context and posts results back.
Prerequisites and authorization
Section titled “Prerequisites and authorization”You need permission to update the factory and install apps in the target Slack workspace. Workspace policy can require administrator approval.
Installation grants the Slack access shown during authorization. Automation filters route received events; they do not reduce app permissions. For workspace installation and removal behavior, see the Slack platform integration.
Connect the factory
Section titled “Connect the factory”When you connect Slack during factory creation, Warp attempts to install the dedicated app after creation when the required user and workspace authorization are available. If installation cannot complete, factory creation still succeeds; use Add to Slack to finish setup.
- In factory setup, go to Add your Factory to your team.
- In the Slack row, click Add to Slack.
- Choose the target workspace and approve access. If Slack requires administrator approval, finish installation after approval.
- Return to factory setup and confirm that Slack shows Connected.
- Invite the factory’s app to each channel where it will receive requests. Private channels require an invitation.
Mention the app in a channel or send it a direct message. An eyes reaction acknowledges accepted requests.
Slack intake and continuity
Section titled “Slack intake and continuity”| Slack activity | Context used by the factory | Slack output |
|---|---|---|
| Mention the app in a channel or thread | Triggering message, available thread history, and supported attachments | Acknowledgment, status, final summary, and available run, issue, or pull request links |
| Send the app a direct message | Direct-message conversation and supported attachments | Acknowledgment, status, and available artifact links |
| Reply in an existing factory thread | Existing work item and the new reply | A follow-up on the same workstream rather than a new work item |
| Match a Slack automation | Event details plus the automation’s agent and instructions | A configured factory run with results returned to the source when supported |
A plain thread reply continues work only after the thread has an existing factory work item. Start a new channel request by mentioning the app. When Slack files are supported, the factory includes them with the initial request or follow-up; files that cannot be included do not prevent the text request from continuing.
Requester and execution identity
Section titled “Requester and execution identity”People who start work through a mention or direct message must link their Slack identity to an active member of the factory’s Warp team. Without that link, the app prompts the requester to connect an account instead of starting work.
Background event automations run as the factory agent selected under Agents. Conversation and author filters admit matching events; they do not change the Slack app’s authorization or execution credential scope.
Configure Slack automations
Section titled “Configure Slack automations”Use an automation when Slack activity must start work without someone explicitly mentioning the app.
- In the factory’s control room, open Automations, then create or edit an automation.
- Under Triggers, click Add trigger > Slack, then choose an event.
- Select the conversations and people that the event must match. Click More filters to add the event’s available content filters.
- Choose the receiving agent under Agents, add any Additional instructions, then click Save.
Slack automations support these events:
- App mentioned - Filter by joined conversations, authors, and keywords.
- Direct message received - Filter by direct-message conversations, authors, and keywords.
- Message posted in channel - Filter by joined conversations, authors, and keywords.
- Reaction added - Filter by conversations, reactors, keywords, emoji, and reacted-message authors.
- Member joined channel - Filter by conversations and members.
Only conversations the factory’s app has joined appear in the Conversations picker. Invite the app to a missing channel, or message it to establish a direct-message conversation, then refresh the automation editor.
Avoid overlapping App mentioned and Message posted in channel triggers for the same conversations. A mentioned channel message can match both triggers and start two runs.
Follow work and review outputs
Section titled “Follow work and review outputs”The Slack thread remains the continuity point for the work item. Reply in the thread to add information or supported attachments while work is active or to continue the same workstream later. The factory posts progress and the final response into that thread.
Open the app’s Home tab to view your factory tasks. App Home groups tasks by Factory task stage — Triage, Planning, Building, Reviewing, Completed, and Cancelled — and supports stage and date filters. Each task links back to the Slack thread, factory run, issue, or pull request when the link is available.
A factory can create an issue, branch, or pull request, but repository policy still controls review and merge. Slack installation permissions and factory routing do not replace required human review.
Troubleshooting and reconnection
Section titled “Troubleshooting and reconnection”- The app does not acknowledge a request - Confirm the Slack row shows Connected, mention the correct factory app, and invite it to the channel.
- A channel is missing from an automation - Invite the app to that channel, then reload the Conversations picker.
- Installation is pending - Ask a Slack workspace administrator to approve the app, then finish the installation.
- Two runs start for one mention - Remove or narrow overlapping app-mention and channel-message triggers.
Removing the app in Slack stops new Slack intake for that factory. Return to factory setup and use Add to Slack to reconnect it. Deleting the factory also removes its dedicated Slack connection. Next, review other intake paths in Connect your factory.