Can TidyCal and SimplyPrint talk in both directions?

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

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

TidyCal triggers: 3
TidyCal actions: 1
SimplyPrint triggers: 62
SimplyPrint actions: 63

Automation ideas

What you can build with TidyCal and SimplyPrint

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

Booking Canceled in TidyCal creates List Printers in SimplyPrint
Triggers when a new booking is canceled
Print Started in SimplyPrint creates Custom API Call in TidyCal
Fires when a print job starts on any printer.
Booking Canceled in TidyCal creates Get Farm Overview in SimplyPrint
Triggers when a new booking is canceled
Print Paused in SimplyPrint creates Custom API Call in TidyCal
Fires when a print is paused (manually or by the AI failure watcher).
Booking Canceled in TidyCal creates Get Printer in SimplyPrint
Triggers when a new booking is canceled
Print Resumed in SimplyPrint creates Custom API Call in TidyCal
Fires when a paused print is resumed.