Skip to content
GitLab logoJumpCloud logo

Connect GitLab to JumpCloud

Move data between GitLab and JumpCloud 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
JumpCloud triggers
1
JumpCloud actions
16

Automation ideas

What you can build with GitLab and JumpCloud

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

  • New Project Issue Event in GitLab creates Create Object in JumpCloud

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

  • New Object in JumpCloud creates Create Issue in GitLab

    Triggers when a new user, device, group or application appears in JumpCloud.

  • New Project Issue Event in GitLab creates Update Object in JumpCloud

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

  • New Object in JumpCloud creates Custom API Call in GitLab

    Triggers when a new user, device, group or application appears in JumpCloud.

  • New Project Issue Event in GitLab creates Delete Object in JumpCloud

    Triggers on project issue events (including confidential issues) 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 JumpCloud, 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.