Can ConnectUC and SimplyPrint talk in both directions?

Yes. Build one flow that starts in ConnectUC 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 ConnectUC to SimplyPrint

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

ConnectUC triggers: 8
ConnectUC actions: 6
SimplyPrint triggers: 62
SimplyPrint actions: 63

Automation ideas

What you can build with ConnectUC and SimplyPrint

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

New Recording in ConnectUC creates List Printers in SimplyPrint
Triggers when a new call recording is available
Print Started in SimplyPrint creates Create Contact in ConnectUC
Fires when a print job starts on any printer.
New Recording in ConnectUC creates Get Farm Overview in SimplyPrint
Triggers when a new call recording is available
Print Started in SimplyPrint creates Set Do Not Disturb in ConnectUC
Fires when a print job starts on any printer.
New Recording in ConnectUC creates Get Printer in SimplyPrint
Triggers when a new call recording is available
Print Started in SimplyPrint creates Find CDR in ConnectUC
Fires when a print job starts on any printer.