A narrow, safety-first document merge alternative
DocForge is an independent Google Sheets add-on for a simple document merge: one Google Docs template, a copied spreadsheet, explicit field mapping, one exact source-row preview, and one verified Docs or PDF output before a batch.
Quick fit check
| Need | Migration fit |
|---|---|
| One Google Docs template populated from Sheet columns | Good copied-sheet test candidate. |
| Generate one Google Doc or PDF and inspect it first | Good fit: one-row preview and one-output proof are the gate. |
| Many conditional templates or complex routing | Do not migrate yet. |
| Automated sharing, advanced attachment delivery, or enterprise document management | Outside this migration slice. |
| Legal approval, contract lifecycle, or signature workflow | Not a DocForge use case. |
Autocrat-style workflow vs broad document automation vs DocForge
DocForge is not trying to replace every job, trigger, approval, signature, or delivery feature. It focuses on proving and reconciling one-template batches.
| Decision point | Autocrat-style workflow | Broad document automation | DocForge |
|---|---|---|---|
| Primary job | Mature document merge jobs with established trigger and delivery patterns. | Documents plus approvals, signatures, webhooks, payments, or multi-app workflows. | One-template verified batches from Google Sheets. |
| Before a batch | Copy the Sheet/template and prove the exact existing job configuration. | Use the provider's preview, workflow test, and account controls. | Field scan, duplicate/missing/blank checks, exact one-row preview, approval, and one opened output. |
| Proof after changes | Retest after template, mapping, source, naming, or folder changes. | Varies by workflow platform. | Durable proof fingerprint invalidates after relevant workflow changes. |
| Repeat batch | Inspect prior outputs before rerunning. | Varies by provider and plan. | Manifest reuses unchanged accessible outputs and identifies changed, missing, or failed rows. |
| Failure recovery | Avoid blindly rerunning successful rows. | May include broad job history and automation controls. | Retry failed rows only, then reconcile expected/generated/reused/changed/failed totals. |
Copied-sheet migration test
- Copy the original spreadsheet and duplicate one simple Google Docs template.
- Use synthetic or non-sensitive data in the copied sheet.
- Select the copied template and scan every
{{merge field}}. - Map each field to one Sheet column; fix missing, duplicate, or blank headers.
- Run Preflight and inspect the exact values for one selected source row.
- Generate one Google Doc or PDF and open it.
- Confirm field values, file name, output type, long-text layout, and destination before any batch.
Why the one-output gate matters
A successful configuration save does not prove a document merge. The useful result is an output file that contains the expected values and layout. If a field is unmapped, a source header is duplicated, or a selected row is blank, the workflow should stop before creating a batch of incorrect files.
Watch the complete one-file proof and recovery tutorial
The controlled tutorial covers tag/header/access diagnosis, a stable row ID, Preflight, exact preview, one-file proof, durable proof invalidation, manifest status, failed-only retry, and reconciliation.