Skip to main content
Automations let Roomote work without waiting for a teammate to write a new prompt every time. It’s the ultimate chore-handling hack. Use them after your first environment, Slack connection, and GitHub connection are working well. Automations are most useful when your team already trusts the normal task review flow and wants Roomote to keep an eye on repeated work.

​
Before you turn them on

Make sure the basics are in place:
  • GitHub is connected for PR and repository automations
  • Slack is connected for automations that post updates to channels
  • Roomote has at least one healthy environment for the repositories it should work in
  • the team knows where automation output will appear
Automations can create useful work quickly. Start with one or two that map to a real team habit, then expand once the signal is good.

​
Other automations

This section controls automations that react to pull requests and repository state.
AutomationWhat it doesGood first use
Review CodeReviews pull requests automatically or on demandAdd an extra reviewer for regressions, risky changes, and missed tests
Resolve PR ConflictsLooks for merge conflicts and helps fix them on open PRsKeep long-running Roomote branches from getting stuck
For Review Code, decide whether Roomote should review new commits automatically and whether draft pull requests should be included. If your team treats drafts as active collaboration, include them. If drafts are noisy or half-formed, keep them out until they are ready. For Resolve PR Conflicts, pick a schedule, PR age cap, and label. The label is the team-controlled opt-in for scheduled scans. Make sure the label exists in your repositories, add it to PRs where you want Roomote to attempt conflict resolution, and remove it when a human should handle the conflict instead. Roomote only tries this on labeled PRs that are still active, and it skips PRs older than the age cap you set so stale work does not keep re-entering the queue.

​
Slack automations

The Slack section starts with Auto-respond channels. Use it to let Roomote start a task from new top-level messages in selected Slack channels, even when nobody mentions Roomote directly. You can add multiple channels, and each one can include its own optional instructions. Good first examples:
  • #ask-engineering
  • #bugs
  • #support-inbound
  • #ops-requests
Invite Roomote to every auto-respond channel before you save it.

​
Automations for Roomote Managers

The manager section controls the shared Manager Channel plus recurring manager-facing updates and suggestions.
AutomationWhat it postsTypical cadence
Automation outputThe shared Manager Channel destinationConfigure once
Weekly Manager StatsA weekly summary of Roomote activityWeekly
Code Quality AuditorCode quality follow-up work from recently merged PRsEvery hour, every 6 hours, daily, or weekly
Suggest Self-improvementsProcess improvement ideas based on PR feedbackDaily, weekly, or every two weeks
Suggest IdeasUseful coding work Roomote thinks the team could doDaily or weekly
Triage Dependabot AlertsSuggested follow-up tasks for open dependency alertsDaily or weekly (beta)
CI Failure TriageAutomatic repro-and-fix tasks for failing default-branch CI runsImmediate via webhook (beta)
Summarize Merged PRsA digest of recently merged pull requestsDaily or weekly
Set Automation output first. This is the shared Slack channel for manager-facing posts, suggestions, summaries, and setup alerts. Invite Roomote to that channel before you save it. For Code Quality Auditor, Roomote inspects recently merged PR diffs and only posts high-confidence maintainability issues worth a real follow-up task. It is meant to catch confusing abstractions, file bloat, spaghetti branching, muddled ownership, wrong-layer logic, and other quality regressions, not correctness bugs or security issues. If your org has beta automations enabled, Triage Dependabot Alerts uses that same Manager Channel. It scans open GitHub Dependabot alerts across your active repositories and suggests tightly scoped follow-up update tasks. It does not open PRs directly from the scheduled scan. With beta automations enabled, CI Failure Triage reacts the moment a CI workflow run fails on a repository’s default branch: GitHub sends Roomote a webhook, Roomote posts an “investigating” message to the Manager Channel right away, and the investigation’s outcome lands in that same thread. When a failure persists (it is not already fixed by a newer run and is not a one-off flake), Roomote starts a fix task that reproduces the failing job inside the repository’s configured environment, finds the root cause, opens a PR with the fix, and posts one summary to the Manager Channel when it finishes. There is no schedule: failures are picked up the moment GitHub reports them, and Run now scans every covered repository on demand. Only repositories that belong to a configured Roomote environment are triaged. For Code Quality Auditor, Roomote inspects recently merged PR diffs and only posts high-confidence maintainability issues worth a real follow-up task. It is meant to catch confusing abstractions, file bloat, spaghetti branching, muddled ownership, wrong-layer logic, and other quality regressions, not correctness bugs or security issues.

​
Add instructions to reduce noise

Several automations include an Additional instructions field. Use it to tell Roomote what good signal looks like for your team. Helpful instructions are specific: 
Prioritize changes that reduce repeated support escalations.
Skip suggestions that require product approval before engineering can start.
For merged PR summaries, call out customer-visible changes first.
Avoid broad instructions such as “only send good ideas.” Roomote needs to know what your team considers useful, risky, or out of scope.

​
Run an automation now

Some automations include a Run now action. Use it when you want to test the current configuration before waiting for the next scheduled run. After you run one, check the destination channel and the task view. A healthy automation should leave enough context for a reviewer to understand why Roomote posted and what should happen next.

​
Use Slack workflows for custom triggers

For workflows that are specific to your team, use Slack’s own workflow builder and end the workflow with a Roomote mention. Good custom triggers include:
  • send new bug-channel posts to Roomote for triage
  • turn operational requests from another system into Roomote tasks
  • ask Roomote to gather diagnostics when a support escalation arrives
This keeps custom routing in Slack while still letting Roomote run a normal, reviewable task.

​
Possible issues

  • Nothing posts to Slack. Check that Slack is connected, Roomote is invited to the Manager Channel, and the automation is enabled.
  • Suggestions are too broad. Add narrower instructions about what to prioritize and what to ignore. Also give us feedback, we’d love to improve these further.
  • Review Code comments on too much. Turn off draft PR review or adjust when automatic reviews run.
  • Conflict resolution starts on the wrong PRs. Use the configured label as the opt-in boundary and remove it from PRs that need human handling.