Use this article to connect Operator to the external tools your team already uses, so it can pull in live data and take actions across your stack without leaving the conversation.
Connections link Operator to third-party tools your team already uses, such as GitHub, Linear, Notion, Jira, Snowflake, and HubSpot. Once connected, Operator can search, query, and act on data from those tools directly.
Note: Connections are included with Operator on the Pro add-on. The connectors available to you are listed in Operator > Customize > Connections.
Key benefits
Work across your tools without switching tabs — ask Operator to pull data from GitHub, Linear, or Notion in the same conversation
Ground analysis in live data — Operator queries your connected tools rather than relying on what you paste in
Extend Operator with MCP Server — connect Operator to any compatible external server using MCP Server (Model Context Protocol)
Supported connections
The following connectors are available. Availability depends on your workspace permissions.
Connector | What you can do |
Stripe | Import Stripe connectors for billing and subscription management |
Linear | Manage issues, projects, and team workflows in Linear |
Notion | Connect your Notion workspace to search, update, and power workflows |
GitHub | Search issues, pull requests, and code in repositories you can access |
Atlassian (Jira and Confluence) | Search, create, and update Jira issues and Confluence pages you can access |
Snowflake | Query your Snowflake warehouse through an OAuth security integration |
Pendo | Look up product usage, in-app guides, and feedback captured by Pendo |
Glean | Search documents, tickets, and chats indexed by Glean |
Slite | Search and update docs in your Slite knowledge base |
Sentry | Look up issues, errors, and events from your Sentry projects |
Fullview | Review session replays, cobrowsing, and console errors from Fullview |
Guru | Search cards and answers in your Guru knowledge base |
Braze | Explore campaigns, canvases, and customer engagement data from Braze |
PostHog | Query product analytics, insights, and feature flags from PostHog |
incident.io | Look up incidents, follow-ups, and on-call schedules from incident.io |
Attio | Look up records, lists, and notes from your Attio CRM |
Hex | Explore projects and ask data questions in your Hex workspace |
Dovetail | Search and update customer research in your Dovetail workspace |
FullStory | Explore session replays and product analytics from FullStory |
Airtable | Search, create, and update records in your Airtable bases |
Close | Look up and update leads, contacts, and opportunities in your Close CRM |
Paddle | Look up customers, subscriptions, transactions, and revenue in your Paddle account |
Honeycomb | Query traces, errors, and latency, and check SLOs and alerts in Honeycomb |
HubSpot | Look up and update contacts, companies, deals, and tickets in HubSpot |
Datadog | Search logs, metrics, traces, monitors, and incidents in Datadog |
Zapier | Run your Zapier actions across thousands of apps |
MCP Server | Connect Operator to any compatible external server using MCP (Model Context Protocol) |
Connect a tool
Connections are set up from the Connections page inside Customize. You need to authorize each tool individually before Operator can use it.
How to connect a tool
In Operator, select Customize from the left navigation, then select Connections.
Find the tool you want to connect.
Select Connect next to the tool name.
Follow the authorization steps for that tool — you may be redirected to the tool's own login or permissions page.
Once authorized, the connection status updates to Connected. Operator can now use that tool in your conversations.
You can also connect a tool from the Operator message composer: click the plus icon, select Connections, and pick the tool.
Tip: Authorization requirements vary by tool. Make sure you have the right permissions in the external tool before connecting — for example, admin access in Notion or owner-level access in a GitHub organization.
Connect a tool that isn't listed
If the tool you need isn't listed, you can connect any compatible MCP server.
In Operator, select Customize from the left navigation, then select Connections.
Select MCP Server.
Enter a name for the connection (optional) and the server URL.
Leave Authentication on OAuth unless your server needs a token. Most servers register automatically.
Click Add. Follow any sign-in steps the server asks for, and the connection appears in your list.
Use a Connection in a conversation
Once a tool is connected, you can ask Operator to use it directly in your conversation. You don't need to switch to the Connections page — just describe what you need.
Example prompts
"Find all Linear issues tagged 'billing' that were opened this week."
"Search our Notion workspace for our escalation policy."
"Show me all open GitHub pull requests in our main repository."
"Query Snowflake for last month's conversation volume by channel."
Operator will use the connected tool to retrieve or act on the data and return the results in the conversation.
Disconnect a tool
You can disconnect a tool at any time from the Connections page. Disconnecting removes Operator's access to that tool — it will no longer be able to retrieve data or take actions through that connection. Disconnecting only removes your own access — it doesn't disconnect the tool for other teammates who connected it separately.
How to disconnect a tool
In Operator, select Customize from the left navigation, then select Connections.
Find the connected tool you want to remove.
Select the three-dot menu (…) next to the tool and select Disconnect.
Confirm the disconnection. The tool's status updates to Not connected and Operator can no longer use it.
FAQs
What is MCP Server?
MCP Server (Model Context Protocol) lets you connect Operator to any compatible external server — including custom-built tools and services not listed as standard connectors. Set it up from Operator > Customize > Connections > MCP Server.
Do I need admin access to set up a Connection?
Whether you need admin access to set up a Connection depends on the tool, because authorization requirements vary by tool. For some tools — such as Notion or GitHub — you may need admin or owner-level access in the external tool to complete the connection. Check the permissions requirements for each tool before connecting.
What permission do I need to connect a tool?
You need the Can access Fin Operator permission to connect a tool. You don't need to be a workspace admin.
Can all teammates use a Connection once it's set up?
Teammates can't share one connection, because connections are per teammate: each teammate connects a tool for themselves. Operator only sees what that teammate can already see in the tool. Connecting needs the Can access Fin Operator permission, not admin rights.
A connector I need isn't listed — what should I do?
If a connector you need isn't listed, check Operator > Customize > Connections for the connectors available in your workspace. For a tool that isn't listed, use MCP Server to connect to any compatible MCP server.
Will connecting a tool give Operator access to all my data in that tool?
Connecting a tool doesn't give Operator access to all your data in that tool. Operator's access to a connected tool is limited to what you authorize during the connection setup, and it acts within the permissions granted — it doesn't have unrestricted access to the external tool.
Need more help? Get support from our Community Forum
Find answers and get help from Intercom Support and Community Experts