src ▸ task opened 0

Automate GitLab

Turn the repetitive GitLab work you do by hand (open a project, read issues and MRs) into a workflow Writ runs for you, on your own account, on a schedule or on demand.

Automate GitLab See how it works
Writ runs on your own accounts, with your own credentials and data, on sites you are authorized to use.
GitLab workflow
  1. 1
    open a project
  2. 2
    read issues and MRs
  3. 3
    export a list
  4. 4
    run a UI-only admin action

✓ Recorded once, then run for you

gap ▸ done by hand 01
01
why

Stop doing GitLab by hand

The GitLab tasks you repeat (open a project, read issues and MRs, export a list) are exactly the kind of work a computer should do. But GitLab only exposes part of it through an API, and the flow runs behind a login and dynamic pages. GitLab has a strong API, but some analytics, group settings, and admin screens are only reachable through the browser UI.

Writ closes that gap. Record the GitLab task once (or describe it to an AI session) and Writ runs it for you in a real browser, on your own account. Writ runs on your own accounts, with your own credentials and data, on sites you are authorized to use.

ops ▸ actions mapped 02
02
automate

GitLab tasks Writ can run for you

Each of these is a real GitLab action, captured into a workflow and run on your own account.

{ }open a project
{ }read issues and MRs
{ }export a list
{ }run a UI-only admin action

Workflows extract structured fields such as project metadata, stars, open issues, MR status along the way: typed data you can route anywhere.

build ▸ three routes 03
03
build

Three ways to build your GitLab automation

Pick whichever fits the task. All three produce the same workflow Writ can run for you.

✦Record itDo the GitLab task once in a real browser (open a project, then read issues and MRs) and the recorder captures every step into a reusable workflow.
✦Describe it to AITell an AI session your goal on GitLab in plain language; it drives the live page and builds the workflow for you, no recording needed.
✦Discover itLet API discovery watch GitLab's own network calls as you browse, then turn the underlying requests into a fast, headless workflow.

Built on the same engine as the recorder and workflows, with 30+ step types.

auth ▸ logged-in web 04
04
the hard web

Login, 2FA, and dynamic pages on GitLab

The reason GitLab is tedious to automate is the same reason most tools can't. Writ handles it.

Writ signs into your own GitLab account through a Persona with 2FA for UI-only actions, or reads public projects with no login.

PersonasTOTP & mailbox OTP AI navigationReal Chromium rendering
when ▸ it runs 05
05
when it runs

Run the GitLab automation on your terms

On a schedule, on demand, or the instant something changes. You choose the trigger.

✦On a scheduleRun the GitLab task every hour, every morning, or any cadence. No one has to remember to do it.
✦On demandTrigger a single run from the dashboard, a webhook, your code, or an AI agent, whenever you need it.
✦On a changeWatch GitLab for new release or new issue matching a label and fire the automation the instant it happens.
  1. 1
    Build the GitLab workflow once

    Record the task, describe it to AI, or discover it from the network. Writ captures each step, including login and 2FA, into a workflow you can edit.

  2. 2
    Run it on your terms

    Run it on demand, on a schedule, or fire it from a Monitor when GitLab changes. It runs on your own GitLab account, in a real browser.

  3. 3
    Call it from anything

    The same workflow is a REST endpoint at /v1/gitlab/run and an MCP tool, so your code, a no-code tool, or an AI agent can trigger the GitLab automation too.

watch ▸ changes tracked 06
06
watch

Trigger the GitLab automation on a change

Monitor GitLab for new release, new issue matching a label, pipeline status change and run your workflow the moment it happens.

Monitors check as fast as every 10s (10s on Enterprise). A detected change becomes a trigger that runs your GitLab automation in seconds. Monitor GitLab ▸

venue ▸ local or cloud 07
07
run it

Free on your own machine, or on cloud

Local / BYO agent

No compute charge. The agent runs on your hardware, so it can reach GitLab even from an intranet or VPN-only network, and your AI keys never leave your machine.

Writ cloud

Metered by running time at $0.12 per browser-hour, drawn from your plan’s included usage. No infrastructure to manage.

call ▸ endpoint too 08
08
callable

The same GitLab automation is an API and an MCP tool

Automating GitLab for yourself and calling it from software are the same workflow. Once you have it, publish it as a REST endpoint at/v1/gitlab/run and a matching MCP tool, so your code or an AI agent can trigger the GitLab task too.

GitLab API GitLab MCP tools
also ▸ same workflow 09
09
other ways

Other ways to work with GitLab

GitLab APICall GitLab as a REST endpoint from your own software.Website to API GitLab MCP toolsExpose GitLab as MCP tools your agent can call.For AI agents Monitor GitLabWatch GitLab and act the instant it changes.Change detection WorkflowsHow recorded workflows run, with login, 2FA, and 30+ step types.Product
faq ▸ questions answered 10
10
faq

Automating GitLab: questions

How do I automate GitLab?
Record the GitLab task once in the recorder (open a project, read issues and MRs, export a list) or describe your goal to an AI session. Writ turns it into a workflow it can run for you on a schedule or on demand, on your own GitLab account. It usually takes minutes, not a backend project.
Is it allowed to automate GitLab this way?
Use Writ on your own GitLab account and on public projects you have the right to access. Respect its Terms of Service. Writ runs on your own accounts, with your own credentials and data, on sites you are authorized to use.
Does GitLab automation work behind login and 2FA?
Writ signs into your own GitLab account through a Persona with 2FA for UI-only actions, or reads public projects with no login. Writ handles TOTP and mailbox-OTP two-factor through Personas, so the automation runs inside your own authenticated GitLab session.
Can I run the GitLab automation without writing code?
Yes. Recording and AI sessions need no code at all. If you do want to trigger it from software, the same workflow is a REST endpoint and an MCP tool, but that is optional.
Where does it run, and what does it cost?
Run it on your own machine with a local or BYO agent for no compute charge, useful when GitLab is only reachable from your network or VPN. Or run it on metered cloud at $0.12 per browser-hour, drawn from your plan’s included usage. Start free.
rec ▸ ready ●

Automate GitLab in minutes

Record it once, then let Writ run it for you: on a schedule, on demand, or on a change. Get started free.

Get started