Skip to content
Docusign logoSimplyPrint logo

Connect Docusign to SimplyPrint

Move data between Docusign 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.

Docusign triggers
11
Docusign actions
8
SimplyPrint triggers
62
SimplyPrint actions
63

Automation ideas

What you can build with Docusign and SimplyPrint

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

  • Signing Request Created in Docusign creates List Printers in SimplyPrint

    Triggers when a new signing request (envelope) is created in DocuSign — whether sent immediately or saved as a draft.

  • Print Started in SimplyPrint creates Search Signing Requests in Docusign

    Fires when a print job starts on any printer.

  • Signing Request Created in Docusign creates Get Farm Overview in SimplyPrint

    Triggers when a new signing request (envelope) is created in DocuSign — whether sent immediately or saved as a draft.

  • Print Started in SimplyPrint creates Get Signing Request Details in Docusign

    Fires when a print job starts on any printer.

  • Signing Request Created in Docusign creates Get Printer in SimplyPrint

    Triggers when a new signing request (envelope) is created in DocuSign — whether sent immediately or saved as a draft.

  • Print Started in SimplyPrint creates Download Document from Signing Request in Docusign

    Fires when a print job starts on any printer.

Questions, answered

No. Pick a trigger on either piece and an action on the other, map the fields, and turn the flow on. Add a code step later only if you want to.

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