You can now configure event-based triggers to automatically invoke Duo Flows and agents in response to GitLab events — without any manual intervention. Supported trigger events include: * **Draft → Ready for review** — trigger a flow when a draft MR is marked ready. Configure triggers in **AI \> Triggers** within your project. https://docs.gitlab.com/user/duo_agent_platform/triggers/ ## Summary Full AI review is wasted on WIP code. This trigger fires only when the developer removes the draft status, signalling they are done, enabling a focused compliance and readiness review at the Create stage. **Audit Event Name:** `merge_request_ready` --- ## Agent Examples ### Agent 1 — Full Compliance Review Agent Triggers only when draft is removed. Performs a security-focused compliance review using the MR context, vulnerability data, and security finding details. **Tools:** - Build Review Merge Request Context - List Merge Request Diffs - List Vulnerabilities - Get Security Finding Details - Create Merge Request Note ### Agent 2 — Readiness Checklist Agent Checks for complete description, updated tests, existing documentation, and up-to-date branch, then posts a pass/fail checklist as a comment. **Tools:** - Get Merge Request - Grep - Find Files - Get Repository File - Run Git Command - Create Merge Request Note --- ## Implementation Notes & Caveats > :warning: **No audit event exists for draft state change.** This event is currently inferred from the webhook system, not the audit event enum. Needs to be added or confirmed via [gitlab-com/content-sites/handbook!18106](https://gitlab.com/gitlab-com/content-sites/handbook/-/merge_requests/18106) before shipping.