Digital signature best practice


I’m looking for experiences and advice on best practice for automating document generation and digital signing using Make to manage the process.

The scenario is an eForm (e.g. Jotform) would take all the variale data required. This would be passed to document generation (I use Docupilot, Pandadoc and others) to generate the document, then I want to pass it for digital signature.

An example would be a simple NDA. New contact fills out the form, Docupilot generates the NDA but I then struggle with the signing stage.

It seems to me that I have to go the API route with the digital signature solutiona nd I’ve looked at a few. That’s OK and I am prepared too but is more expensive than using the regular licenses for a doc signature solution. I don’t believe I can use a template without doing the automation in the document generation or digital signature stages. I want the control of Make controlling it.

Am I missing something here? Overthnking it perhaps?

I’m open to any tools to achieve this. Any experiences or advice would be most welcome


Hi @mdb213,

Generally, the costs of these platforms are relative high if you want to incorporate API. I can recommend Dropbox Sign and Docusign:

If you really want to compare, you can check the Apps in the E-signatures directory:

Hope this helps,


Thanks Henk. I appreciate you taking the time to reply. I have done all those comparisons, The problem is without API it doesn’t seem possible to use Make and needs manual interventions in document writing.

We create 60-100 contracts per month, all from a set template but variable data best completed in a form

I’ll keep trying but seems a big gap for someone to fill