Can GitLab and CloudConvert talk in both directions?

Yes. Build one flow that starts in GitLab and acts in CloudConvert, 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.

Connect GitLab to CloudConvert

Move data between GitLab and CloudConvert 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.

Start building Explore GitLab Explore CloudConvert

GitLab triggers: 1
GitLab actions: 2
CloudConvert triggers: 3
CloudConvert actions: 7

Automation ideas

What you can build with GitLab and CloudConvert

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

New Project Issue Event in GitLab creates Convert File in CloudConvert
Triggers on project issue events when an issue is created or when an existing issue is updated, closed, or reopened.
New Job Event in CloudConvert creates Create Issue in GitLab
Triggers when a new job has been created
New Project Issue Event in GitLab creates Capture Website in CloudConvert
Triggers on project issue events when an issue is created or when an existing issue is updated, closed, or reopened.
New Job Event in CloudConvert creates Custom API Call in GitLab
Triggers when a new job has been created
New Project Issue Event in GitLab creates Merge Files to PDF in CloudConvert
Triggers on project issue events when an issue is created or when an existing issue is updated, closed, or reopened.
Job Finished in CloudConvert creates Create Issue in GitLab
Triggers when a CloudConvert job has been completed