Skip to content
GitLab logoNetlify logo

Connect GitLab to Netlify

Move data between GitLab and Netlify the moment it happens. Build the flow visually, or let AI write it for you, then run it on our cloud or your own infrastructure.

GitLab triggers
1
GitLab actions
2
Netlify triggers
4
Netlify actions
4

Automation ideas

What you can build with GitLab and Netlify

A few flows teams run between GitLab and Netlify. Use one as a starting point, or build your own from scratch.

  • New Project Issue Event in GitLab creates Start Deploy in Netlify

    Triggers on project issue events (including confidential issues) when an issue is created or when an existing issue is updated, closed, or reopened.

  • New Deploy Started in Netlify creates Create Issue in GitLab

    Fires immediately when a deploy job starts on your Netlify site.

  • New Project Issue Event in GitLab creates Get Site in Netlify

    Triggers on project issue events (including confidential issues) when an issue is created or when an existing issue is updated, closed, or reopened.

  • New Deploy Started in Netlify creates Custom API Call in GitLab

    Fires immediately when a deploy job starts on your Netlify site.

  • New Project Issue Event in GitLab creates List Site Deploys in Netlify

    Triggers on project issue events (including confidential issues) when an issue is created or when an existing issue is updated, closed, or reopened.

  • New Deploy Succeeded in Netlify creates Create Issue in GitLab

    Fires when a new site version has successfully deployed.

Questions, answered

No. Pick a trigger on either piece and an action on the other, map the fields, and turn the flow on. Add a code step later only if you want to.

Yes. Build one flow that starts in GitLab and acts in Netlify, and a second that runs the other way, in the same project.

On our EU cloud in Frankfurt, or self-hosted on your own infrastructure with Docker or Kubernetes. The MIT-licensed core means there is always an exit.