Connect Droid to the tools that run your company
By Factory - August 25, 2026 - 3 minute read
Product
Share
Connect the apps your team already uses so Droid can take on work across them.
Most of the context Droid needs doesn’t start in the request you type. It’s in a Linear issue, a Slack thread, a Sentry alert, a Notion page, or a Salesforce opportunity.
Today we’re launching Connectors, which give Droid managed access to the apps your team uses. And with Personas, each role is pointed to the right Connectors during setup.
Pick an app from a conversation with Droid or from Settings, sign in, and start delegating. Droid finds the right tools when a task needs them, so there’s no server to configure and no API to learn. Connect once and it works across Desktop, CLI, web, and mobile.
You can still use MCP for custom tools, private services, and self-hosted systems. Connectors add a managed path for supported apps, and both work in the same session.
Start with the work you do
When someone opens Factory for the first time, they pick the persona that matches their work: Engineering, Product, Design, Finance, Marketing, Sales, or Operations. Factory shapes the first tasks and guidance around that choice.
An engineer can start by exploring a codebase or drafting a design document. A product manager can map the product surface and draft a spec. In Enterprise organizations, Owners and Managers can recommend approved Connectors for each persona, so the walkthrough points each role to the apps it actually uses.
What this looks like in practice
Once the right apps are connected, Droid works across all of them. It can trace a production incident back to the code, turn customer feedback into a roadmap recommendation, or explain a forecast change from the source data.
Engineering
Turn a production error into a patch your team can review.
Checkout timeouts jumped after yesterday’s production change. The signals live in Sentry and Datadog, the incident timeline in PagerDuty, and the code, recent changes, and ownership context in GitHub and Linear.
Investigate checkout timeouts from yesterday’s production change. Correlate the Sentry and Datadog signals with the PagerDuty timeline, find the first bad commit in GitHub, draft a minimal safe patch, and prepare a Linear-ready incident brief with the remaining follow-ups.
Droid comes back with a draft patch and an incident brief. The team confirms the diagnosis, adjusts the blast radius, and approves the patch.
Product
Decide what to build from what customers are saying.
Approval controls keep coming up in customer feedback, but the roadmap is already committed. The feedback and prior decisions are spread across Slack and Notion, commitments live in Linear, wireframes in Figma, and usage data in Amplitude.
Compare feedback about approval controls with our current commitments and product data. Separate repeated needs from one-off requests, identify conflicts with the planned experience, and recommend what should change.
Droid returns a roadmap recommendation with the evidence, the tradeoffs, and the open questions. The product team challenges the evidence and chooses the scope.
Finance
Explain why the forecast changed and show the source data.
The forecast moved after month close. Revenue is in Stripe, pipeline in Salesforce, expense detail in Expensify, and the forecast and plan in Google Sheets and Anaplan.
Reconcile the changed forecast with revenue, pipeline, expense, and planning data. Rank the largest drivers, link each explanation to its source, and flag assumptions that still need an owner.
Droid puts together a variance brief with sourced drivers and open questions. The finance team validates the drivers and corrects the assumptions.
Controls for company rollouts
Enterprise Owners and Managers decide which Connectors members can use, which Personas are available, and which Connectors to recommend for each role. Recommendations help people find the right apps during setup but do not grant access, so each person still connects their own account.
If an admin turns off a Connector, its tools are removed from Droid, members can no longer create authorization links, and calls to that Connector are blocked, even from sessions already in progress.
Connector calls follow the same confirmation rules as other Droid tools, based on the session’s Autonomy Level. The selected level determines whether read-only calls can run automatically and when Droid must ask for confirmation before a write, a destructive action, or anything it cannot classify.
Available now
Connect an app by asking Droid or opening Settings → Connectors. Pick an app, sign in, and give Droid your first task.
Owners and Managers can set up company rollouts in Settings → Enterprise Controls.
