Connectors
Connect third-party apps so Droid can use their tools in sessions, with managed authentication and organization-level controls.
Connectors give Droid managed access to third-party apps such as Linear, Jira, Notion, Slack, Sentry, and Google Workspace. Connect an app once, then ask Droid to work with it in natural language. Droid discovers the relevant tools and calls them under your current Autonomy Level.
Use Connectors when the app appears in Factory's catalog and you want guided authentication with no server configuration. Use MCP when you need a custom tool, a self-hosted service, or direct control over the server and transport.
Connect an app
- 1Open Connectors
Open Settings → Connectors in the Factory App.
- 2Choose an app
Search the catalog or browse the featured and full integration lists. If your organization manages connector availability, only apps an Owner or Manager enabled appear.
- 3Authorize access
Select Connect. Factory opens the app's authorization flow in a new browser tab. Sign in and approve the access requested by the app.
- 4Delegate work
Return to your session and ask Droid to use the app. Droid discovers the connected tools when the task needs them.
In an interactive session, ask Droid to connect an app:
Connect my Linear account so you can update the issue for this branch.Droid returns an authorization link when the app is available. Open the link, finish the provider's authorization flow, then tell Droid to continue.
Chat-based connection requires an interactive session because you must open an authorization link. Connect the app in the Factory App before running a non-interactive droid exec workflow.
Connections belong to both your Factory user and the active organization. If you belong to more than one organization, connect the app separately in each organization where Droid needs access.
Use a connected app
Ask for the outcome. You do not need to know tool names or API schemas.
Summarize the open Linear issues assigned to me, then update the one for this branch with the implementation status.Read the latest Sentry errors for checkout, correlate them with this code, and propose a fix.Create a Notion page with the rollout plan from this repository and include links to the relevant GitHub pull requests.Droid keeps connector tools in the deferred tool catalog. It loads the matching tool definitions only when a task needs them, which keeps unrelated app schemas out of the session context. Connected tools can also become available during a running session.
Connector calls follow the same approval model as other external tools:
| Tool classification | Default behavior |
|---|---|
| Read-only | Classified as low risk. It runs automatically when the session's Autonomy Level allows low-risk actions. |
| Write, destructive, or unknown | Classified as high risk. Droid asks for confirmation unless the session's Autonomy Level allows high-risk actions. |
Connector approvals apply to the current action. They are not stored as persistent MCP permissions.
How connectors work
The connection and execution paths stay separate:
| Stage | What happens |
|---|---|
| Availability | Factory maintains a curated connector catalog. Enterprise organizations can choose which catalog entries their members may use. |
| Connection | You finish the app's authorization flow. The resulting connection is scoped to your Factory user and active organization. |
| Discovery | Droid retrieves tools for apps you connected and adds them to its deferred tool catalog. |
| Execution | Droid sends approved tool calls through Factory's managed connector service. No connector process runs on your local machine. |
| Disconnection | Factory removes your credential for that app in the active organization. Organization availability for other members does not change. |
If an MCP server and a connected app expose the same capability, Droid removes overlapping tools from the session catalog where possible. Self-hosted and cloud instances remain separate when they may point to different systems.
Connectors and MCP
Connectors and MCP both extend Droid with external tools. They solve different setup and governance needs.
| Connectors | MCP | |
|---|---|---|
| Setup | Choose an app and finish its authorization flow. | Configure or install an MCP server. |
| Catalog | Factory-curated third-party apps and tool sets. | Any compatible local or remote MCP server. |
| Runtime | Factory-managed remote connector service. | Local stdio process or remote http / sse endpoint. |
| Authentication | Guided per-user, per-organization connection. | App-provided authorization, headers, environment variables, or server-defined authentication. |
| Configuration | No repository file or server lifecycle to manage. | User, folder, project, or organization mcp.json. |
| Organization controls | Owners and Managers enable or disable each catalog app for the organization. | Administrators control server access with managed MCP policy. |
| Best fit | Supported cloud apps that should work with minimal setup. | Custom tools, private services, self-hosted instances, and explicit server control. |
You can use both in the same session. Choose the surface that represents the system you intend to access. For example, keep a self-hosted Jira MCP server even if you also connect a cloud Jira account.
Manage your connections
Open Settings → Connectors to review connected apps.
- Connect starts a new authorization flow for that app.
- Disconnect removes your connection for the active organization. It does not disable the connector for teammates.
- Suggest a connector sends Factory the app name, website, and optional use case for review when the app is not in the catalog.
Never put passwords, API keys, access tokens, or customer data in a connector suggestion. Use the app's authorization flow for credentials.
Enterprise controls
Enterprise organizations get an organization-specific connector catalog. Connectors start disabled when the organization first configures this control. An Owner or Manager chooses which apps members can connect and use.
- 1Open Enterprise Controls
In the Factory App, open Settings → Enterprise Controls → Connectors.
- 2Review the catalog
The table shows every connector in Factory's curated catalog and whether it is available to this organization.
- 3Set availability
Turn on the apps the organization approves. Turn off an app to remove it from member settings and the tools available to Droid.
- 4Have members connect
Availability does not share an account or credential. Each member connects the enabled app with their own identity in Settings → Connectors.
The server enforces connector availability. Disabling an app:
- removes it from the organization's Connectors page;
- blocks new authorization links;
- removes its tools from the catalog available to Droid; and
- rejects direct tool calls, including calls from an existing session.
Disabling an app does not delete each member's saved connection. If an Owner or Manager enables it again, a member may still be connected. Members can use Disconnect to remove their own credential.
Organizations without Enterprise connector controls use Factory's curated catalog and do not see organization-level availability switches.
Owners and Managers can also recommend enabled connectors to members by work persona, so new members are guided to the right apps during onboarding. See Personas.
Security and data handling
| Control | Behavior |
|---|---|
| Identity scope | A connection is isolated by Factory user and active organization. It is not a shared organization credential. |
| App permissions | The third-party app controls the permissions shown during authorization. Review them before approving access. |
| Tool approval | Autonomy and confirmation checks run before Droid calls a connector tool. Unknown or non-read-only tools default to high risk. |
| Server-side enforcement | Organization availability is checked before Factory creates an authorization link or runs a tool. A disabled app cannot be called by bypassing the UI. |
| Local environment | Connector calls run through the managed remote service. They do not start a local process or read local files unless a separate Droid tool supplies that data. |
| Connector audit event | Factory records the connector tool name for the connector invocation event, without adding tool arguments or result content to that event. |
Only connect accounts and workspaces that Droid is allowed to access. The permissions granted by the third-party app remain the final boundary on what its tools can read or change.
Troubleshooting
Connector catalog
Factory's catalog covers the apps below, the same list as the connector catalog on factory.ai. Search by name or filter by category. Availability is per organization: if an Owner or Manager manages Enterprise controls, only the apps they enabled appear for members.
- Amazon S3List and read objects across your S3 buckets.
- AmplitudeQuery product analytics events and user cohorts.
- ApolloFind contacts, accounts, and sales prospecting data.
- AsanaSearch and manage tasks, projects, and sections.
- AshbySearch candidates, jobs, and interviews in Ashby.
- AxiomQuery logs, traces, and datasets in Axiom.
- ClayEnrich and manage people, companies, and lists in Clay.
- CloudflareManage DNS, zones, and settings in Cloudflare.
- CodaSearch and update docs, tables, and rows in Coda.
- ConfluenceSearch spaces, pages, and documentation.
- DatabricksRun queries and manage jobs in Databricks.
- DatadogQuery metrics, monitors, and logs from Datadog.
- DropboxSearch and read files and folders in Dropbox.
- FigmaSearch files, projects, and design components.
- FirefliesSearch meeting transcripts and notes from Fireflies.
- GmailSearch, read, and send email threads and messages in Gmail.
- GongSearch call recordings and conversation insights in Gong.
- Google CalendarLook up events and availability across calendars.
- Google DocsCreate, read, and update documents in Google Docs.
- Google DriveSearch and manage files and folders in Google Drive.
- Google MapsLook up places, directions, and geocoding data.
- Google SheetsRead and update rows across your spreadsheets.
- Google SlidesCreate, read, and update presentations in Google Slides.
- GrafanaQuery dashboards, panels, and metrics in Grafana.
- GranolaSearch meeting notes and transcripts in Granola.
- GreenhouseSearch candidates, jobs, and applications in Greenhouse.
- HexRun and manage data notebooks and apps in Hex.
- HubSpotSearch contacts, companies, deals, and tickets.
- JiraSearch and manage issues, sprints, and projects.
- Jira Service ManagementManage service requests and incidents in Jira Service Management.
- LinearSearch and create issues, projects, and cycles.
- LookerQuery dashboards, looks, and explores in Looker.
- MetabaseQuery dashboards, questions, and models in Metabase.
- Microsoft TeamsSearch channels, chats, and messages in Microsoft Teams.
- Microsoft Teams GCC HighSearch channels and messages in Microsoft Teams GCC High.
- MondaySearch and manage boards, items, and updates.
- NotionSearch pages and databases across your workspace.
- OktaManage users, groups, applications, and identity resources in Okta.
- OneDrive GCC HighSearch and read files in OneDrive GCC High.
- OneNoteSearch and read notes and notebooks in OneNote.
- OutlookSearch and read email threads and messages.
- PagerDutyLook up incidents, schedules, and on-call responders.
- PostHogQuery product analytics, events, and funnels in PostHog.
- PubmedSearch biomedical literature and abstracts on PubMed.
- PylonSearch and manage customer issues and accounts in Pylon.
- RootlyManage incidents and on-call workflows in Rootly.
- SalesforceSearch accounts, contacts, opportunities, and cases.Coming soon
- SentrySearch issues, events, and error details across projects.
- SharePointSearch sites, documents, and lists in SharePoint.
- SharePoint GCC HighSearch sites and documents in SharePoint GCC High.
- SlackSearch channels and messages and look up users and threads.
- SnowflakeRun queries across your Snowflake data warehouse.
- StatsigInspect feature gates, experiments, and metrics in Statsig.
- SupabaseQuery tables and manage data in Supabase.
- Teamwork.comManage tasks, projects, and milestones in Teamwork.com.
- VercelManage deployments, projects, and domains in Vercel.
- XSearch posts and look up profiles on X.
- ZendeskSearch and manage support tickets and users.
- Zendesk SellSearch and manage leads, contacts, and deals in Zendesk Sell.
- ZoomLook up meetings, recordings, and participants in Zoom.
The catalog in the Factory App is the live list. Use Suggest a connector when an app is missing here, or configure an MCP server for a custom or self-hosted service. Repository access to GitHub and GitLab does not use a connector: Factory reads and writes code through its Git integration, described in Identity & Access.
Related resources
Configure custom, private, and self-hosted tool servers.
Control which connector actions run without confirmation.
Understand organization settings, precedence, and governance.
Manage Factory roles, membership, SSO, and Directory Sync.