@Ian_Muyrong - Found the original thread, so I thought I’d reply here :slightly_smiling_face:
You don’t actually need a Google Doc in the process here at all. The easiest way would be to pass data from Airtable straight into your esignature app. DocuSign, however, is not the wisest choice, since it does not allow you to easily pass variables (name, email addresses, phone numbers, etc) from Airtable. It could be doable with the “Make an API Call” module but that is a more advanced process to work through.
So I guess the question is how “married” you are to DocuSign. I know that PandaDoc is much friendlier in this aspect. A while ago, we created a post on passing info from Typeform to PadaDoc and generating docs to be signed. So you can totally check it out for inspiration. There’s also a pre-made template for this use case :slightly_smiling_face:
@Ian_Muyrong - Found the original thread, so I thought I’d reply here :slightly_smiling_face:
You don’t actually need a Google Doc in the process here at all. The easiest way would be to pass data from Airtable straight into your esignature app. DocuSign, however, is not the wisest choice, since it does not allow you to easily pass variables (name, email addresses, phone numbers, etc) from Airtable. It could be doable with the “Make an API Call” module but that is a more advanced process to work through.
So I guess the question is how “married” you are to DocuSign. I know that PandaDoc is much friendlier in this aspect. A while ago, we created a post on passing info from Typeform to PadaDoc and generating docs to be signed. So you can totally check it out for inspiration. There’s also a pre-made template for this use case :slightly_smiling_face:
Hi Michaela! Thanks for this. Our company is really happy with DocuSign and we’d like to stick by it as much as we can. That being said, I’m open to checking other signing platforms that will enable us to make our workflow more efficient.
To update you, I was actually able to make use of the ‘send document to sign’ module of docusign in integromat. It enabled me to pass on a document made with google docs then passed on details of signatory from airtable. One deal breaker is that it can’t configure signing order and envelope expiration. A work around I’m doing right now is to make it as a draft as a default instead of sending it to the signers right away. I know this will require a manual step for us to edit the draft to enable signing order and envelope expiration but this is definitely better than our current workflow.
By the way, I have no experience in coding/scripts so making an API call is something I’m not familiar with. However I already asked from our IT team if they can help me on this extra step :slightly_smiling_face:
Hi Ian!
I recently created a YouTube video walking people through how to send and request signatures for documents inside of DocuSign. You can view it here.
I personally did not find a lot of documentation around how to use DocuSign inside of Make.com, which is why I created the video. Had I had someone show me beforehand, it would have saved me hours of trial and error.
Nice work getting that workflow partly automated, @Ian_Muyrong
that’s already a big step forward. The limitation you’re running into with signing order and envelope expiration is indeed one of the trickier parts of DocuSign’s module in Integromat/Make.
It exposes only a subset of the DocuSign API fields, so fine-tuning envelope behavior typically requires that extra “Make an API Call” module Michaela mentioned.
If your IT team can help you with that, it’ll unlock those advanced parameters; otherwise, you might consider a hybrid approach, keep Integromat as your orchestrator but handle the DocuSign call via a small webhook or script that hits the API directly (DocuSign’s Envelope API reference explains the payload options).
Once you’ve tested that path, you could even loop results back into Airtable for tracking signer status in real time.