Gmail + Google Drive proposals, sent and filed fast
Proposal requests show up at the worst times. You copy a template, hunt for the latest pricing, fix formatting, export to PDF, attach it to an email, then try to remember where you saved the final version.
Sales managers feel the follow-up lag immediately. Agency owners notice it when “quick quotes” start eating mornings. And ops folks end up cleaning the file mess later. This Drive proposal automation takes the busywork out so proposals go out fast and land in the right folder every time.
You’ll set up an n8n workflow that turns incoming deal or form data into a branded PDF, emails it via Gmail, archives it in Google Drive, and pings your team in Slack with the link.
How This Automation Works
Here’s the complete workflow you’ll be setting up:
n8n Workflow Template: Gmail + Google Drive proposals, sent and filed fast
flowchart LR
subgraph sg0["Flow 1"]
direction LR
n0["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/webhook.dark.svg' width='40' height='40' /></div><br/>Webhook Trigger"]
n1["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/code.svg' width='40' height='40' /></div><br/>Validate Input Data"]
n2["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/code.svg' width='40' height='40' /></div><br/>Enrich with Company Data"]
n3["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/code.svg' width='40' height='40' /></div><br/>Generate Professional HTML"]
n4@{ icon: "mdi:cog", form: "rounded", label: "Save to Google Drive", pos: "b", h: 48 }
n5["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/httprequest.dark.svg' width='40' height='40' /></div><br/>Notify Team (Slack)"]
n6@{ icon: "mdi:location-exit", form: "rounded", label: "HTML to PDF", pos: "b", h: 48 }
n7@{ icon: "mdi:message-outline", form: "rounded", label: "Send to Client", pos: "b", h: 48 }
n6 --> n4
n7 --> n5
n0 --> n1
n1 --> n2
n4 --> n7
n2 --> n3
n3 --> n6
end
%% Styling
classDef trigger fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
classDef ai fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
classDef aiModel fill:#e8eaf6,stroke:#3f51b5,stroke-width:2px
classDef decision fill:#fff8e1,stroke:#f9a825,stroke-width:2px
classDef database fill:#fce4ec,stroke:#c2185b,stroke-width:2px
classDef api fill:#fff3e0,stroke:#e65100,stroke-width:2px
classDef code fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
classDef disabled stroke-dasharray: 5 5,opacity: 0.5
class n0,n5 api
class n1,n2,n3 code
classDef customIcon fill:none,stroke:none
class n0,n1,n2,n3,n5 customIcon
Why This Matters: Proposals Get Delayed (and Lost)
Creating proposals is one of those tasks that looks simple until you do it three times in one day. The details have to be right: client name, scope, line items, taxes or discounts, payment terms, and the “this expires in 30 days” language you forgot to update last time. Then comes the polish. Fonts, spacing, your logo, a clean PDF export, a decent email, and finally filing it somewhere future-you can find. When you’re busy, you send “good enough,” and that’s when errors slip in and follow-ups slow down.
It adds up fast. Here’s where it usually breaks down.
- You rebuild the same proposal structure repeatedly, which quietly burns a couple hours a week.
- Line item math gets rechecked (and still goes wrong), especially when discounts or tax are involved.
- Files end up scattered across laptops and “Final_v7” folders, so resends and audits turn into a search party.
- The team doesn’t know it was sent, so follow-ups are late or duplicated and the client experience feels sloppy.
What You’ll Build: A Proposal Factory That Runs on Incoming Requests
This workflow starts with a webhook, so it can accept proposal details from a CRM stage change, a form submission, or any system that can send data to a URL. n8n validates the input first (required fields, email formatting, and pricing totals) so you’re not sending half-filled documents. Then it enriches the proposal with your company details like logo, contact info, and standard terms, and generates a clean HTML proposal layout. That HTML is converted into a print-ready PDF using an HTML-to-PDF service. Finally, the PDF is filed into Google Drive with an intelligent filename, emailed to the client via Gmail as an attachment, and your sales team gets a Slack message with the proposal number and Drive link.
The workflow begins when a new request hits your webhook. From there, n8n assembles and converts the proposal automatically, then handles delivery and storage. The end result is a client-ready PDF and a tidy record trail you can trust.
What You’re Building
| What Gets Automated | What You’ll Achieve |
|---|---|
|
|
Expected Results
Say you send 15 proposals a week. Manually, assume about 2 hours each once you include formatting, PDF export, email drafting, and filing. That’s roughly 30 hours weekly spent on a task that isn’t selling. With this workflow, the “work” becomes a quick webhook submission (or automatic CRM trigger) plus maybe 5 minutes to sanity-check the output. Even if you still review every proposal, you’re getting back about 25 hours most weeks.
Before You Start
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Gmail for sending proposal emails with attachments
- Google Drive to store and organize the PDFs
- HTML-to-PDF API key (get it from your PDF conversion provider)
Skill level: Beginner. You’ll connect accounts, paste a webhook payload to test, and adjust a few text fields for branding.
Want someone to build this for you? Talk to an automation expert (free 15-minute consultation).
Step by Step
A new proposal request hits your webhook. This can come from a CRM workflow, a form tool, or a simple internal request page. The webhook delivers client details, scope notes, and line items into n8n in one structured payload.
The workflow validates and cleans the data. A code step checks required fields and catches obvious issues (missing email, missing items, totals that don’t add up). If something is off, you can stop the flow before an embarrassing PDF gets generated.
Your branding and proposal layout are assembled. Company details get added (logo URL, contact information, payment terms), then the workflow builds a professional HTML document with consistent fonts, colors, and itemized pricing.
The PDF is created, filed, and delivered. An HTML-to-PDF service converts the proposal into a print-ready PDF. n8n saves it into Google Drive with a clear filename, sends the email via Gmail with the PDF attached, and then posts a Slack message so the team can follow up using the Drive link.
You can easily modify the proposal template and folder structure to match how your team sells. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Webhook Trigger
Set up the inbound request that starts the proposal workflow and validates payloads.
- Add and open Incoming Webhook Start.
- Set HTTP Method to
POST. - Set Path to
proposal-generator. - Use the generated webhook URL as the endpoint for your proposal requests.
Tip: In the incoming JSON, include clientName, clientEmail, clientCompany, projectTitle, and an items array to pass validation in Verify Input Details.
Step 2: Connect Google Drive
Configure storage for the generated PDF file.
- Open Archive to Drive and select your Google Drive destination.
- Set Name to
={{ $('Build Proposal HTML').item.json.fileName }}to dynamically name the PDF file. - Choose a Drive and Folder (e.g.,
My Driveandroot). - Credential Required: Connect your Google Drive credentials (this node needs credentials but none are configured).
⚠️ Common Pitfall: If Google Drive credentials are missing, Archive to Drive will fail and downstream nodes (Email Client Proposal and Slack Team Update) will not run.
Step 3: Set Up Processing Nodes
Validate inputs, add company branding defaults, generate HTML, and convert it to PDF.
- In Verify Input Details, keep the validation logic as provided to enforce required fields and calculate totals.
- In Add Company Context, customize your company defaults like
companyName,companyEmail,companyPhone, andcompanyWebsite. - In Build Proposal HTML, confirm the HTML template and file naming logic remain intact for consistent PDF output.
- Open Convert HTML to PDF and verify it receives the HTML generated by Build Proposal HTML.
⚠️ Common Pitfall: Replace [YOUR_EMAIL] in Add Company Context to avoid sending proposals with a placeholder email.
Step 4: Configure Output/Action Nodes
Send the proposal to the client and notify your team after the file is archived.
- Open Email Client Proposal and set up the email recipient and message body as needed.
- Credential Required: Connect your gmailOAuth2 credentials in Email Client Proposal.
- Open Slack Team Update and replace the URL with your Slack webhook:
https://hooks.slack.com/services/[CONFIGURE_YOUR_TOKEN]. - Keep JSON Body enabled and preserve the expression-based fields that pull proposal details and the Drive link.
Execution order: Incoming Webhook Start → Verify Input Details → Add Company Context → Build Proposal HTML → Convert HTML to PDF → Archive to Drive → Email Client Proposal → Slack Team Update.
Step 5: Test and Activate Your Workflow
Run a full test to confirm validation, PDF generation, storage, email delivery, and Slack notifications.
- Click Execute Workflow and send a POST request to the Incoming Webhook Start URL with a sample proposal payload.
- Confirm a PDF is created in Google Drive by Archive to Drive and the file name matches the expression-based format.
- Verify the client receives the email from Email Client Proposal and Slack receives a message from Slack Team Update with a valid Drive link.
- Once everything looks correct, toggle the workflow to Active for production use.
Troubleshooting Tips
- Google Drive credentials can expire or need specific permissions. If things break, check the n8n Credentials screen and confirm the connected Google account can write to the target folder ID.
- If you’re using Wait nodes or external rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
- Default prompts in AI nodes are generic. Add your brand voice early or you’ll be editing outputs forever.
Quick Answers
About 30 minutes if your Google accounts are ready.
No. You’ll mostly connect accounts and edit a few text fields for branding and folder locations.
Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in HTML-to-PDF API costs from your chosen provider.
Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.
Yes, and you should. Most teams start by editing the “Add Company Context” step (logo, address, default terms), then tweaking “Build Proposal HTML” to match their service packages. If you use a different PDF provider, swap the “Convert HTML to PDF” node to the service you prefer. You can also add an approval checkpoint before the Gmail send, which is handy for enterprise deals or regulated industries.
Usually it’s the folder permission or a changed folder ID. Confirm the Google account in n8n has access to the destination folder, then recheck the folder ID you configured in the Drive step. If it still fails, reconnect the Google Drive credential so OAuth permissions refresh. Also watch for shared drives, which often require extra settings to write files correctly.
If you self-host, volume mainly depends on your server and your PDF provider’s limits; most small teams comfortably run dozens of proposals a day. On n8n Cloud, capacity depends on your plan’s monthly executions.
Sometimes, yes. This workflow includes validation logic, document generation, and a multi-step file/email/Slack chain, which is where n8n tends to feel more flexible (and less “pay per tiny step”). Zapier or Make can work if you already live there, but document-heavy flows often get awkward once you need custom HTML, precise file naming, or branching rules. The other consideration is cost: self-hosted n8n can run unlimited executions, while many no-code tools scale pricing quickly as volume grows. If you’re unsure, map your real weekly volume and the number of steps you need. Talk to an automation expert and you’ll get a straight recommendation.
Once this is live, proposals stop being a bottleneck and start being a button. Your workflow handles the repetitive parts, so you can focus on the deal.
Need Help Setting This Up?
Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.
