How to Send Airtable Records to DocuSign and Update Records When Signed Using Make.com

Introduction

You keep contract metadata and signer details in Airtable but still copy fields into an e-sign tool, wait for the signature, then manually attach the signed PDF and update the record. That manual loop is slow, error prone, and leaves no reliable audit trail.

This guide shows how to build a production-grade Make.com scenario that creates a DocuSign envelope from an Airtable row, sends it for signature, captures DocuSign Connect events for envelope progress, saves the signed PDF to Google Drive, and writes envelope status and file links back into Airtable. By the end you will have an auditable, idempotent flow suitable for legal and revenue teams.

What you will know by the end: the exact Make.com modules and HTTP payloads to use, how to set up DocuSign Connect or envelope-level eventNotification, field mappings to avoid hallucinated keys, and pragmatic error handling when signers decline or DocuSign rate limits occur.

What You'll Need

• Airtable base and table with fields: signer name, signer email, subject, request_id (or use Airtable record ID), envelope_id, envelope_status, signed_pdf_link.
• DocuSign account with API access, integration key, and configured RSA/JWT or OAuth token. DocuSign Connect or envelope eventNotification access for webhook events.
• Make.com account with HTTP module, Airtable, Google Drive, Gmail, and Slack connections. Paid Make.com plan recommended for reliable webhook handling and retries.
• Google Drive folder for storing request JSON and final signed PDFs.
• Optional: a Gmail account to send confirmation emails or a Slack channel to notify the ops team.
• Permissions to create webhooks and manage API keys in DocuSign, and to create and update records in Airtable.

Notes on plans and permissions: DocuSign Connect webhooks require account-level configuration or using eventNotification per envelope. Test in a DocuSign developer account before production.

How It Works (The Logic)

Trigger: Airtable row marked ready for signature. Make.com reads the row and builds a DocuSign envelope payload, including document bytes or a template reference, recipients, and an envelope-level eventNotification that points to a Make.com webhook.

Action: Make.com calls DocuSign to create and send the envelope. DocuSign returns an envelopeId. Make.com writes the envelopeId and initial status back to Airtable and stores the raw request/response JSON in Google Drive.

Event: DocuSign posts envelope events to the Make.com webhook (via Connect or envelope-level eventNotification). When you receive envelope-completed, the scenario downloads the signed PDF, uploads it to Google Drive, updates the Airtable record with the Drive link and envelope_status=completed, and sends a Slack or Gmail notification to the owner.

In short: Airtable row → Make.com builds envelope → DocuSign sends → DocuSign posts completion → Make.com saves PDF → Airtable updated.

Step-by-Step Setup

1. Decide document source and template strategy

• Option A, DocuSign templates: create a DocuSign template with role names and placeholders, then reference templateId in the createEnvelope call. This reduces payload size and keeps legal text in the template.
• Option B, ad hoc PDF or Google Docs: Generate a PDF from Google Docs or pull a PDF from Drive and include it as base64 in the envelope creation. Use this when documents are highly custom per record.

Choose templates when possible. Templates simplify recipient roles and reduce the chance of missing tags.

2. Prepare Airtable fields and view

• Add fields to the table: request_id (text), signer_name, signer_email, envelope_id (text), envelope_status (single select), signed_pdf (URL), docusign_request_json (attachment or long text), last_error (long text).
• Create a saved view Ready for Signature where records become the trigger. Include only records you want processed automatically.

Why: using a view keeps Make.com triggers deterministic and reduces accidental sends.

3. Create the Make.com scenario and webhook listener

• Scenario A (Outbound): start with Airtable "Watch Records in View" for Ready for Signature.
• Scenario B (Inbound): create a separate Make.com HTTP webhook to receive DocuSign Connect or envelope eventNotification POSTs. Name it Webhook: DocuSign Events.

Important: Do not combine the inbound handler and outbound flow in a single long scenario. Keep them separate for reliability and retries.

4. Build the envelope create step in Make.com

In the outbound scenario:

• Module 1: Airtable - Watch Records in View, map required fields.
• Module 2: (Optional) Google Drive - Save a snapshot JSON file of the Airtable row for audit. Store the fileId and include it in later logs.
• Module 3: Tools/Set Variables - build the envelope payload. If you use a template, your payload can be small: { "templateId": "<TEMPLATE_ID>", "templateRoles": [{"email":"{{signer_email}}","name":"{{signer_name}}","roleName":"Client"}], "status":"sent", "eventNotification": {"url":"<MAKE_WEBHOOK_URL>","loggingEnabled":"true","includeDocuments":"true","envelopeEvents":[{"envelopeEventStatusCode":"completed"},{"envelopeEventStatusCode":"declined"},{"envelopeEventStatusCode":"sent"}]} }

If you include the document as bytes, build a multipart upload or use DocuSign's composite templates pattern.

