Skip to content
GitLab logoDigitalOcean logo

Connect GitLab to DigitalOcean

Move data between GitLab and DigitalOcean 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
DigitalOcean triggers
0
DigitalOcean actions
11

Automation ideas

What you can build with GitLab and DigitalOcean

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

  • New Project Issue Event in GitLab creates List All Domains in DigitalOcean

    Triggers on project issue events when an issue is created or when an existing issue is updated, closed, or reopened.

  • New Project Issue Event in GitLab creates Create Domain in DigitalOcean

    Triggers on project issue events when an issue is created or when an existing issue is updated, closed, or reopened.

  • New Project Issue Event in GitLab creates Get Domain in DigitalOcean

    Triggers on project issue events when an issue is created or when an existing issue is updated, closed, or reopened.

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 DigitalOcean, 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.