Connect your factory

Connect your factory to the tools where your team already discusses, tracks, and reviews work. Wherever work starts, the factory keeps the original context — the thread, issue, or pull request — and posts results back to the same place.

Choose a source

Pick the sources that match where work starts for your team. You can connect multiple sources, but not both Linear and Jira at the same time. The setup wizard currently offers Linear; to use Jira, connect it after setup or in your factory definition.

Source	Best for	Where follow-ups continue
Slack	Chat and support requests	The Slack thread or DM
GitHub	Issues, pull requests, reviews, and CI	The issue, pull request, or review thread
GitLab	Merge request activity and bot mentions	The merge request thread
Linear	Planned issues	The Linear issue and its agent session
Jira	Work items assigned to Warp	The Jira agent session
Factory MCP	Exchanging work with a local coding agent, in both directions	The factory work item
Direct runs and schedules	One-off or recurring work	The factory work item

Connect a source

Each source’s integration guide walks through authorizing access; grant only what the factory needs. Provider connections come with default automations that decide which events start work and which agent handles them. Review their filters and run settings after connecting. Filters route work, not access: what a running agent can reach depends on its own configuration, not the filters that started it.

After connecting, send a test request, such as mentioning the factory in Slack or assigning it an issue, and confirm it picks up the work and replies at the source.

How work reaches your factory

flowchart LR
  Event["Event from a<br/>connected tool"] --> Automation["Matching<br/>automation"]
  Schedule["Schedule"] --> Automation
  Automation --> Foreman["Foreman agent"]
  Direct["Direct request"] --> Foreman
  Foreman --> Work["Work item"]
  Work --> Results["Results posted<br/>back to the source"]

An event from a connected tool starts the automation based on filter matching, such as a specific repository, channel, or label. Schedules start their automation on a timer, and direct requests go straight to the factory.

Every request lands with the foreman agent, which turns it into a work item and dispatches the agents each stage needs. A reply in the same thread, issue, or pull request continues that work item instead of starting a new one, and repeated event deliveries don’t create duplicates. See how Warp Factories work for the full lifecycle, including where people stay in the loop.

Review the default automations

When you create a factory through the setup wizard, Warp adds default automations for each tool you connect, so common requests work immediately:

• GitHub - Starts work when the factory is mentioned or assigned, and follows up when pull requests close or merge, completing a linked tracker issue when it can. See the GitHub integration guide.
• GitLab - Starts work when someone mentions the factory’s bot in a merge request comment. See the GitLab integration guide.
• Jira - Starts work when someone assigns or mentions Warp on a work item in one of the Jira projects you selected. See the Jira integration guide.
• Linear - Starts work when a new agent session arrives from one of the Linear teams you selected. See the Linear integration guide.
• Slack - Starts work from mentions and messages, as described in the Slack integration guide.

These defaults are starting points. Review each automation’s filters, agent, and run settings, and adjust them to match your workflow.

Factory MCP

The Factory MCP connects local coding agents and other MCP clients to your factory, and it works in both directions. Send work to the factory, or take work over from it by pulling a task down to your machine, iterating on it locally, and handing it back to the same work item. See the Factory MCP guide.

Direct runs and schedules

Not every task starts in an external tool:

• Start a direct run for one-off work. Click New on the factory’s Runs page and describe the task to the foreman, the same way you would from Slack or an issue tracker.
• Create a scheduled automation for recurring work, such as maintenance or reports. See the triggers overview for how schedules and other triggers work across the platform.