<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/extend-gitlab-duo-agent-platform-into-your-business-systems-xftgu5ud1" -->

---
title: Extend GitLab Duo Agent Platform into your business systems
description: This tutorial shows how to connect Salesforce errors to GitLab Duo Agent Platform so they turn into GitLab issues with root-cause analysis. A custom GitLab...
canonical: https://daily.dev/posts/extend-gitlab-duo-agent-platform-into-your-business-systems-xftgu5ud1
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Extend GitLab Duo Agent Platform into your business systems | daily.dev
og:description: This tutorial shows how to connect Salesforce errors to GitLab Duo Agent Platform so they turn into GitLab issues with root-cause analysis. A custom GitLab...
og:url: https://daily.dev/posts/extend-gitlab-duo-agent-platform-into-your-business-systems-xftgu5ud1
og:image: https://api.daily.dev/og/posts/xftgu5ud1.png
og:image:alt: Extend GitLab Duo Agent Platform into your business systems
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Extend GitLab Duo Agent Platform into your business systems

**[GitLab](https://daily.dev/sources/gitlab)** · 12 min read · 0 upvotes · 0 comments

## Summary

This tutorial shows how to connect Salesforce errors to GitLab Duo Agent Platform so they turn into GitLab issues with root-cause analysis. A custom GitLab flow, written as one YAML file, reads the error, investigates the codebase, and opens an issue citing file paths, line numbers and commit SHAs. Salesforce triggers the flow through the Flows API from a Queueable Apex job, either automatically on exceptions or via a button. The flow is limited to four read tools plus issue creation, requires GitLab Premium or Ultimate with Duo Agent Platform on GitLab 19.5 or later, and leaves the fix decision to an engineer.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://about.gitlab.com/blog/extend-gitlab-duo-agent-platform-into-your-business-systems>

## Questions this post answers

### How can I automatically create a GitLab issue with root-cause analysis when a Salesforce Apex exception occurs?

Call the GitLab Duo Agent Platform Flows API from a Salesforce Queueable job that runs in your exception handler, passing the error details as the flow's goal. A custom flow (one YAML file using tools like find_files, grep, read_file, and list_commits) investigates the code and creates a GitLab issue citing file paths, line numbers and commit SHAs as the likely cause.

_Developers wiring Salesforce errors into GitLab track implementation patterns like this one on daily.dev._

### What GitLab plan and version do I need to use custom flows with the Duo Agent Platform Flows API?

You need GitLab Premium or Ultimate, either on GitLab.com or self-managed GitLab 19.5 or later, since the Flows API reached general availability in 19.5. You also need Duo Agent Platform turned on with custom flows allowed for your top-level group, plus a Maintainer or Owner role in the target project.

_Teams planning a GitLab Duo rollout can compare version and plan requirements on daily.dev._

### How do I restrict a GitLab Duo Agent Platform flow so it can only read code and create issues, not modify anything?

Set agent_privileges and pre_approved_agent_privileges to only include reading files (1), reading GitLab (2), and writing to GitLab (3) in the Flows API request body, and build the flow's toolset with only find_files, grep, read_file, list_commits, and create_issue. This lets the agent investigate and open an issue but never run commands, use Git, or push code changes.

_Engineers scoping AI agent permissions follow guardrail guidance like this on daily.dev._

## Similar posts on daily.dev

- [Introduction to GitLab Duo Agent Platform](https://daily.dev/posts/introduction-to-gitlab-duo-agent-platform-qxdfmwj3o) · GitLab · 0 upvotes · 0 comments
- [Get started with GitLab Duo Agent Platform: The complete guide](https://daily.dev/posts/get-started-with-gitlab-duo-agent-platform-the-complete-guide-ojlwlc2zf) · GitLab · 0 upvotes · 0 comments
- [Understanding flows: Multi-agent workflows](https://daily.dev/posts/understanding-flows-multi-agent-workflows-k6qjnmpbi) · GitLab · 1 upvotes · 0 comments
- [GitLab 19.0 targets the gap between writing code and shipping it](https://daily.dev/posts/gitlab-19-0-targets-the-gap-between-writing-code-and-shipping-it-jmuidkvw4) · The Next Web · 2 upvotes · 0 comments

---

Tags: [#ai-agents](https://daily.dev/tags/ai-agents), [#cicd](https://daily.dev/tags/cicd), [#gitlab](https://daily.dev/tags/gitlab), [#salesforce](https://daily.dev/tags/salesforce)

[View this post on daily.dev](https://daily.dev/posts/extend-gitlab-duo-agent-platform-into-your-business-systems-xftgu5ud1)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"Extend GitLab Duo Agent Platform into your business systems","url":"https://daily.dev/posts/extend-gitlab-duo-agent-platform-into-your-business-systems-xftgu5ud1","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/extend-gitlab-duo-agent-platform-into-your-business-systems-xftgu5ud1"},"datePublished":"2026-10-27T14:00:17.907Z","dateModified":"2026-10-27T14:02:46.583Z","description":"This tutorial shows how to connect Salesforce errors to GitLab Duo Agent Platform so they turn into GitLab issues with root-cause analysis. A custom GitLab...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/0ecb823f07e9cdf81c3de163d3cd68f5?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/0ecb823f07e9cdf81c3de163d3cd68f5?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"GitLab","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"GitLab","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/3720ce340ca4435daef529abbf361b69","url":"https://daily.dev/sources/gitlab"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/extend-gitlab-duo-agent-platform-into-your-business-systems-xftgu5ud1","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"ai-agents,cicd,gitlab,salesforce","timeRequired":"PT12M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"GitLab","item":"https://daily.dev/sources/gitlab"},{"@type":"ListItem","position":3,"name":"Extend GitLab Duo Agent Platform into your business systems"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/extend-gitlab-duo-agent-platform-into-your-business-systems-xftgu5ud1#faq","mainEntity":[{"@type":"Question","name":"How can I automatically create a GitLab issue with root-cause analysis when a Salesforce Apex exception occurs?","acceptedAnswer":{"@type":"Answer","text":"Call the GitLab Duo Agent Platform Flows API from a Salesforce Queueable job that runs in your exception handler, passing the error details as the flow's goal. A custom flow (one YAML file using tools like find_files, grep, read_file, and list_commits) investigates the code and creates a GitLab issue citing file paths, line numbers and commit SHAs as the likely cause. Developers wiring Salesforce errors into GitLab track implementation patterns like this one on daily.dev."}},{"@type":"Question","name":"What GitLab plan and version do I need to use custom flows with the Duo Agent Platform Flows API?","acceptedAnswer":{"@type":"Answer","text":"You need GitLab Premium or Ultimate, either on GitLab.com or self-managed GitLab 19.5 or later, since the Flows API reached general availability in 19.5. You also need Duo Agent Platform turned on with custom flows allowed for your top-level group, plus a Maintainer or Owner role in the target project. Teams planning a GitLab Duo rollout can compare version and plan requirements on daily.dev."}},{"@type":"Question","name":"How do I restrict a GitLab Duo Agent Platform flow so it can only read code and create issues, not modify anything?","acceptedAnswer":{"@type":"Answer","text":"Set agent_privileges and pre_approved_agent_privileges to only include reading files (1), reading GitLab (2), and writing to GitLab (3) in the Flows API request body, and build the flow's toolset with only find_files, grep, read_file, list_commits, and create_issue. This lets the agent investigate and open an issue but never run commands, use Git, or push code changes. Engineers scoping AI agent permissions follow guardrail guidance like this on daily.dev."}}]}
```