Skip to main content
DOCUMENTS

Every sales document lives in one place — proposals, invoices, contracts, quotes, and statements of work — with the same PDF render pipeline, the same email send flow, and the same audit trail.

​
Document Types

ParsaLink ships five document types out of the box. They share one underlying model — the Type field tells the system which status workflow and which template defaults to apply.
TypeWhat it’s forStatus workflow
ProposalA pitch / scope for a prospectdraft → sent → viewed → revision_requested → revised → accepted / rejected / expired
InvoiceA billable invoice you want a customer to paydraft → sent → viewed → paid / partially_paid / overdue
ContractA binding agreement requiring signaturedraft → sent → viewed → signed → countersigned → active → terminated
QuoteA formal price quote, narrower than a full proposaldraft → sent → viewed → accepted / rejected / expired
SOWStatement of Work tied to a contract or projectdraft → sent → viewed → accepted / rejected
Need a deeper walkthrough of proposals specifically? See the Proposals page for the AI-assisted proposal generation flow, branding, sections, and follow-up automation.

​
What’s the Same Across All Types

Every document — regardless of type — gets:
  • Linking — attach to an Opportunity, Account, and one or more Contacts.
  • PDF render — generate a branded PDF on demand (download or send by email).
  • Email send — pick a recipient contact, customize the message, send via your configured Email account.
  • Status tracking — when a recipient opens the PDF link, the document status auto-advances to viewed.
  • Activity log — every status transition is timestamped on the entity timeline.
  • Versioning — edit and resend without losing the original; the previous version stays on record.

​
Google Drive Sync

Any document can optionally sync its rendered PDF to your workspace’s Google Drive.

​
How It Works

When you mark a document with sync_target = google_drive, ParsaLink:
  1. Renders the latest PDF.
  2. Uploads it to your Google Drive in a per-tenant folder structure.
  3. Stores the resulting Drive file ID + URL on the document.
Subsequent edits push a new revision (not a new file), so the Drive link is stable for sharing.

​
Setting It Up

1

Connect Google Workspace

First connect your Google account at Settings → Integrations → Google Workspace — the drive.file scope is included by default. See the Google Workspace page for the connection walkthrough.
2

Enable Drive sync on documents

At Settings → Document Sync, toggle “Sync to Google Drive” for the document types you want. You can sync proposals but not invoices, for example.
3

Choose folder

Pick the target folder in your Drive. Defaults to a ParsaLink Documents folder created at first sync.
4

Sync a document

On any document detail page, click Sync to Drive. Watch the status flip from parsalink_only to google_drive.

​
Unsync

To stop syncing a document, click Unsync from Drive on the detail page. The file stays in Drive (you can delete it manually) but ParsaLink will no longer push updates.
Drive sync is one-way (ParsaLink → Drive). Editing the file directly in Drive doesn’t write back to the CRM. If you need round-trip editing, use Google Docs from the agent instead.

​
Choosing the Right Document Type

Most teams pick the type by the use case:
  • Proposals for the initial pitch (often AI-assisted; see the Proposals deep-dive)
  • Quotes when you have a more transactional, line-item-driven price-fix
  • Contracts when signatures are needed (uploads via the Documents API once signed)
  • Invoices when it’s time to get paid
  • SOWs tied to an active engagement
You can convert a Quote to a Proposal or a Proposal to an Invoice with one click — the document type field swaps, the status resets to draft, and the activity trail is preserved.

​
Documents from the AI Agent

The CRM AI agent can create, edit, and send any document type:
“Draft a one-page proposal for the Globex opportunity using the AI Marketing Audit template and send it to John as soon as it’s ready.”
The agent calls the documents namespace tools, drafts the document, shows you a preview, and only sends once you confirm. See AI Chat for the conversational flow.