Use Airtable record data to create documents for signing through eSignatures.io. The miniExtensions eSignatures.io Integration generates a record-specific signing link, stores the contract ID, and can add the completed PDF back to Airtable through the eSignatures.io webhook.
What you can do
- Populate an eSignatures.io template with Airtable values.
- Generate record-specific signing links.
- Return completed PDFs to Airtable through the provider webhook.
Signing links and completed documents
Choose an eSignatures.io template and map the signer’s name, email, and document values from Airtable. The generated formula creates a signing link for each record. Opening the link creates a contract when needed or uses the existing contract associated with that record.
Store the contract ID in a text field and select an attachment field for signed PDFs. Configure the miniExtensions return webhook in eSignatures.io so completed signing events can send the document back to the correct record.
Use Test Mode to check the template, signer information, and PDF return before sending live agreements. This is a provider-backed signing-link workflow rather than an immediate bulk generation of every contract in the table.
A practical example
A consulting team can map a client’s name and email together with the service description, start date, and rate. Share the resulting signing link through the team’s delivery workflow, then retain the returned PDF with the client record.
How to get started
Connect your provider key and template, map signer and document fields, and configure the return webhook. Complete a test signing before sharing live links.
Good to know
An eSignatures.io account and provider charges apply. The return webhook is required to store completed PDFs in Airtable.
