GitLab
Run connic agents on issues, merge requests and comments in your GitLab projects. Agents reply with a comment where the event happened.
- Modes
- Inbound, Outbound
- Set up in
- Dashboard or connectors/*.yaml
- Documentation
- GitLab docs
- Publisher
- By connic
Answer issues, merge requests and comments
When an event in the project matches an inbound connector's events, every agent linked to it starts. An outbound connector on the same Connection posts the result as a comment.
- Pick events and actions
- merge_requests reacts to every change of a merge request, merge_requests.merge only to merges. The same works for issues and comments.
- Several connectors per project
- Each connector has its own webhook, so you can watch merge requests with one and issues with another, or use one per environment.
- No loops, no double runs
- Changes by the token's user are ignored, and an event that GitLab delivers again doesn't start a second run.
Something happens in the project
Someone opens an issue or merge request, merges one, or writes a comment.
merge_requests.openconnic checks and confirms the event
It checks the webhook's secret token, and its signature from GitLab 19.0 on, then answers GitLab right away.
X-Gitlab-TokenLinked agents start
The run gets the event and action, the issue or merge request with its title, the text in Markdown, a link and who caused it.
notes.createThe answer lands as a comment
An outbound connector on the same Connection comments on the issue or merge request that started the run.
One token, the webhook is added for you
You paste an access token once. Saving an inbound connector adds a webhook to its project in GitLab, and deleting the connector removes it.
- gitlab.com or your own instance
- Keep the default base URL for gitlab.com, or enter your self-managed GitLab. It must be reachable from the internet.
- One project per connector
- Enter the project by its path, like acme/shop. connic keeps its ID, so renaming the project doesn't break the connector.
- Nothing to copy back
- connic generates the webhook's secret token and signing token and checks every delivery with them. You find the webhook in the project's webhook settings.
{
"url": "https://connect.connic.co/gitlab/<connector-id>",
"issues_events": true,
"merge_requests_events": true,
"note_events": true,
"push_events": false,
"token": "<generated by connic>",
"signing_token": "<generated by connic>"
}Reply where the event happened
An outbound GitLab connector posts the agent's output as a comment on the issue or merge request that started the run.
- Replies only
- The comment goes to the issue or merge request the run came from, through an inbound connector on the same Connection.
- Three ways to send
- Send after every completed run, give the model a tool to call, or call send_connector from middleware when your code decides.
- Rate limits handled
- When GitLab rate-limits a comment, connic waits and sends it again.
{
"body": "The total is rounded in the cart and again at payment."
}{
"body": "Reproduced on main: the total is rounded twice."
}Where GitLab fits
Pick a setup to see what reaches the agent and what it posts back to GitLab.
Someone opens an issue, and the agent asks for missing details and names the likely area.
{
"event": "issues",
"action": "open",
"project": "acme/shop",
"type": "issue",
"iid": 418,
"title": "Refund button does nothing",
"text": "Clicking Refund on an order shows no error and no refund.",
"url": "https://gitlab.com/acme/shop/-/issues/418",
"author": "jane"
}{
"body": "Likely the refunds service. Which order ID and browser?"
}Someone opens a merge request, and the agent comments on what it changes and what it misses.
{
"event": "merge_requests",
"action": "open",
"project": "acme/shop",
"type": "merge_request",
"iid": 97,
"title": "Round EUR totals once",
"text": "Drops the rounding in the cart service.",
"url": "https://gitlab.com/acme/shop/-/merge_requests/97",
"author": "jane"
}{
"body": "Looks right. The invoice service still rounds on its own."
}Someone asks a question in a comment, and the agent answers on the same merge request.
{
"event": "notes",
"action": "create",
"project": "acme/shop",
"type": "merge_request",
"iid": 97,
"title": "Round EUR totals once",
"text": "Which services still round on their own?",
"url": "https://gitlab.com/acme/shop/-/merge_requests/97#note_5521",
"author": "jane"
}{
"body": "The cart and invoice services. Both call round() before payment."
}A merge request is merged, and the agent writes the changelog entry for it.
{
"event": "merge_requests",
"action": "merge",
"project": "acme/shop",
"type": "merge_request",
"iid": 97,
"title": "Round EUR totals once",
"text": "Drops the rounding in the cart service.",
"url": "https://gitlab.com/acme/shop/-/merge_requests/97",
"author": "jane"
}{
"body": "Changelog: EUR totals are rounded once, at payment."
}GitLab FAQ
More connectors
Apache Kafka
Consume topics to trigger agents and produce results back to topics under the source message key.
Inbound · Outbound
Email (SMTP/IMAP)
Read an inbox to trigger an agent. Reply with a drafted message over SMTP. Attachments included.
Inbound · Outbound
Linear
Run an agent on new and updated issues and comments in a Linear team. It replies in the comment thread or creates a new issue.
Inbound · Outbound
Telegram
Power a Telegram bot with an agent. Read user messages, reply in the chat, push alerts to any channel.
Inbound · Outbound
Telnyx Messaging
Receive and send SMS/MMS, WhatsApp, and RCS messages through your Telnyx account. Connect agents to customer conversations and notifications.
Inbound · Outbound
WhatsApp
Answer WhatsApp messages to your business number with an agent, files included. Reply within 24 hours or reach people with approved templates.
Inbound · Outbound