This message was deleted.

I've done it with Airtable, Make and Docusign. There might be easier ways, but: • Tick a box in Stacker labelled something like 'request contract' • This ticks a box in a field in Airtable • An automation on Make looks out for this field to be changed. It runs every 5 mins. The automation links Airtable to Docusign. When it noticed it's changed, it looks up other fields in the record and passed them to Docusign and the contract is issued for signing. It then also send a Slack message to say the contract has been issued.

this is awesome, thanks for sharing @high-tomato-50749! Just curious what functionality does Make offer in this sequence that Zapier couldn't handle?

no idea, I ended up ages ago using make rather than zapier. zapier may or may not be able to do this, not sure!

We use esignatures.io get a contract embed URL we save in Air table and display that as embed/ iframe. Pretty similar automation flows in Make as Andrew mentions. I just prefer the simplicity of the esignatures.io API.

awesome thanks @early-dress-58417! going to check this out. great idea to embed it as well

@hundreds-queen-22353 For us it's the same agreement for everyone with a few variables that change. So we collect the data in Stacker from the user, automate creating the agreement in esignatures by using a template and values for each necessary variable, and store the URL to view/sign in Airtable. Then use that to display as the embed. Esignatures does enable multi-person agreements. You can indicate who most sign first and second. We typically use this when we need our organization to counter sign. So we generate the agreement, have the user sign it, and then we usually automatically sign our side. You can also have it send an email to the second person to sign. If your agreements are substantively different from user to user your process would need to be a little different. Esignatures might not be the best solution if you're not using any sort of template agreement.