> ## Documentation Index > Fetch the complete documentation index at: https://modem.ai/docs/llms.txt > Use this file to discover all available pages before exploring further. # Overview > Connect your tools to capture feedback and take action Modem connects to the tools where your users and team already work. Integrations serve two purposes: **capturing data** (messages, issues, emails) so Modem can analyze it, and **giving the agent tools** to take action on what it finds. Integrations are grouped by what they bring into Modem. Most are connected from **Settings** → **Integrations** in the dashboard. External MCP servers have their own page under **Settings** → **External MCPs**, and each member adds their own Cursor or Devin API key under **Profile** → **Coding Integrations**. ## Chat The conversations where your team and customers already talk. Capture messages from selected channels. Also lets you talk to the Modem Agent directly from Slack. Capture messages from Discord servers. Also lets you talk to the Modem Agent by mentioning the bot. Capture channel messages from Microsoft Teams. ## Social Public conversations about your product. Monitor public posts matching search queries you define. ## Customer Support Tickets, support chats, and customer-reported issues. Capture conversations in real time. The agent can also search, reply, and manage tags. Capture Zendesk tickets in real time, including replies, internal notes, and ticket metadata. Capture support issues via triggers. The agent can also search, reply, and add notes. Capture support threads: customer emails, chats, and internal notes. Capture shared inbox conversations: customer messages, replies, and internal comments. Capture feature requests, bug reports, comments, and votes from your feedback boards. Route email feedback to Modem through a dedicated inbound address. ## Video Conferencing Recorded meetings and sales calls, captured as searchable transcripts. Capture transcripts from your recorded Gong calls, linked to the people who spoke on them. Capture transcripts and summaries from your Fathom-recorded meetings, linked to the people who spoke on them. ## Sales & Revenue CRM records and billing signals from your go-to-market stack. Query standard and custom CRM objects read-only, with core account and opportunity context kept synced. Sync a read-only mirror of your billing data and trigger automations on subscriptions, trials, and failed payments. ## Project Management Planning systems, so signals can become work. Search, create, and update issues. Link topics to existing tickets. Capture issues and comments in real time. The agent can also search, create, and update issues. Capture customer support requests from Jira Service Management, including public replies and internal notes. Search, read, and create pages and database entries in your Notion workspace. ## Product Analytics Behavioral context from your analytics tools. Both are query-based: the agent asks them questions on demand, and nothing is ingested into Modem. Query product analytics, feature flags, experiments, and error tracking data. Query events, funnels, retention, and segmentation. ## Code & Coding Agents Repository activity, error tracking, and coding agents. Sync issue and PR metadata: titles, descriptions, comments, labels, and review discussions. Does not read source code. Sync merge request, issue, and comment metadata. The agent can also search, create, update, and comment. Ingest user feedback into topics. The agent can also search issues, read stack traces, and resolve or assign them. Delegate implementation tasks to Claude Code, Cursor, or Devin, enriched with Modem context. ## Extending Modem Connect your own tool servers so the agent can use tools Modem does not provide natively. Connect any MCP-compatible tool server to extend the agent's capabilities. Looking for the opposite direction, using Modem from Claude Code, Cursor, or another MCP client? See the [Modem MCP Server](/docs/api/modem-mcp-server). ## What Each Data Source Captures These integrations continuously capture messages and events, feeding them into Modem's analysis pipeline. Messages are grouped into [topics](/docs/guides/topics), classified by type (bug, feature request, praise, complaint), and linked to [people](/docs/guides/people) and [companies](/docs/guides/people#companies). | Source | What's captured | Historical backfill | Real-time | | - | - | - | - | | Slack | Messages, reactions, threads | 30 days | Yes | | Discord | Messages, reactions, threads, forum posts | 30 days | Yes | | Microsoft Teams | Channel messages, replies, reactions, edits | 30 days (≤500/channel) | Yes | | GitHub | Issue/PR titles, descriptions, comments, labels | 30 days | Yes (webhooks) | | GitLab | MR/issue titles, descriptions, comments, labels | 30 days (≤100 comments per item) | Yes (webhooks) | | Intercom | Conversations, replies, notes, CSAT, contacts | 30 days (≤500 convs) | Yes (webhooks) | | Zendesk | Tickets, replies, internal notes, ticket metadata | None | Yes (webhooks) | | Pylon | Issues, customer and teammate replies, internal notes | 30 days (≤500 issues) | Yes (webhooks) | | Plain | Thread emails, chats, internal notes, thread metadata | 30 days (≤500 threads) | Yes (webhooks) | | Front | Conversations, replies, internal comments, status | 90 days (≤500 convs) | Yes (webhooks) | | Canny | Board posts, comments, votes, post status | Full history (≤10,000 posts) | Yes (webhooks) | | Jira | Issues, comments, issue metadata | None | Yes (webhooks) | | Jira Service Desk | Requests, public replies, internal notes | 30 days (≤2,000 requests) | Yes (webhooks) | | Stripe | Customers, subscriptions, invoices, payments | Full history (on connect) | Yes (webhooks) | | Gong | Call transcripts, participants, call metadata | 30 days (≤100 calls) | Polled (\~15m) | | Fathom | Meeting transcripts, summaries, participants | 30 days (≤100 meetings) | Yes (webhooks) | | X | Public posts matching your queries, authors, replies | None | Polled | | Email | Email body and threads | None | Yes | For Microsoft Teams, Pylon, Plain, Canny, and Jira Service Desk, the backfill is optional, and an admin starts it from the integration's settings page. The other backfills start automatically. All data sources let you choose what to monitor: specific Slack channels, Discord channels, GitHub repositories, Pylon triggers, X search queries, or a dedicated email address. Start narrow and expand as needed. Several integrations are both data sources and agent tools. Slack lets your team talk to the agent via DM or @mention, and Discord by mentioning the bot. Intercom lets the agent search, reply to, and manage conversations (when write access is enabled). Jira captures issue activity and lets the agent search, create, and update issues. Pylon captures support issues and lets the agent reply, add notes, and manage tags. ## Setup Most integrations are configured from **Settings** → **Integrations** in the Modem dashboard. Data sources connect through OAuth (Slack, Discord, Intercom, Zendesk, Front), an app install (GitHub, Sentry), an API key (Pylon, Plain, Canny), or a generated address (Email). Agent tools use OAuth (Linear, Notion, Mixpanel) or API keys (PostHog, Coding Agents). External MCP servers use no auth, a bearer token, custom headers, or OAuth 2.1, depending on the server. Each integration page has step-by-step setup instructions. Integrations marked **Beta** (X, Front, Mixpanel) are still rolled out per organization. If you don't see one in your dashboard, email [support@modem.dev](mailto:support@modem.dev) to request access. ## Cross-Platform Identity When you connect multiple data sources, Modem links people across platforms using shared identifiers like email addresses. A user who messages you on Slack, files a GitHub issue, and emails support gets a single unified profile with their full history. This also works at the company level. Email domains and other signals help associate people with companies, giving you an account-level view of feedback across all sources. See [Companies & People](/docs/guides/people) for details. ## Next Steps Connect your first integration in 5 minutes. See what the agent can do with your connected tools. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.