Airtable e-sign trigger

Airtable bases track deals, vendors, and hiring pipelines. Atlas adds signing when a checkbox or status change should send a PDF and write results back to the same row.

> Share: "Airtable automation hits middleware. Atlas review_url returns to the row."

Base schema

Use views filtered by "Ready to send" to avoid accidental triggers.

Automation architecture

Airtable Automations cannot attach Bearer secrets safely in all plans. Common pattern:

Airtable trigger (record matches condition)
  → Webhook to Make/n8n/Vercel
  → POST /api/envelope
  → Airtable API PATCH record with review_url

Direct Airtable scripting extension with remoteFetchAsync is possible for Pro bases if API key lives in extension secrets.

Middleware create payload

Map Airtable fields:

{
  "document_url": "{{attachment_public_url}}",
  "webhook_url": "https://your-app.com/hooks/atlas-airtable",
  "metadata": {
    "client_reference_id": "airtable-rec{{recordId}}",
    "external_id": "{{recordId}}"
  },
  "parties": [
    {
      "email": "{{Signer email}}",
      "name": "{{Signer name}}",
      "role": "Customer"
    }
  ]
}

Attachment URLs must be fetchable by Atlas servers. Expiring Airtable attachment links may fail. Copy file to S3 or GCS first if links rot quickly.

Webhook update row

On envelope.signed, handler calls Airtable REST API:

curl -X PATCH "https://api.airtable.com/v0/{baseId}/{tableId}/{recordId}" \
  -H "Authorization: Bearer $AIRTABLE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "fields": {
      "Sign status": "Signed",
      "Signed at": "2026-06-22"
    }
  }'

Attach signed PDF link from Atlas download URL or upload back to Attachment field via upload helper.

Human Send

Internal owner opens review URL from Airtable URL field. Clicks Send after checking detected fields. Status moves to Pending in Airtable when webhook reports envelope.sent.

Zapier and Make alternatives

See Zapier and Make.com guides for visual builders if Airtable scripting is too limited.

Volume guidance

Airtable automations fit tens of sends per month. Above that, migrate orchestration to n8n with the same field mapping.

Interface designer buttons

Airtable Interface buttons can open the Atlas review URL field in a new tab for legal reviewers without giving them API access. Keep Send permission on trusted roles only.

Hiring pipeline variant

Recruiting bases use the same pattern: offer letter attachment, signer email from candidate field, status Single select. Webhook on sign triggers IT provisioning Zap or n8n branch separate from sales ops automation.

Error column pattern

Add Last error text field middleware updates on 402 or 409 responses. Ops filters the view instead of digging through automation logs when sends fail silently.

FAQ

Can Airtable host signing? No. Signers use Atlas pages.

Multiple signers? Pass parties array in order.

Prefill from Airtable columns? Map to template prefill on template send path.

Free tier limits? Atlas gives five free sends for testing. Airtable automation limits are separate.

MCP? Founders can send from Claude and paste envelope ID into Airtable manually during early ops.

Sync back from Atlas without webhook

If you cannot receive webhooks, schedule Airtable automation or n8n poll every ten minutes on open rows where Envelope ID is set and Sign status is not Signed. Call GET /api/envelope/{id}/status. Polling is a backup, not the happy path.

Permissions

Limit who can flip the "Ready to send" checkbox that triggers automation. accidental triggers send draft envelopes to real signers after create returns review URL.

Column types that break flows

Avoid formula fields as signer email source unless middleware validates format. Link fields to Contact tables need extra API fetch to resolve email before Atlas create. Document attachment fields require export to stable URL before Atlas fetch.

Related

• Notion contract signing
• HubSpot document signing
• E-signature API

Extended FAQ

Airtable Enterprise API limits? Batch creates during import may hit rate limits. Add sleep nodes.

Interfaces vs Grid? Interfaces for reviewers opening review URL. Grid for ops bulk edit.

Sync from Salesforce? Synced tables still need middleware for Atlas Bearer auth.

Color-coded status? Single select updated by webhook keeps views simple for leadership.

Free Airtable plan? Automation limits may block scale before Atlas limits do.

Ops handoff

Document which base views trigger automation in runbook linked from Airtable interface. New ops hires should not duplicate automations without disabling old ones, or you will double-send envelopes on the same row update.

Keep a changelog when automation filters change so legal can audit who could trigger sends in each quarter.

API reference

Full route list and request schemas live at /dev. Start with E-signature API for the mental model, then use this guide for copy-paste examples.