Setup a pre-built automation

Faheem Code ships with a set of pre-built automations for the most common agent workflows. Each one is a ready-to-use starting point — pick the one that fits your use case, connect it to the right backend, and you can have an automation running in minutes.

Available pre-built automations

Automation	What It Does
GitHub PR Review Assistant	Automatically 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

---

Backends created by the faheem-code launcher include Automation Server, so they can run agents on a schedule or in response to external events.

What you can do

In the Automate 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

How creation flows usually start

The Automations view is mainly for browsing and managing automations that already exist.

In practice, new automation setup starts in one of two ways:

• From a conversation, where you ask Faheem Code to create an automation for you
• From a recommended automation flow in the Automations view

For recommended automations that support a direct form setup, Faheem Code checks the active backend's capabilities and any prerequisites, then guides you through the required input fields, a review step, and creation. If direct form setup is unavailable, it offers a conversation-assisted setup instead. Review the proposed configuration before creating an automation.

Some catalog entries ship a script bundle — a packaged set of files that install as a deterministic automation — rather than a prompt-based preset. Script-bundle entries run their own logic for tasks like polling, deduplication, and fixed API calls, using the agent only for the parts that genuinely require judgment. When a catalog entry supports a bundle install, the setup form handles packaging and upload automatically; you just fill in the required fields.

Catalog entries that accept repositories can also collect multiple repositories in a single field, so one automation can monitor several repos at once.

For a detailed walkthrough, see Creating Automations.

Note

Some recommended automations depend on integrations that cannot be auto-installed as MCP servers on this backend (for example, Jira's HTTP/OpenAPI-only integration). These appear on the recommendation card with a Needs external setup label. The MCPs to connect count only covers integrations the install flow can connect automatically. You must configure externally-hosted integrations yourself before the automation can use them.

Automations run against the active backend. Use Manage Backends to see and switch which backend your automations run on.

Edit an automation's LLM profile

Open an automation, select Edit, 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.