• Module 4: HTTP - Make a request to DocuSign's envelopes endpoint. Use POST /v2.1/accounts/{accountId}/envelopes with Authorization header and the JSON body constructed above.

Gotcha: DocuSign requires proper authentication. Using JWT grants a long-lived server-to-server token appropriate for Make.com. If you use OAuth, refresh tokens must be handled.

5. Map the DocuSign response back to Airtable and save artifacts

• Module 5: Parse the HTTP response. Extract envelopeId and status.
• Module 6: Airtable - Update record: write envelope_id = envelopeId, envelope_status = status, and add a link to the Drive snapshot file. Clear last_error.
• Module 7: Google Drive - save the raw request and response bodies into a per-request folder for later audit.

Why: persistent artifacts make audits and dispute resolution straightforward.

6. Configure DocuSign Connect or envelope eventNotification

Two approaches:

• Account-level DocuSign Connect: configure in DocuSign console to post to your Make.com webhook. This sends many events from across the account, so include verification and filtering in your handler.
• Envelope-level eventNotification: included in the envelope create payload as shown above. This is easier when you want webhooks only for envelopes you create.

Both options will POST a JSON payload containing envelopeId and event information. DocuSign also includes document bytes if you set includeDocuments.

Security tip: validate incoming messages. Use DocuSign's HMAC signature if available, or check known envelopeIds and timestamps against your Airtable records to avoid accepting forged callbacks.

7. Build the inbound webhook handler in Make.com

In the inbound scenario triggered by Webhook: DocuSign Events:

• Module 1: HTTP webhook catch, parse JSON body.
• Module 2: Validate the payload: required keys such as envelopeId and event (status). Optionally verify HMAC signature header or check the origin IP range if you restrict.
• Module 3: Router by envelope event status:
  • If status == completed: proceed to download signed documents.
  • If status == declined or voided: update Airtable with envelope_status and post a Slack alert.

8. Download signed PDF and store in Drive

When envelope completes:

• Module 4: HTTP - GET /v2.1/accounts/{accountId}/envelopes/{envelopeId}/documents/combined to fetch combined signed PDF. Pass Authorization header.
• Module 5: Google Drive - Upload file, name it using request_id and envelopeId, e.g., "signed_{request_id}_{envelopeId}.pdf".

Gotcha: DocuSign returns binary. Use Make.com's HTTP binary handling and pass the binary output into the Drive upload module.

9. Update Airtable and notify stakeholders

• Module 6: Airtable - Find the record by envelope_id or by request_id stored earlier, update envelope_status = completed, signed_pdf = Drive file URL, and add timestamp signed_at.
• Module 7: Slack or Gmail - send a short notification to the record owner with the Drive link and envelope summary. Use a templated message: "Request {{request_id}} signed. Signed PDF: {{drive_url}}."

10. Error handling and retries

• For outbound create failures (4xx), write the API response into Airtable last_error and set envelope_status = error. Post a Slack alert to ops with the envelope payload link in Drive.
• For 429 or 5xx from DocuSign, use Make.com retries with exponential backoff. Log retry attempts into Drive and into a monitoring sheet so you can spot rate limiting patterns.
• For inbound webhook failures, respond HTTP 500 to cause DocuSign to retry, but only after logging the payload. If signature verification fails, respond 200 and log an alert to ops to avoid infinite retries from spoofed payloads.

Real-World Business Scenario

A mid-market consultancy saved hours per week using this exact pattern. Sales marked an Airtable row ready for signature. Make.com created an envelope from a DocuSign template, set the client as the signer, and added an envelope-level eventNotification back to Make.com. When the client completed signing, the signed PDF was automatically stored in a Drive folder and the Airtable row updated with the envelopeId and Drive link. Legal no longer chased signed copies and finance could invoice on the same day the signature completed.

Common Variations

• Use DocuSign templates with compositeTemplates when you need to combine a dynamic Google Docs PDF plus static template content.
• Keep the signed PDF in Airtable as an attachment instead of Drive by downloading the binary and uploading it into the Airtable attachment field, if your Airtable plan supports the file sizes.
• Add an approval gate: create the envelope in created status (draft) and only call the send endpoint after a Slack-based approval button is clicked. This adds a human-in-the-loop safety check for high-value agreements.

Putting this into practice

You now have a full, auditable pattern to move from Airtable to DocuSign and back, using Make.com as the orchestration layer, Google Drive for artifact storage, and Slack/Gmail for notifications. If you want help implementing envelope templates, configuring DocuSign Connect securely, or hardening retries and idempotency, Olmec Dynamics builds and operates these automations for businesses. See how we work at https://olmecdynamics.com.

For related document generation patterns using PandaDoc and Airtable, see our guides on How to Generate and Send Contracts from Airtable to PandaDoc Using Make.com and Notion and How to Connect Airtable to PandaDoc with Make.com to Auto-Generate Contracts.