# Build custom flows in minutes with the Flow Creator agent

DevFeed: [Build custom flows in minutes with the Flow Creator agent](<https://devfeed.tech/articles/build-custom-flows-in-minutes-with-the-flow-creator-agent-89.md>)

Original publisher: [Read original article](<https://about.gitlab.com/blog/flow-creator-agent/>)

Author: Rebecca Carter

Published: 2026-08-20T00:00:00Z

Content type: release

Language: en

Sources: [GitLab](<https://devfeed.tech/sources/gitlab.md>)

Topics: [AI Chat](<https://devfeed.tech/topics/ai-chat.md>)

Tags: [agentic-ai](<https://devfeed.tech/tags/agentic-ai.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [automation](<https://devfeed.tech/tags/automation.md>), [features](<https://devfeed.tech/tags/features.md>), [identity](<https://devfeed.tech/tags/identity.md>), [product](<https://devfeed.tech/tags/product.md>), [security](<https://devfeed.tech/tags/security.md>)

## AI overview

GitLab 19.3 introduces the Flow Creator agent, which turns plain-language workflow descriptions into runnable Custom Flow definitions. It clarifies ambiguous requirements before building and keeps flow activation subject to role-based controls and scoped service-account permissions.

## Source excerpt

Custom Flows already let teams turn manual, multi-step work into automation that runs on GitLab events. But writing one meant learning the Flow Registry schema first. That requirement is a real barrier. The people who understand a workflow best aren't always the same ones who know a YAML schema. In GitLab 19.3, the Flow Creator agent removes that requirement. Describe the flow you want in your own words, and it responds with a complete, runnable definition. When good automations stopped at the schema Consider two people who know exactly what should be automated, but not how to build it. The security analyst triages vulnerability reports every day and knows which patterns are false positives and who owns each affected dependency. None of that knowledge is captured in a schema they have never used. The planning lead knows what should happen next when a work item changes status. The automation is obvious to them. The Flow Registry syntax is not. Writing a flow meant learning that schema before any of this knowledge could become automation. That requirement limited who could author flows to people with schema familiarity, not people with process knowledge. The result is a gap between who understands the work and who can automate it. That gap effectively slows down automations across the entire software lifecycle especially where bottlenecks already lurk. Bring flow building to everyone who understands the work Flow Creator is a foundational agent within GitLab Duo Agent Platform, available via Agentic Chat. Invoke the agent, describe what you want the flow to do in plain language, and it produces a complete flow definition. For example, "When a work item is created with the label security-triage, check it against our known false-positive patterns, find the affected dependency and its owner, and post a severity assessment as a comment." This simple explanation gives the agent a trigger, steps, and an output target. You don't have to get the description perfect on the fir