## Introduction
For sales teams, speed and personalization in generating proposals can be the difference between closing a deal and losing a prospect. Manually creating proposals is time-consuming and prone to errors, leading to delays and inconsistent document quality. Automating the creation of sales proposals streamlines this process, ensuring quick, accurate, and on-brand proposal delivery.
In this article, we will walk through how to build an automation workflow using n8n — an open-source workflow automation tool — to auto-create sales proposals. This workflow benefits sales representatives, sales operations, and revenue teams aiming to reduce manual tasks and improve sales cycle efficiency.
We will integrate Google Sheets (as a CRM-lite or lead database), Google Docs (to serve as proposal templates), and Gmail (to send proposals). The workflow will be triggered by new data entries in Google Sheets, generate a customized proposal in Google Docs, export it as a PDF, and email the proposal directly to the prospect.
—
## What Problem Does This Automation Solve?
– **Problem:** Manual proposal creation is repetitive, error-prone, and delays sending proposals to prospects.
– **Who benefits:** Sales reps save time and can focus more on selling; operations teams get consistent, branded proposals; executives improve deal closing speed and pipeline visibility.
—
## Tools and Services Integrated:
– **n8n:** Orchestrates the entire workflow, handling triggers, data transformations, and API calls.
– **Google Sheets:** Stores client and deal data, acts as trigger source.
– **Google Docs:** Holds the proposal template with placeholders.
– **Google Drive:** For storing generated documents.
– **Gmail:** Sends the final proposal as an email attachment.
—
## Overview of the Workflow
1. **Trigger**: New row added in Google Sheets indicating a new prospect or deal.
2. **Get Data**: Fetch row details such as client name, deal value, contact email.
3. **Generate Proposal Document**: Using Google Docs template, replace placeholders with prospect-specific data.
4. **Export Proposal as PDF**: Convert the Google Doc into a PDF stored in Google Drive.
5. **Send Email**: Email the PDF proposal to the prospect via Gmail.
6. **Update Sheet**: Mark row as “Proposal Sent” with timestamp.
Each step is modular, allowing easy customization and scaling.
—
## Step-by-Step Technical Tutorial
### Prerequisites
– An n8n instance (self-hosted or cloud-hosted)
– Access to Google Sheets, Google Docs, Google Drive, and Gmail with OAuth credentials configured in n8n
– A Google Sheets spreadsheet with columns: `Client Name`, `Contact Email`, `Deal Details`, etc.
– A Google Docs proposal template with clearly defined placeholders (e.g., {{ClientName}}, {{DealValue}})
### Step 1: Set Up the Trigger Node – Google Sheets
– **Node Type:** Google Sheets Trigger
– **Configuration:**
– **Event:** New Spreadsheet Row
– **Spreadsheet ID:** Connect to your sales leads spreadsheet
– **Sheet Name:** Use the relevant sheet name
This node listens for any new prospect data added to the spreadsheet.
### Step 2: Fetch Data for the New Row
If the trigger node does not provide full row data, add a Google Sheets node to fetch all data by row ID.
### Step 3: Prepare Data for Template Replacement
– Use a Function node to map the spreadsheet columns to the placeholders used in the Google Docs template.
– Example code snippet in Function node:
“`javascript
return [{
json: {
clientName: $input.item.json[‘Client Name’],
dealValue: $input.item.json[‘Deal Details’],
contactEmail: $input.item.json[‘Contact Email’],
proposalDate: new Date().toLocaleDateString()
}
}];
“`
### Step 4: Copy Google Docs Template
– **Node Type:** Google Docs
– **Operation:** Copy Document
– **Configuration:**
– Provide the template Document ID
– Destination folder in Google Drive to save the new proposal
– Rename copied doc dynamically, e.g., `Proposal – {{clientName}} – {{date}}`
This creates a unique editable copy per proposal.
### Step 5: Replace Placeholders in the New Google Doc
– **Node Type:** Google Docs (Advanced)
– Use the “Replace Text” operation or via the Google Docs API integration within n8n to find placeholders like `{{ClientName}}` and replace them with actual data.
– For each placeholder in your template, configure a Replace Text node or API calls with:
– Text to find (e.g., `{{ClientName}}`)
– Replace with `{{$json.clientName}}`
### Step 6: Export Google Doc as PDF
– **Node Type:** Google Drive
– **Operation:** Export File
– **Configuration:**
– File ID: ID of the copied & updated Google Doc
– Export format: PDF
This node will generate a PDF file ready for emailing.
### Step 7: Send Email with Proposal PDF Attachment
– **Node Type:** Gmail
– **Operation:** Send Email
– **Configuration:**
– To: `{{$json.contactEmail}}`
– Subject: `Your Proposal from [Company]`
– Body: Personalized message referencing client name and deal
– Attachment: File from the Google Drive export node
### Step 8: Update Google Sheet Row – Mark Proposal Sent
– **Node Type:** Google Sheets
– **Operation:** Update Row
– **Configuration:**
– Update a column (e.g., “Status”) with “Proposal Sent”
– Add Timestamp to track when proposal was sent
—
## Handling Common Errors and Tips
– **Authentication:** Ensure OAuth credentials for Google services are correctly configured and refreshed if expired.
– **API Quotas:** Google APIs have quotas; large-scale operations may require quota increase requests.
– **Template Placeholders:** Keep placeholders consistent and uniquely identifiable (use double curly braces) to avoid accidental replacement.
– **Error Handling in n8n:** Use the Error Trigger node or add retry logic to handle intermittent API failures gracefully.
– **Data Validation:** Validate spreadsheet data before processing to avoid malformed proposals.
– **Permissions:** The Google Drive folder used for storing proposals must have the appropriate permissions.
—
## Scaling and Adapting the Workflow
– **Multi-language proposals:** Extend template replacements and create multiple language versions.
– **CRM Integration:** Integrate with HubSpot, Salesforce, or Pipedrive instead of Google Sheets for advanced lead management.
– **Advanced Formatting:** Use the Google Docs API for more complex proposal generation, including charts and tables.
– **Follow-up Automation:** Add subsequent triggers to remind sales reps of follow-ups post-proposal.
– **Dashboard Reporting:** Aggregate proposal statuses from Google Sheets or a database to monitor pipeline health.
—
## Summary
Automating proposal creation using n8n dramatically reduces manual effort in sales workflows. By integrating Google Sheets, Google Docs, Google Drive, and Gmail, we created a seamless workflow that:
– Listens for new prospect entries
– Generates personalized proposals from a template
– Converts proposals to PDFs
– Sends the proposals directly to prospects via email
– Tracks proposals sent
The modular nature of n8n nodes allows for customization to fit your sales process perfectly. With robust error handling, proper template design, and good data hygiene, this automation can accelerate your sales cycles and improve consistency across your team.
—
### Bonus Tip: Version Control Your Proposal Templates
Maintain your Google Docs template versions in a dedicated Google Drive folder and implement a naming convention with version numbers and dates. This prevents accidental overwrites and allows rolling back if needed. You can automate template updates and notify your sales team via Slack using n8n when a new proposal version is published.