Workflow, Prompts, and Review Notifications
Workflow settings tell MergeLoom which work can run, which code host receives review output, and which quality checks must happen before review.
Open the customer controller, then go to Workflow.
Workflow Settings
Section titled “Workflow Settings”Configure:
- intake source
- code output target
- managed intake label or tag
- ready, in-progress, review, blocked, and done states
- Scheduled intake
- Quality Agent controls
- diff guard thresholds
- review notification webhooks
New workspaces start with Scheduled intake off. Keep it off until the execution mode, integrations, repository catalog, and first test ticket are ready.
Quality Agents
Section titled “Quality Agents”Quality Agent settings live with Workflow because they control whether a ticket should move from intake to implementation to review.
Common controls include:
- Clarity Agent minimum score and extra scoring requirements
- Investigation Agent
- validation gate
- bounded repair attempts
- Review Agent
- review fix and confirmation
- Diff Guard
For the execution stages and audit output, see Workflow and Quality Agents.
Prompts
Section titled “Prompts”Open Prompts for organization-wide context and review/publish templates.
Use prompt settings for:
- organization context that should apply to all runs
- review request body templates
- completion comment templates
Worker system prompts are managed by MergeLoom and are not editable from the customer controller.
Keep prompts operational. The best prompts tell MergeLoom where to look, what constraints matter, and what must be validated.
Review Notifications
Section titled “Review Notifications”Review notifications post published PR/MR links to Slack or Microsoft Teams.
In Workflow, configure:
- Slack incoming webhook URL
- Teams incoming webhook URL
- optional review notification template
Notifications are sent by the controller after review output is published. If a notification fails, the PR/MR can still exist; check controller-side activity or contact MergeLoom support for notification errors.
Cloud Hosted and Self Hosted
Section titled “Cloud Hosted and Self Hosted”Workflow, prompt, and notification settings live in the controller for both deployment modes.
Cloud Hosted runs those rules on MergeLoom-managed workers. Self Hosted workers receive the same job rules when they start a job and run them inside your environment.
What to Check Before Saving
Section titled “What to Check Before Saving”- The selected intake source matches the connected tracker.
- The selected code output target matches the connected code host.
- Status names match the real tracker states.
- Scheduled intake is off until the first test ticket is ready.
- The repository routing label is
repo-<alias>. - Notification webhooks are only added after your team approves the target channel.