Dynamic Document Creation with E-Signature Capability?

I use a combination of Google docs, Zapier and Airtable for this.

The signing part is a nightmare - There are no good apps out there. I went with Eversign, but I wouldn’t recommend it. Docusign is prohibitively expensive If I had to do it again, I think I would explore PDF filler.

Thanks Andy! Seriously, it feels like nothing out there is a perfect solution. PDFFiller is great; they’re reasonably priced and I’m 99% sure they provide everything that I described above… but alas, the clunkiness of their system rendered my client uninterested :smiling_face_with_halo:

If I exhaust all other options (and it feels like I’m close to doing so), I think I’ll suggest PDFFiller again.

Hope you’re well!

We recently launched an integration for eSignatures.io. Not sure if it checks off all the requirement that you’ve mentioned above, but I think it’s worth checking out.

I checked out eSignatures.io and they offer up a pretty basic form designer that you are limited to. You need to use their editor and you can’t jazz up your form with embedded graphics or anything fancy like that. If all you need is a very straightforward signature doc it’s seem to work smoothly, but you are also paying on a per document sent basis $0.49 per doc.

Hey @AlliAlosa,

The discussion is outdated, but in case you are still looking for a solution, Plumsail Documents might be a good fit. It seems to perfectly match your requirements. You can create a Microsoft Word template that will be dynamically populated with Airtable data. The integration is also based around Zapier.

Here’s an article you might want to check out:
How to auto generate contracts from Airtable data in Zapier — Plumsail Documents

Fortunately, the solution offers a free one-month trial, so you can try it for yourself. Hope this helps!

Hi! If you're looking for a step-by-step guide on integrating DocuSign with Airtable, this article might be helpful: How to set up docusign airtable integration. It breaks down the process into manageable steps, making it easier to follow along. Hope this helps!

2026 Update:

This can now be natively done in Fillout's advanced forms for Airtable. which is an advanced form platform for Airtable. They now support eSignatures & custom PDF files that are automatically created after the signature is received.

I give a demonstration of how to accomplish this on this Airtable podcast episode:
Using Fillout to create an eSignature approval process with PDF file creation.

Fillout also offers hundreds of other advanced features for Airtable, such as the ability to update existing Airtable records with a form.

Other options: 

Even though you have very unique requirements, all of this is extremely easy to accomplish using Make’s advanced automations for Airtable. And you can optionally choose to use DocsAutomator as well.

These are the 2 very simple steps you would take:

1. You would start by automatically creating your editable document from Airtable by using Make’s Microsoft Word modules or Make’s Google Docs modules.
   
   Alternatively, instead of using Make, you could use DocsAutomator, which also creates editable Google Docs documents.
   
   (I normally also recommend using DocuMint for creating documents from Airtable, but that won’t work for you because it only creates uneditable PDF files.)
    
2. After you have finished reviewing & editing your document, you would then use Make to automatically upload your document & send it for eSignature to the e-signature app of your choice.
   
   Currently, Make natively supports 48 different e-signature platforms (and Make natively communicates with over 3,000 different apps), but you can additionally communicate with any e-signature app that has an API by using Make’s HTTP modules.

If you’ve never used Make before, I’ve assembled a bunch of Make training resources in this thread. For example, here is one of the ways that you could instantly trigger a Make automation from Airtable.

I also give live demonstrations of how to use Make in many of my Airtable podcast appearances. For example, in this video, I show how to work with Airtable arrays in Make.

Hope this helps!

If you have a budget and you’d like to hire the best Airtable consultant to help you with this or anything else that is Airtable-related, please feel free to contact me through my website: Airtable consultant — ScottWorld

This thread is old but the requirement is specific enough that it's worth a fresh answer.

The three requirements (pre-filled editable doc, get signing URL before sending, trigger on completion) rule out most simple solutions.

eSignatures.io supports retrieving signing URLs via API, and you can connect it to Airtable via Make. It's one of the cheaper options but requires some API work to get the URL stored back in Airtable before sending.

DocuSign also gives you signing URLs programmatically, but the setup with Airtable goes through Make and is more complex.

TypeFlow has a "Link only" delivery mode where it saves each signer's unique URL to an Airtable field before sending - which matches requirement #2 exactly. Completion triggers a webhook and uploads the signed PDF back. No Make needed. TypeFlow also lets you generate the document in Google Docs so you can modify it afterward.

Worth checking what "editable" means in your case - if signers need to edit content (not just fill signature fields), that changes things significantly. Most e-sign tools treat the document as read-only once generated.