Skip to main content
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 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.

​
Supported integrations

​
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