Can iLoveAPI and PDF.co talk in both directions?

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

Move data between iLoveAPI and PDF.co 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 iLoveAPI Explore PDF.co

iLoveAPI triggers: 11
iLoveAPI actions: 22
PDF.co triggers: 0
PDF.co actions: 34

Automation ideas

What you can build with iLoveAPI and PDF.co

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

Task Completed in iLoveAPI creates Add Barcode to PDF in PDF.co
Fires when a processing task finishes successfully. Optionally filter by tool.
Task Completed in iLoveAPI creates Add Image to PDF in PDF.co
Fires when a processing task finishes successfully. Optionally filter by tool.
Task Completed in iLoveAPI creates Add Text to PDF in PDF.co
Fires when a processing task finishes successfully. Optionally filter by tool.
Task Failed in iLoveAPI creates Add Barcode to PDF in PDF.co
Fires when a processing task fails. Optionally filter by tool.