How to Automatically generate client proposals from Airtable using Make.com and PandaDoc

Introduction

If your team spends 10 to 15 minutes per proposal copying data from Airtable into PandaDoc, you are losing time and focus. The moment a new client inquiry hits Airtable, that data sits in isolation until someone manually crafts a proposal. You know there is a better way. This post shows you how to connect Airtable to PandaDoc via Make.com to automatically generate client proposals with the right data, in the right template, and then update Airtable with the status and document link.

You will learn a practical end-to-end setup you can implement today. By the end, you will know exactly how to wire Airtable, Make.com and PandaDoc to generate and send proposals without manual data entry.

What You'll Need

• Airtable: a base with a Proposals table containing fields like Client Name, Company, Project Name, Description, Line Items, Total and Due Date.
• PandaDoc: a document template that has merge fields for the client name, company, project details, line items and totals.
• Make.com: access to create a scenario that connects Airtable and PandaDoc. A plan that supports multi-step workflows and external services is recommended.
• Optional: Slack for notifications, and a base for storing PandaDoc URLs in Airtable.
• Prerequisites: PandaDoc account with a ready-to-use proposal template; Airtable API key, and a Make.com connection to Airtable and PandaDoc.

How It Works (The Logic)

• Trigger: A new record is added to Airtable in the Proposals table with Status set to New.
• Action: Make.com reads the record details from Airtable.
• Action: PandaDoc creates a document from your template and maps Airtable fields into PandaDoc merge fields.
• Optional Action: Send the document for signature via PandaDoc if you require e signatures.
• Action: Make.com updates the Airtable record with the PandaDoc Document ID and Document URL.
• Optional Action: Post a notification to Slack about the new proposal.

This flow keeps your data synchronized and your team informed without manual data entry.

Step-by-Step Setup

1. Create a new Make.com scenario. Name it something like Airtable to PandaDoc – Proposals.

2. Add Airtable as the trigger module. Choose Watch Records. Connect your Airtable account, select the base (e.g., SalesOps) and the Proposals table. Pick a View that shows New records or use a filter for Status equals "New". Set the trigger to watch for new or updated records.

3. Add a second Airtable module to Get a Record by ID. Use the Record ID from the trigger to fetch the full row data. This ensures you have all fields needed for PandaDoc, including line items and totals.

4. Add PandaDoc module. Choose Create Document from Template. Pick the PandaDoc template you prepared for proposals. Map template variables to Airtable fields. Example mappings:

   • client_name -> Airtable: Client Name
   • client_company -> Airtable: Company
   • project_title -> Airtable: Project Name
   • project_description -> Airtable: Description
   • line_items -> Airtable: Line Items (format this as a JSON array or as a structure your template supports)
   • total_amount -> Airtable: Total
   • due_date -> Airtable: Due Date

5. If you want signatures, add a second PandaDoc action: Send Document for Signature. Pass recipient email from Airtable and include a short message.

6. Add Slack (optional): Post a message to your proposals channel with the PandaDoc link and a summary of the client and project.

7. Add Airtable module: Update a Record. Use the original Record ID to update fields such as PandaDoc_ID, PandaDoc_Document_URL, and Status (for example to Sent or In Review).

8. Turn on the scenario. Test by adding a new record in Airtable with Status New and verify the document is created in PandaDoc, then updated back in Airtable and notified in Slack.

9. Validate field formats. If your template expects line items as a list, ensure your Airtable field is formatted accordingly or transform the data in Make.com using a helper function before sending to PandaDoc.

10. Monitor and iterate. Make sure to set up error handlers in Make.com for failed document creation or signature, and add a retry policy to keep the flow robust.

Real-World Business Scenario

A small software consultancy uses Airtable to track client prospects. When a new prospect record lands with a proposed project scope, the Make.com scenario creates a PandaDoc proposal from a branded template, fills in the client details and line items, and sends it for signature. The Airtable row is updated with the PandaDoc link, and the team gets a Slack alert. The entire process takes under two minutes per proposal instead of 15, and the data is always consistent across Airtable and PandaDoc. This is the exact kind of automation we implement for clients at Olmec Dynamics. If you want a hand turning this into a polished production workflow for your business, Olmec Dynamics creates these exact automation patterns for clients across CRM, document generation and e-signature stacks. Learn more about our approach and capabilities at Olmec Dynamics.

Common Variations

• Add a per-proposal PDF copy that saves to Google Drive or Dropbox automatically.

• Implement an approval step in PandaDoc before sending for signature based on the proposal value.

• Filter by deal value so only high value proposals trigger signatures or Slack alerts.

• Extend to include a post-proposal nurture flow in your CRM, for example updating a Lead or Opportunity stage in your CRM when PandaDoc status changes.

A Practical takeaway

What you just built is a robust end-to-end data to document automation. It reduces manual data entry, removes copy paste errors, and shortens the time from inquiry to signed proposal. If you want a hand turning this into a polished production workflow for your business, Olmec Dynamics creates these exact automation patterns for clients across CRM, document generation and e-signature stacks. Learn more about our approach and capabilities at Olmec Dynamics.