Create workflow persistence (agent-initiated, limited privileges)
Accessible via ai_workflows scope token. Does not accept agent_privileges or pre_approved_agent_privileges.
Authorizations
Section titled “ Authorizations ”Request Body
Section titled “ Request Body ”object
The ID or path of the workflow project
Example
1The ID or path of the workflow namespace
Example
1The ID of AI Catalog ItemConsumer that configures which catalog item to execute.
Example
1Optional parameter to start workflow in a CI pipeline.This feature is currently in an experimental state.
Example
trueGoal of the workflow
Example
Fix pipeline for merge request 1 in project 1Workflow type based on its capability
Example
software_developerWhen this is enabled Duo Agent Platform may stop to ask the user questions before proceeding. When it is disabled Duo Agent Platform will always just run through the workflow without ever asking for user input. Defaults to true.
Example
trueContainer image to use for running the workflow in CI pipeline.
Example
registry.gitlab.com/gitlab-org/duo-workflow/custom-image:latestSource branch for the CI pipeline. Uses default branch when not specified.
Example
mainEnvironment for the workflow.
The ID of AI Catalog ItemVersion that sourced flow config used by the workflow.
Example
1Additional Context required by the Flow, in JSON format. Contains an array of context details, where each detail is a Hash with a minimum of “Category” and “Content” keys.
object
The category of the context detail
The content type of the context detail
Whether or not the workflow should use a shallow clone of the repository during its execution. Defaults to true.
Example
trueIID of the Issue noteable that the workflow is associated with.
Example
123IID of the MergeRequest noteable that the workflow is associated with.
Example
123Responses
Section titled “ Responses ”Created
Validation failed
Unauthorized
403 Forbidden
Not found