Signed contracts as Airtable records
Airtable can catch a SignMaster webhook on its own, with no Zapier in between. An Airtable automation that starts When webhook received gets its own URL, SignMaster posts to it when a contract is signed, and a Create record action files the answers in your base.
Updated November 5, 2026 · 2 min read
Set it up
- 1
Build the table
Add fields for what you want to keep: Customer, Email, Job address, Contract price, Signed on and Envelope ID.
- 2
Create the automation
In your base, open Automations, add a trigger and choose When webhook received. Airtable shows the webhook URL; copy it.
- 3
Add it in SignMaster
In Settings › Developers › Webhooks, add an endpoint with that URL and tick envelope.completed.
- 4
Send a real sample
Airtable needs a sample request to learn the fields. Sign a test contract made from your template, then choose Run test in Airtable so it picks up the message.
- 5
Create the record
Add a Create record action, pick the table and map each field from the webhook body: data, then fields_by_label, for the answers, and data, then envelope, for the ID and completed_at date.
- 6
Turn it on
Switch the automation on. From now on, every completed contract arrives as a record.
For example, a pool service company gets a record each time a customer signs a season agreement: name, address, pool type, start date and the gate code the customer typed in. The service team filters the table by start date to plan the first week's routes.
Good to know
- Anyone with the webhook URL can create records, and Airtable doesn't check signatures on this trigger, so keep the URL private.
- Each webhook run counts toward your Airtable plan's automation runs, and Airtable accepts up to five requests a second. If it turns one away, SignMaster retries later.
- Airtable caps each request at 100 KB. A SignMaster message is usually a few kilobytes, so only very large templates come anywhere near it.
- Sending from several templates? Add a condition on data.envelope.template_id, or give each template its own endpoint and automation.
When to use Zapier or Make instead
The signed PDF link in data.signed_pdf.url stops working after 24 hours, so a URL field won't keep the document. Zapier's Airtable Create Record and Make's Create a Record can put the file itself into an attachment field. They can also check for an existing record first, with Zapier's Find Record or Make's Search Records, so a message that arrives twice doesn't add a second row.
If you only need a list for reporting, a template's Responses tab exports every answer to CSV, which Airtable can import into a new table.
Questions? Answers.
Do I need Zapier to connect SignMaster and Airtable?
No. Airtable's When webhook received trigger accepts SignMaster's messages directly. Zapier or Make only help with extras, like attaching the PDF file.
Which Airtable plans support webhook triggers?
Airtable says the trigger is available on all plan types, with automation run limits that vary by plan. Check yours if you send a lot of contracts.
Can Airtable start a SignMaster send?
Yes, with a Run a script action that calls the SignMaster REST API. Anyone who can edit the automation can read a key written into the script, so give that key only the scopes it needs.
