Can PDFMonkey and iLoveAPI talk in both directions?

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

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

PDFMonkey triggers: 1
PDFMonkey actions: 10
iLoveAPI triggers: 11
iLoveAPI actions: 22

Automation ideas

What you can build with PDFMonkey and iLoveAPI

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

Document Generated in PDFMonkey creates Compress PDF in iLoveAPI
Triggers when a document generation completes successfully.
Task Completed in iLoveAPI creates Generate Document in PDFMonkey
Fires when a processing task finishes successfully. Optionally filter by tool.
Document Generated in PDFMonkey creates Merge PDF in iLoveAPI
Triggers when a document generation completes successfully.
Task Completed in iLoveAPI creates Find Document in PDFMonkey
Fires when a processing task finishes successfully. Optionally filter by tool.
Document Generated in PDFMonkey creates Split PDF in iLoveAPI
Triggers when a document generation completes successfully.
Task Completed in iLoveAPI creates List Documents in PDFMonkey
Fires when a processing task finishes successfully. Optionally filter by tool.