Can PolyDoc and SimplyPrint talk in both directions?

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

Move data between PolyDoc and SimplyPrint 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 PolyDoc Explore SimplyPrint

PolyDoc triggers: 0
PolyDoc actions: 4
SimplyPrint triggers: 62
SimplyPrint actions: 63

Automation ideas

What you can build with PolyDoc and SimplyPrint

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

Print Started in SimplyPrint creates Convert to PDF in PolyDoc
Fires when a print job starts on any printer.
Print Started in SimplyPrint creates Capture Screenshot in PolyDoc
Fires when a print job starts on any printer.
Print Started in SimplyPrint creates Generate E-Invoice in PolyDoc
Fires when a print job starts on any printer.
Print Paused in SimplyPrint creates Convert to PDF in PolyDoc
Fires when a print is paused (manually or by the AI failure watcher).