Available Pre-built Automations
Issue to Pull Request
Implements issues from your issue tracker and creates pull requests.
GitHub PR Review Assistant
Reviews pull requests and posts feedback as a comment.
GitHub Repository Monitor
Watches a repository for events and triggers agent actions in response.
Slack Channel Monitor
Listens to a Slack channel and triggers an agent when a message matches a pattern.
agent-canvas launcher include Automation Server, so they can run agents on a schedule or in response to external events.
What You Can Do
In theAutomate view, you can:
- Browse existing automations
- Inspect automation configuration and activity
- Enable or disable automations
- Edit an automation’s LLM profile for future runs
- Work with recommended automation flows
Templates
The Templates page groups pre-built automations into Suggested (up to eight cards) and More templates. The Beta label appears on individual cards rather than as a section heading. With nothing connected, Suggested starts with proven default templates. Templates that use a connected Git provider, an installed MCP server, or an integration reported by the instance move ahead of the defaults. A template moves to the end of More templates only when the instance reports a different provider or integration type and you have not connected the one the template needs. The catalog includes Bitbucket Data Center code review and Jira Data Center issue to Bitbucket Data Center PR templates on all backends. On a compatible self-hosted deployment, set up Bitbucket Data Center and, for the issue-to-PR template, Jira Data Center. Confirm the automation service supports the required event source before creating one. A Data Center template may be listed even if your backend cannot run it. For the Bitbucket repository picker and cloning behavior, see Repository picker providers. On a self-hosted instance with no detected setup for a Git provider used by a template, selecting the template first shows guidance for connecting that provider through MCP or a token. Continue to the provider’s MCP install, or cancel; when a native integration, matching MCP server, or matching token secret is already available, the template setup opens without this notice. Cloud and local backends do not show this self-hosted notice.How Creation Flows Usually Start
In practice, new automation setup starts in one of two ways:- From a conversation, where you ask OpenHands to
create an automationfor you - From a recommended automation flow in the
Automationsview
Edit an Automation’s LLM Profile
Open an automation, selectEdit, and use the LLM profile dropdown to change which saved profile future runs use. If an automation already has a profile, the edit dialog pre-selects it.
Changing the LLM profile affects future automation runs. It does not rewrite previous run history.
Select an Agent Profile for an Automation
When the active backend advertises agent-profile support, the automation setup and edit dialogs include an optional agent profile selector. Choose a saved agent profile to use for automation runs instead of the default agent. When a saved agent profile is selected:- The stable
agent_profile_ididentifies the profile sent to the backend. - The automation uses the selected agent profile instead of an LLM profile. Editing an automation clears any existing legacy model selection.

