> ## Documentation Index
> Fetch the complete documentation index at: https://docs.newmote.dev/llms.txt
> Use this file to discover all available pages before exploring further.
# Integrations overview
> Connect the tools that give Roomote the right context and operating surfaces.
export function IntegrationName({fallbackIcon, href, icon, name}) {
const manualIconFallbacks = {
slack: {
viewBox: '0 0 24 24',
strokeWidth: 1.6,
path: 'M14.5 2A1.5 1.5 0 0 0 13 3.5v5A1.5 1.5 0 0 0 14.5 10h0A1.5 1.5 0 0 0 16 8.5v-5A1.5 1.5 0 0 0 14.5 2ZM19 8.5V10h1.5A1.5 1.5 0 1 0 19 8.5ZM9.5 22a1.5 1.5 0 0 0 1.5-1.5v-5A1.5 1.5 0 0 0 9.5 14h0A1.5 1.5 0 0 0 8 15.5v5A1.5 1.5 0 0 0 9.5 22ZM5 15.5V14H3.5A1.5 1.5 0 1 0 5 15.5ZM22 14.5a1.5 1.5 0 0 0-1.5-1.5h-5a1.5 1.5 0 0 0-1.5 1.5h0a1.5 1.5 0 0 0 1.5 1.5h5a1.5 1.5 0 0 0 1.5-1.5ZM15.5 19H14v1.5a1.5 1.5 0 1 0 1.5-1.5ZM2 9.5A1.5 1.5 0 0 0 3.5 11h5A1.5 1.5 0 0 0 10 9.5h0A1.5 1.5 0 0 0 8.5 8h-5A1.5 1.5 0 0 0 2 9.5ZM8.5 5H10V3.5A1.5 1.5 0 1 0 8.5 5Z'
},
pylon: {
viewBox: '0 0 164 168',
filled: true,
path: 'M66.1 4.1C48.8 7.5 30.6 18.3 19.2 32 12.6 40 4.7 56 2.5 66 .1 76.5.3 93.3 2.8 103.1c9.1 34.7 38.5 59.2 73.7 61.6 34.7 2.3 67.5-18.6 80.5-51.1 18.4-45.9-9.2-97.8-58-109.1C91.9 2.9 73.4 2.5 66.1 4.1ZM72 31.5V40H38.6l2.7-2.8c3.8-4 12.4-9 20.4-11.7C72.2 21.7 72 21.6 72 31.5ZM103.7 26.7c18 6.7 32.8 23.5 37.7 42.4 2 7.8 2.1 22.2.1 29.9-5.4 21.3-23.1 39.5-43.7 44.8-3.1.8-5.9 1.2-6.2.9-.3-.3-.6-27.7-.6-61V23.3l3.7.7c2 .3 6.1 1.6 9 2.7ZM72 67v7H21l1.6-7 1.7-5.8H72V67ZM72 101v7H24.9l-1.4-3.3c-.7-1.7-1.6-4.9-2-7l-.7-3.7H72v7ZM72 136.4v8.4l-3.7-.9c-9.5-2.1-19.6-7-26.3-12.8l-3.5-3H72v8.3Z'
}
};
const manualIcon = fallbackIcon ?? manualIconFallbacks[icon];
return
{manualIcon ? : }
{name};
}
Integrations do two different jobs in Roomote:
* some are workflow surfaces where teammates start or continue work, such as Slack, GitHub, and Linear
* others give Roomote more context inside a task, such as docs, tickets, monitoring, analytics, or data systems
Slack and GitHub are part of the core onboarding path. Most other integrations are best added after the first environment and first task flow already feel solid.
## Connection patterns
You will usually see one of these setup models:
* **Admin connection once**: an admin connects the integration for the organization from **Settings > Integrations**
* **Enable first, then teammates link accounts**: an admin enables the integration, then each teammate links their own account from [Personal Settings](/personal-settings) when they need it
* **Workspace plus user identity**: the organization connects the integration, then individual users link their identity so Roomote can associate actions correctly
## Manage available tools
Some connected integrations expose a **Manage tools** action in **Settings > Integrations**. Admins can use it to restrict the types of operations Roomote can make with the service.
Use this as a coarse permissions system – eg letting only read vs write operations, or restricting to a certain type of entity. The list varies depending on the integration.
Some integrations can only list tools after the first user links their account from [Personal Settings](/personal-settings).
## Supported integrations
| Integration | Best for | Connection model |
| -------------------------------------------------------------------------------------------- | ------------------------------------------------- | ---------------------------------------------------- |
| | Starting and continuing tasks in team threads | Connect the workspace and invite the app to channels |
| | Repository access, PR review, and follow-up work | Install the GitHub app |
| | Project and task context from Asana | Admin connection once |
| | Monitoring and incident context | Admin connection once |
| | Read-only warehouse and dataset queries | Admin connection once |
| | Prompts, runs, and evaluation context | Enable first, then teammates link accounts |
| | Google Drive files plus Docs and Sheets context | Enable first, then teammates link accounts |
| | Dashboards, alerting, and monitoring context | Admin connection once |
| | Issues, projects, and JQL-backed issue context | Enable first, then teammates link accounts |
| | Turning issues into Roomote work | Workspace plus user identity |
| | Database inspection in Neon | Enable first, then teammates link accounts |
| | Shared docs and database context | Enable first, then teammates link accounts |
| | Product analytics, experiments, and error context | Admin connection once |
| | Customer issue and account context | Admin connection once |
| | Project and service context from Railway | Admin connection once |
| | Error and performance investigation | Admin connection once |
| | Data warehouse exploration | Admin connection once |
| | Read-only database access in Supabase | Enable first, then teammates link accounts |
| | Deployments, logs, and domain availability | Admin connection once |
## New Integrations
We're constantly adding new integrations, on-demand.
There's a form on the page to request more, we usually add it in less than a day.
## A practical order
For most teams, this order works well:
1. Slack
2. GitHub
3. The first environment
4. One task-tracking integration (Linear, Jira, etc) if your team already works there
5. One monitoring or data integration (Sentry, Grafana, Railway, Vercel, etc) when investigations need it
6. One knowledge base integration (Notion, etc) to get tasks done directly from PRDs and other docs
}