Start free
Per-pair page

Connect GitLab to Slack in two minutes.

Real-time triggers from GitLab, ready-made actions in Slack. Filter, transform, and route without writing a line of code.

Connect GitLab and SlackSee reverse direction
Trigger app
GitLab as the trigger

Workflows fire when something happens in GitLab.

Action app
Slack as the action

Workflows do something in Slack, instantly.

See all 45 actions →
Both directions

Pick the way that fits your stack.

Pair pages are mirrored. Each direction gets its own dedicated page.

GitLab → Slack

When something happens in GitLab, do it in Slack.

5 GitLab triggers wired to 45 Slack actions. Most-used pairing: GitLab Issue Created → Add Reaction.

Slack → GitLab

Or fire it the other way around.

13 Slack triggers wired to 10 GitLab actions downstream.

See Slack → GitLab →
Popular pairings

Common GitLab → Slack workflows.

Pick a pairing to set it up in two minutes. Each one is a fully editable recipe.

Showing 9 of 225 combinations
When gitlab issue created in GitLab, add reaction in Slack.

Fires when a new issue is created in a GitLab project. Payload includes title, description, labels, assignees. Useful for "auto-route to team channel based on labels" or "create cross-tracker copy" sync workflows.

When gitlab issue created in GitLab, raw api request in Slack.

Fires when a new issue is created in a GitLab project. Payload includes title, description, labels, assignees. Useful for "auto-route to team channel based on labels" or "create cross-tracker copy" sync workflows.

When gitlab issue created in GitLab, archive channel in Slack.

Fires when a new issue is created in a GitLab project. Payload includes title, description, labels, assignees. Useful for "auto-route to team channel based on labels" or "create cross-tracker copy" sync workflows.

When gitlab issue created in GitLab, cancel scheduled message in Slack.

Fires when a new issue is created in a GitLab project. Payload includes title, description, labels, assignees. Useful for "auto-route to team channel based on labels" or "create cross-tracker copy" sync workflows.

When gitlab merge request in GitLab, add reaction in Slack.

Fires on MR events — opened, updated, closed, merged. The hook for "auto-assign reviewer", "post to review channel", "trigger downstream CI" workflows.

When gitlab merge request in GitLab, raw api request in Slack.

Fires on MR events — opened, updated, closed, merged. The hook for "auto-assign reviewer", "post to review channel", "trigger downstream CI" workflows.

When gitlab merge request in GitLab, archive channel in Slack.

Fires on MR events — opened, updated, closed, merged. The hook for "auto-assign reviewer", "post to review channel", "trigger downstream CI" workflows.

When gitlab merge request in GitLab, cancel scheduled message in Slack.

Fires on MR events — opened, updated, closed, merged. The hook for "auto-assign reviewer", "post to review channel", "trigger downstream CI" workflows.

When gitlab pipeline completed in GitLab, add reaction in Slack.

Fires when a CI/CD pipeline completes with final status (passed, failed, canceled). For "post deploy result to engineering Slack" or "alert on consecutive failures" workflows.

How it works

Connect GitLab and Slack in five steps.

No code, no glue, no half-day setup. Each step is one click.

  1. 1
    Connect
    Authorize GitLab and Slack

    Open Tiny Command, authorize GitLab and Slack once each. Both connections are available to every workflow on your account.

  2. 2
    Trigger
    Pick a GitLab trigger

    Drop the GitLab → GitLab Issue Created trigger onto the canvas. Tiny Command auto-registers the webhook.

    POST /v1/webhooks/gitlab.trigger-issue-created
  3. 3
    Transform
    Add a filter or AI step

    Optionally add a Filter node ("subject contains URGENT") or an AI step ("classify intent") between trigger and action.

  4. 4
    Action
    Add the Slack action

    Drop the Slack → Add Reaction action below it. Map fields from the GitLab payload into the Slack inputs.

    slack.add-reaction
  5. 5
    Publish
    Publish and forget

    Hit Publish. Tiny Command runs it in production from second one. Watch the run-log fill up.

FAQ

Questions about GitLab + Slack.

How long does it take to connect GitLab and Slack on Tiny Command?
Under two minutes. Authorize GitLab and Slack once each, drop the GitLab trigger and Slack action onto a workflow canvas, map a couple of fields, and publish. No code, no glue.
Is the GitLab ↔ Slack integration real-time?
Yes. Both GitLab and Slack expose webhooks, so events from one fire workflows in the other within seconds rather than on a polling interval.
Can I filter or transform data between GitLab and Slack?
Yes. Add a Filter node to only pass through matching events, a Switch node to branch by value, or an AI / Code node to transform payloads before they hit Slack.
What GitLab events can trigger a Slack workflow?
Any of the 5 GitLab triggers, including "GitLab Issue Created". Each fires in real time when the matching event happens in GitLab.
Do I need a paid plan to use GitLab with Slack?
No. There's a free tier that covers most GitLab+Slack use cases without a credit card. Paid plans unlock higher run volumes and team features when you outgrow it.
What if I want Slack → GitLab instead?
Build it the same way, in reverse. There's a dedicated /integrations/slack/with/gitlab page with the reverse-direction triggers and actions.
Related

Other apps that pair well with GitLab.

+
GitLab + Gmail
Email
+
GitLab + Google Sheets
Spreadsheets & Databases
+
GitLab + HubSpot
CRM & Sales
+
GitLab + Stripe
Payments
+
GitLab + Notion
Productivity
+
GitLab + Airtable
Spreadsheets & Databases

Wire GitLab to Slack in 2 minutes.

Free tier available. No credit card. No onboarding call.

Try for freeRequest a demo