Skip to main content
connic

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.
  1. Something happens in the project

    Someone opens an issue or merge request, merges one, or writes a comment.

    merge_requests.open
  2. connic 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-Token
  3. Linked 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.create
  4. The 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.
gitlab-webhook.json
{
  "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.
output.json
{
  "body": "The total is rounded in the cart and again at payment."
}
connector-payload.json
{
  "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.

New issue
Inbound GitLab
issue-triage
Comment on the issue
gitlab-payload.json
{
  "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"
}
output.json
{
  "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.

New merge request
Inbound GitLab
mr-reviewer
Review comment
gitlab-payload.json
{
  "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"
}
output.json
{
  "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.

New comment
Inbound GitLab
codebase-helper
Answer as a comment
gitlab-payload.json
{
  "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"
}
output.json
{
  "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.

Merged
Inbound GitLab
changelog-writer
Changelog comment
gitlab-payload.json
{
  "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"
}
output.json
{
  "body": "Changelog: EUR totals are rounded once, at payment."
}

GitLab FAQ

The address of your GitLab, gitlab.com or your own instance, and an access token with the api scope: a project, group or personal access token. Inbound connectors add a webhook to their project, which GitLab only allows Maintainers, so their token needs that role.

From the token's user. connic ignores events that user causes, so an agent doesn't start itself again. A project or group access token comes with a user of its own, so everyone else's changes start runs.

No. Saving an inbound connector adds a webhook to its project with a secret token connic generates, and deleting the connector removes it. From GitLab 19.0 on, connic also checks the signature of every delivery.

Yes, when the instance is reachable from the internet over HTTPS and runs GitLab 17.4 or later.

Yes, with type: gitlab, the project path, and the name of a GitLab Connection that holds the base URL and the access token.