Skip to content
PagerDuty logoCloudConvert logo

Connect PagerDuty to CloudConvert

Move data between PagerDuty 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.

PagerDuty triggers
3
PagerDuty actions
6
CloudConvert triggers
3
CloudConvert actions
7

Automation ideas

What you can build with PagerDuty and CloudConvert

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

  • New Incident in PagerDuty creates Convert File in CloudConvert

    Triggers when a new incident is created

  • New Job Event in CloudConvert creates Create Incident in PagerDuty

    Triggers when a new job has been created

  • New Incident in PagerDuty creates Capture Website in CloudConvert

    Triggers when a new incident is created

  • New Job Event in CloudConvert creates List Incidents in PagerDuty

    Triggers when a new job has been created

  • New Incident in PagerDuty creates Merge Files to PDF in CloudConvert

    Triggers when a new incident is created

  • New Job Event in CloudConvert creates Get Incident in PagerDuty

    Triggers when a new job has been created

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 PagerDuty 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.