The Problem
Most teams have their client data well-structured — in HubSpot, Airtable, or Google Sheets. But when it’s time to send a proposal, contract, or invoice, someone still opens Word and starts copy-pasting.
This is one of those workflow gaps that’s easy to ignore until you’re generating 20+ documents a month.
The Standard Approach (and why it breaks)
Most developers reach for one of these:
- Templated emails in HubSpot — works for simple text, breaks for complex formatted docs
- Google Docs + Apps Script — fragile, hard to maintain, no AI
- Zapier + Docupilot/Documint — gets the job done but limited formatting control
- Custom code (puppeteer, pdfkit, docx.js) — full control but significant dev time
A Cleaner Architecture
Here’s the pattern that actually scales:
Data Source (HubSpot / Airtable / REST API)
↓
Variable Mapping
↓
Document Template
↓
AI Content Layer (Claude / GPT / Gemini)
↓
Output: PDF / DOCX / HTML
The key insight: separate your data layer from your document layer. Your CRM shouldn’t know about your document format, and your document template shouldn’t need custom code to pull data.
Triggering Generation
Two common patterns:
1. Event-based (recommended)
Deal moves to “Won” in HubSpot → webhook fires → document generates automatically
2. On-demand
User clicks a button → POST to /api/generate with record ID → document returned as PDF
What I Built
I ran into this problem building internal tools for agencies and ended up creating GJSDocs (gjsdocs.com) — a document generation engine with native connectors for HubSpot, Airtable, Google Sheets, and a REST API. Supports Claude, ChatGPT, and Gemini with your own API key.
Happy to go deeper on any part of this architecture in the comments — especially the webhook + template variable mapping pattern which trips people up.