GitLab

Developer tools OAuth, or a personal access token Windmill docs

Read repositories, manage merge requests and trigger pipelines from any Windmill script, flow or app.

Set up in 2 steps

Connect from the Resources page

Open Resources, click Add a resource/API and pick gitlab from the OAuth APIs list. Click Connect, allow access, then name the resource and save it.

Run your first script

Fork any script below and read a project before writing anything.

Scripts

Building blocks, if none of the projects above fit. Fork one, run it, or call it as a step inside your own flow.

Resource type

gitlab — the shape of the credential every script on this page expects.

View raw schema →

Field	Type	Required	What it is
baseUrl	string	No
token	string	Yes

Questions

OAuth or a personal access token?

OAuth is one click. Reach for a token when you script the setup, when you need a scope the connection does not request, or on a self-managed instance with no OAuth client configured.

I run GitLab myself

Set baseUrl to your instance. It defaults to gitlab.com, and every request is built from it.

Is my token stored on the hub?

Never. It lives only in your own Windmill workspace, encrypted at rest.

Set up in 2 steps

Connect from the Resources page

Run your first script

Scripts

Create Branch

Search Issues

Edit Issue

List Commits

Get Issue

Get release

GitLab: push changes to windmill

List project issues

Create issue

List Repo Branches

Get Repo Branch

Add MR comment (gitlab)

Resource type

Questions