AI agents with GitLab webhooks

Receive GitLab webhooks on Trigger.dev and use them to start, resume or message your AI agents.

Get started now

What you can do with GitLab webhooks

Start an agent

GitLab events can start a new agent run. For example, an agent that reviews every GitLab merge request.

Resume an agent

An agent can pause until the GitLab event it needs arrives, for up to 90 days, and costs nothing while it waits.

Message an agent

GitLab events can land in a running agent's conversation, so it acts on them with full context.

Events you can receive from GitLab

Some of the events GitLab sends. Your agent can filter on any of them.

View all events
Confidential Issue Hook
Issue Hook
Note Hook
Push Hook
Release Hook
Tag Push Hook
Wiki Page Hook
Merge Request Hook

Merge request event, e.g. opened

Pipeline Hook

Pipeline event, e.g. succeeded

Job Hook

CI/CD job changed state

Example

An agent that reviews every GitLab merge request

import { webhook, webhooks } from "@trigger.dev/sdk";


export const gitlab = webhooks.endpoint.define({
  id: "gitlab",
  source: webhooks.gitlab(),
});


export const gitlabEvents = webhook({
  id: "gitlab-events",
  endpoint: gitlab,
  onEvent: async ({ event }) => {
    // Start, resume or message your agent with the event
    console.log(event);
  },
});

Handled for you

Docs

Verified for you

webhooks.gitlab() checks the GitLab signature on every request. Bad requests are rejected before anything runs.

Filter before anything runs

Only the GitLab events you care about start a run. Filtered webhooks use no compute.

See every delivery

Every webhook is recorded with its payload, headers and the agents it reached, so you can debug it and replay it.

Get started

  1. 1

    Set up the agent

    Copy the starter prompt into your coding agent, like Claude Code, Cursor or Codex. It creates a Trigger.dev project and adds the webhook endpoint. Prefer to write it yourself? Start from the example above.

  2. 2

    Add the webhook in GitLab

    Deploy your project, or run trigger dev, and the endpoint appears on the Webhooks page of the Trigger.dev dashboard with its URL. Add that URL in GitLab's webhook settings and pick the events you need. The endpoint's Copy setup prompt button gives your coding agent the exact steps.

  3. 3

    Add a signing secret

    On the endpoint's page in the Trigger.dev dashboard, choose Generate secret. Then paste it into GitLab's webhook settings, so Trigger.dev can check every request really came from GitLab.

  4. 4

    Try it

    Send a test event from GitLab, or use the endpoint's Test tab. It appears on the endpoint's Deliveries tab, with the agents it reached.

Related integrations

All 48 integrations

Firecrawl

Developer tools

GitHub

Developer tools

Linear

Productivity

Slack

Communication

Attio

Productivity

Autumn

Payments & billing

Brex

Payments & billing

Cal.com

Productivity

Ready to build with GitLab webhooks?

Declare an endpoint, deploy, and paste the URL into your provider.

Get started for free