Can Cloudinary and PDFMonkey talk in both directions?

Yes. Build one flow that starts in Cloudinary and acts in PDFMonkey, 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 Cloudinary to PDFMonkey

Move data between Cloudinary and PDFMonkey 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 Cloudinary Explore PDFMonkey

Cloudinary triggers: 2
Cloudinary actions: 6
PDFMonkey triggers: 1
PDFMonkey actions: 10

Automation ideas

What you can build with Cloudinary and PDFMonkey

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

New Resource in Cloudinary creates Generate Document in PDFMonkey
Triggers when a new image, video, or file is uploaded to a specific folder or account in Cloudinary.
Document Generated in PDFMonkey creates Upload Resource in Cloudinary
Triggers when a document generation completes successfully.
New Resource in Cloudinary creates Find Document in PDFMonkey
Triggers when a new image, video, or file is uploaded to a specific folder or account in Cloudinary.
Document Generated in PDFMonkey creates Delete Resource in Cloudinary
Triggers when a document generation completes successfully.
New Resource in Cloudinary creates List Documents in PDFMonkey
Triggers when a new image, video, or file is uploaded to a specific folder or account in Cloudinary.
Document Generated in PDFMonkey creates Create Usage Report in Cloudinary
Triggers when a document generation completes successfully.