Skip to content
CloudConvert logoGitHub logo

Connect CloudConvert to GitHub

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

CloudConvert triggers
3
CloudConvert actions
7
GitHub triggers
14
GitHub actions
19

Automation ideas

What you can build with CloudConvert and GitHub

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

  • New Job Event in CloudConvert creates Create Issue in GitHub

    Triggers when a new job has been created

  • New Pull Request in GitHub creates Convert File in CloudConvert

    Triggers when there is activity on a pull request.

  • New Job Event in CloudConvert creates Get issue information in GitHub

    Triggers when a new job has been created

  • New Pull Request in GitHub creates Capture Website in CloudConvert

    Triggers when there is activity on a pull request.

  • New Job Event in CloudConvert creates Create comment on a issue in GitHub

    Triggers when a new job has been created

  • New Pull Request in GitHub creates Merge Files to PDF in CloudConvert

    Triggers when there is activity on a pull request.

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 CloudConvert and acts in GitHub, 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.