Can SendPulse and SimplyPrint talk in both directions?

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

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

SendPulse triggers: 3
SendPulse actions: 6
SimplyPrint triggers: 62
SimplyPrint actions: 63

Automation ideas

What you can build with SendPulse and SimplyPrint

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

New Subscriber in SendPulse creates List Printers in SimplyPrint
Fires when new subscriber is added
Print Started in SimplyPrint creates Add Subscriber in SendPulse
Fires when a print job starts on any printer.
New Subscriber in SendPulse creates Get Farm Overview in SimplyPrint
Fires when new subscriber is added
Print Started in SimplyPrint creates Change Variable for Subscriber in SendPulse
Fires when a print job starts on any printer.
New Subscriber in SendPulse creates Get Printer in SimplyPrint
Fires when new subscriber is added
Print Started in SimplyPrint creates Delete Contact in SendPulse
Fires when a print job starts on any printer.