GitLab
Push, MR, pipeline, and issue events from GitLab
GitLab is the self-hostable Git-plus-CI-plus-issues platform a lot of larger orgs run instead of GitHub. Five triggers cover the lifecycle events worth automating: Push Event (any commit to any branch), Tag Pushed (release-triggering), Issue Created, Merge Request (any state change on an MR), Pipeline Completed (the CI run finished, success or fail). Ten actions handle the operational surface: Create Issue, Create Merge Request, Add Comment, Get Issue, Get Project, List Branches, List Issues, List Merge Requests. The integration authorizes via GitLab OAuth or a personal access token, depending on whether you're wiring org-wide or for yourself. Works against GitLab.com and self-hosted GitLab instances (Community Edition, Enterprise Edition), for self-hosted, you provide the instance URL in the connection. Common patterns: a Pipeline Completed with status failed pings the on-call rotation in Slack with the failing job name and log URL, or a Merge Request opened in the main repo auto-creates a paired Linear issue for QA.
Workflows start when GitLab does.
5 real-time triggers, each backed by a webhook subscription. Events arrive within seconds and you don't have to set up polling.
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.
Fires on MR events — opened, updated, closed, merged. The hook for "auto-assign reviewer", "post to review channel", "trigger downstream CI" workflows.
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.
Fires on commit pushes to any branch (or filtered). Payload includes commits with messages and authors. For commit-message-based automation or for custom CI triggers.
Fires when a new tag is pushed. Useful for release-management workflows that fire on version tags (e.g., "v1.2.3 pushed → trigger production deploy").
Do anything GitLab can do, from a workflow.
Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.
| Action | What it does |
|---|---|
| Add GitLab Comment | Posts a comment on an issue, merge request, or commit. For AI-code-review bots or for cross-tool sync ("Linear status changed → comment on the linked MR"). |
| Create GitLab Issue | Files an issue with title, description, labels, assignees, milestone. For "Sentry error → file repo issue" or "support ticket marked bug → create issue" workflows. |
| Create GitLab Merge Request | Opens a new MR from source branch to target branch with title, description, reviewers, labels. For automation that auto-creates MRs from generated branches (dependabot-style). |
| Get GitLab Issue | Returns an issue by ID with all metadata. The standard lookup for cross-system sync workflows that need fresh issue state. |
| Get GitLab Project | Returns project metadata — name, namespace, visibility, default branch, recent activity. Useful for project inventory workflows. |
| List GitLab Branches | Returns the project's branches with last commit info. Useful for "find stale branches for cleanup" maintenance workflows. |
| List GitLab Issues | Paginated issues with filters by state, label, assignee, milestone, date. For "open critical issues" dashboards or per-engineer queue rollups. |
| List GitLab Merge Requests | Paginated MRs with state, target branch, author, reviewer filters. The base query for review-velocity reporting and for "MRs awaiting my review" daily nudges. |
| List GitLab Pipelines | Paginated pipelines with status and ref filters. For "deploy history this week" reports or for CI-health monitoring workflows. |
| List GitLab Projects | Returns paginated projects in the namespace or accessible to the user. Useful for cross-project automation and for project inventory workflows. |
Pre-built GitLab workflows.
Clone any recipe and customize it in one click. Every recipe is fully editable.
Three things worth knowing.
Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.
Connect GitLab once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.
Every GitLab field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.
Questions about the GitLab integration.
If we missed yours, ping support. We usually reply within an hour.
How do I connect GitLab to Tiny Command?
What GitLab triggers does Tiny Command support?
What GitLab actions can I run from a workflow?
Is the GitLab integration real-time?
Do I need to write code to use GitLab with Tiny Command?
How much does the GitLab integration cost?
More developer tools apps people connect.
Same category as GitLab, ordered by how often teams pair them. Hover the carousel to pause.
Do more with GitLab.
Wire it to Slack, Notion, HubSpot, Stripe, or any of the other 438 apps in our catalog. Setup takes roughly two minutes. Free to try, no credit card.
