Skip to main content
Automations let a Roomote agent start repeatable work without waiting for a teammate to write the same prompt each time. An automation combines a saved instruction with a trigger, optional execution preferences, and a report destination. Every run becomes a distinct session and can answer directly or delegate a normal task when repository or workspace work is needed. Automations are not a separate agent identity. They are one way to launch the same Roomote agent workflows that teammates can start from the dashboard, chat, source control, Linear, or the API.

​
When to use an automation

Use an automation when the work has a repeatable input and a clear review path:
  • scheduled summaries, triage, audits, or housekeeping
  • pull request reviews and conflict checks
  • source-control or provider events that should start a bounded workflow
  • recurring team updates delivered to a channel, direct message, or email
  • a custom prompt that should be available through Run now or a private webhook
Use a regular session when the request needs an evolving conversation, clarification, or a one-off decision. Use a task when you need an independently controllable execution with a terminal, logs, diff, preview, or artifacts. Automation runs use those same surfaces rather than creating a separate execution model.

​
How an automation runs

  1. A schedule, provider event, manual action, or webhook starts the automation.
  2. Roomote opens a new session with the saved prompt and the run’s trigger context.
  3. The session answers from its available integrations when that is enough. If workspace work is needed, it delegates a task using the configured routing preference.
  4. The session reports meaningful findings, completed results, blockers, or questions to its configured destination. Routine success and no-change runs can remain silent unless the prompt asks for a report.
  5. The run remains available in the web app as a session, with links to any delegated tasks, pull requests, artifacts, costs, and the final report.
Each run is independent. Starting one automation does not cancel or serialize another run, and a queued run means Roomote accepted the session turn, not that the delegated work has completed.

​
Built-in and custom work

Admins manage built-in automations and deployment-wide settings. Members can create and manage the custom automations they own; administrators can manage all custom automations, including those without a creator. The configuration guide explains built-in controls, while the custom automation guide covers saved prompts, schedules, destinations, models, and execution targets. Built-in automations cover common team workflows: The exact provider support, permissions, and output behavior differ by automation. Review the configuration guide before enabling a built-in automation instead of assuming every one starts a coding task or supports every provider.

​
Choose the review path first

Before enabling automation, decide where a teammate will inspect the result:
  • a session in the web app when the run has no external destination
  • a Slack, Discord, Microsoft Teams, Telegram, or email report when the team needs a notification or replyable thread
  • the Results inbox when eligible reports should become a shared review queue with prepared follow-up work
Reports contain the finished announcement or result. Intermediate research notes and tool progress are excluded from a posted automation report. Session-backed chat reports can be replyable; reply in the thread Roomote started to continue the session without mentioning Roomote. Deterministic alerts such as Inference Provider Usage Alerts are informational cards and do not create a task or session.

​
Start with a bounded rollout

Make sure the basics are in place before enabling a recurring workflow:
  • source control is connected for pull request and repository automations
  • a communications provider is connected when the automation posts to a channel or direct message
  • at least one healthy environment exists for repositories that need workspace execution
  • the team knows where the automation will report and who owns its runs
Start with one or two automations tied to a real team habit. Use Run now to check the prompt, routing, permissions, and destination before waiting for the next trigger. After a successful manual launch, choose Follow session in the confirmation to open the exact session that was created. Then review the transcript, logs, diffs, previews, artifacts, and final summary using the same evidence standard as manually started work.

​
Continue with the guides