The Formstack Documents alternative for documents born from intake
Formstack Documents — formerly WebMerge — is genuinely good at what it is for: no-code generation that pulls data from CRMs, form builders and other systems into Word, PowerPoint and PDF templates, and delivers the result onward. If your documents are driven by data living in many systems, it may well be the right choice. Teams come here when the data is an intake — a claim, an application, an order — and the document should be produced by the same record, at the moment its workflow moves.
The usual triggers
Three reasons people search for this page
Not adjectives — each one is a difference in mechanism, and each is checkable in behaviour before you commit anything.
-
The document comes from the record
A standalone generator waits for data to be sent to it. In Faldaro the template merges the submission it belongs to — typed answers and server-computed values — and generation is a workflow action: when the claim reaches Approved, the settlement letter is produced and attached to that record.
-
The PDF you already use
When the paperwork must look exactly like the original — a certificate, a carrier-branded schedule, a government form — the facsimile engine turns its pages into the template itself: vector rules, editable text, extracted images. You click a line to bind a field to it. Converting is plain computation and costs no AI credits.
-
A template cannot be turned against you
Templates are a closed set of blocks — or, for a facsimile, markup the platform rebuilds itself from a closed vocabulary — never HTML it trusts. Every merged value is escaped, images are your own uploaded files rather than URLs, and the renderer is denied every external resource, so a submitted value cannot smuggle markup into your paperwork.
The full template reference — blocks, the facsimile engine, budgets — is in the documents guide. To turn a paper form into the online form that feeds it, try the free PDF to online form converter.
How it runs
From template to attached PDF
No merge service in between: the submission, the template and the generated document live in one place.
-
1 Build or reproduce the template
Compose it from blocks — headings, paragraphs, tables, images, page breaks — or describe it and let the AI draft it, or reproduce your existing PDF exactly.
-
2 Merge the submission
Reference field slugs in the text, repeat a table row per line item, show a paragraph only when a condition holds, and compute values with the same closed expression language the form uses.
-
3 Generate on the move
Attach generation to a transition or a rule. It runs after the move commits, so a template that fails cannot un-move a record — and the PDF lands on the record’s Documents tab, ready to email or to send for signature.
See documents alongside payments and signatures on the documents and payments page, or start from the certificate of insurance request template.
Choosing honestly
When a dedicated generator is still the better tool
The fit is a question of where the data lives and what the output has to be.
-
Stay with a generator when
the data lives in a CRM or a spreadsheet rather than a form, the output must be an editable Word or PowerPoint file, or one document merges records from several systems at once.
-
Move to Faldaro when
the data is an intake from outside, the document belongs to one record and should appear the moment it moves, and it may need signing, paying or approving before the work is done.
Fair questions
Can Faldaro produce Word or PowerPoint files?
No — Faldaro generates PDFs, with searchable text painted directly from the template. If your process needs editable Word or PowerPoint output, a dedicated document generator is the honest choice.
Can it generate documents from Salesforce or a spreadsheet?
Not directly. Faldaro templates merge Faldaro submissions. Data can arrive as submissions through the public form, the API, email-to-form or a CSV import, and generation then happens on the record — but if your documents are driven by data that lives in a CRM, a generator that reads the CRM is the better fit.
Do templates stay stable once documents are out?
Yes. Templates are versioned like forms: publishing freezes a version, a document renders through the version live for its submission, and editing a live template starts a new draft that changes nothing already produced.
Which plans include documents?
PDF documents are on every plan, including the free plan with unlimited forms and ten thousand submissions a month. Signature requests over a generated document are on Team and above — the pricing page lists exactly what each tier grants.
Generate documents where the work moves
The free plan includes unlimited forms, ten thousand submissions a month and PDF documents generated from every one of them.
No card required.