Connect Slack to your factory

Connect a factory to Slack so your team can send it work without leaving their conversations. Mention the factory in a channel or send it a direct message, and it picks up the request with the conversation as context, then posts progress and results back into the same thread.

Each factory appears in Slack as its own app, carrying the factory’s name and avatar. A channel can host several factories, and you choose which one to mention.

Prerequisites

• Permission to install Slack apps - You need it in the target workspace, and workspace policy can require an administrator to approve the app before it installs.
• Permission to update the factory - Connecting Slack changes the factory’s configuration.

Connect the factory

Select Slack while creating a factory and Warp installs its app for you. If the install can’t finish on its own — usually because your workspace requires administrator approval — click Add to Slack in factory setup to complete it.

Then invite the app to each channel it should listen in. Private channels always need an invitation.

To check that it worked, mention the app in one of those channels. It reacts with 👀 to show it picked up the request.

Start and continue work from Slack

Slack activity	Context used by the factory	Slack output
Mention the app in a channel or thread	The triggering message, available thread history, and supported attachments	An acknowledgment, progress updates, a final summary, and links to the run, issue, or pull request when available
Send the app a direct message	The direct-message conversation and supported attachments	An acknowledgment, progress updates, and links to results when available
Reply in an existing factory thread	The existing work item and your reply	A follow-up on the existing work item instead of new work
Slack activity matches an automation	The event details plus the automation’s agent and instructions	A factory run, with results posted back to the source conversation when supported

A plain reply in a thread continues work only if that thread already has a factory work item; to start new work in a channel, mention the app. You can attach files to a request or a follow-up. The factory includes the files it supports, and a file it can’t include doesn’t stop the text of your request from going through.

Who can start work

To start work with a mention or direct message, your Slack account must be linked to an active member of the factory’s Warp team. If it isn’t, the app prompts you to connect an account instead of starting work.

Work started by an automation runs as the factory agent you chose for it, not as whoever triggered it.

Configure factory automations for Slack

Use a factory automation to start work from Slack activity automatically, without anyone mentioning the app, such as on every message in a triage channel or on a specific emoji reaction. Add a Slack trigger to an automation and pick one of these events; automation filters covers the steps.

• 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.

The Conversations picker only shows conversations the factory’s app has joined. If a channel is missing, invite the app to it; for direct messages, send the app a DM first. Then refresh the automation editor.

A single Slack message can match more than one automation. For example, if one automation triggers on App mentioned and another triggers on Message posted in channel in the same channel, a channel message that mentions the app starts two separate runs, one for each automation. To avoid duplicate runs, don’t point both triggers at the same channel.

Follow work and review outputs

The Slack thread where work started is also where you follow it: the factory posts progress and the final response there. Reply in the thread to add information or attachments while work is active, or to pick the same work item back up later.

For an overview of the factory’s work items, open the app’s Home tab in Slack. It groups them by the same stages as the factory dashboard’s Activity view (Triage, Planning, Building, Reviewing, Completed, and Cancelled), offers stage and date filters, and links each work item back to its Slack thread, factory run, issue, or pull request when available.

Work that starts in Slack still ends at a pull request for a person to review — see how Warp Factories work.

Troubleshooting and reconnection

• The app doesn’t acknowledge a request - Confirm Slack is connected for that factory, that you mentioned the right factory’s app, and that the app is in 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.

To disconnect Slack, either delete the factory — which removes its Slack app along with it — or remove the app from your Slack workspace, which stops new Slack requests reaching that factory. To reconnect afterward, click Add to Slack in factory setup again.

To route work into the factory from other tools, see Connect your factory.

Privacy

The factory’s app reads messages only where it’s mentioned, directly messaged, or subscribed by an automation you configured. Message content and supported attachments are used to run the factory’s work, and your Slack profile email is used to map you to your Warp account. Data is handled per the Warp Privacy Policy.