DFDocForge
Google Sheets document merge

Prove one file. Generate each row once.

DocForge binds a one-file proof to the selected template, source headers, mapping, stable key, naming, and output. Its manifest reuses unchanged successful outputs, retries failed rows only, and reconciles the batch.

Durable one-file proof Output manifest Retry failed only Batch reconciliation
Install from Marketplace
Document generation previewTemplate mapped
Google Sheetsource rows
Rows86 records
Name, Course, Date, Score
Docs templatecertificate
Placeholder{{Name}}
Generated as Google Doc or PDF
DocForgeWorkspace add-on

Connect a Docs template, map sheet columns to placeholders, preview one file, then generate the batch.

Preview generated
1. Configure2. Preview3. Launch

Verified Batch: one-template reliability.

The difference is not more connectors. It is knowing which expected rows were generated, reused, changed, or failed—and refusing an old proof after the workflow changes.

1

Choose a stable row ID

Use an order, invoice, certificate, member, or case ID when available; duplicate and blank keys block Preflight.

2

Bind and reuse the proof

The template version, headers, mapping, output, and proof-row hash must still match after the sidebar closes.

3

Retry and reconcile

Leave successful outputs untouched, retry failed rows only, and compare expected, generated, reused, changed, and failed totals.

A focused workflow, not another bulky form builder.

Each FormSuite add-on does one operational job around Google Forms, Sheets, Docs, or Gmail — then gets out of the way.

1

Choose template

Start from a Google Docs file with placeholders.

2

Map fields

Connect sheet columns to document tags.

3

Preview then run

Generate one file before bulk output.

Testing a simple Autocrat-style document merge?

Start with a copied spreadsheet and one Google Docs template. DocForge is independent and does not claim full Autocrat feature parity.

Migration fit checklist

Check whether a one-template Sheets-to-Docs or PDF workflow fits the current product boundary.

Fields not replacing

Compare template variables, Sheet headers, mapping, blanks, and the one-row preview.

See a manifest-protected verified batch.

The controlled 31-second proof shows durable one-file proof, unchanged-output reuse, changed-workflow invalidation, failed-only retry, and reconciliation. It does not claim full Autocrat feature parity.

Watch Verified Batch proofRun the one-row checklist

Frequently asked questions

Can it create PDFs?

Yes. The workflow supports generating documents and PDF-style outputs from rows.

Do I need a template?

Yes. A Google Docs template gives the generated files their structure.

Will a rerun duplicate successful files?

An unchanged successful row with an accessible output is reused from the manifest. A changed template, header set, mapping, key, naming pattern, folder, or output requires a new one-file proof.