A document is a PDF that Formspring fills from one response: an agreement, a quote, an order confirmation or a filled-in application form. You prepare a template once on the form, then generate a document for any response with one click, through the API or through an agent. You can also upload a PDF you already have and ask for signatures on it directly: see Create a signing request.
Every document, whether generated or uploaded, collects in Documents in the workspace navigation, next to the signing requests made from it. A document is ready to send for signature once it shows Ready. To collect signatures, see Electronic signing.
Documents are included with the Scale plan, with a monthly allowance. See Plans and allowances.
Two kinds of template
| Kind | What you provide | Best for |
|---|---|---|
| Text and layout | A short HTML layout with placeholders | Agreements, quotes and letters you design in Formspring |
| PDF form | A PDF that already has fillable form fields | Official forms you must keep exactly as issued |
Open Documents from the form's settings to manage both: New text template or New template from a PDF form. Every save creates a new, numbered version. A version never changes after it is saved, so a document always shows exactly which version it came from, and editing a template never rewrites documents you already generated.
Text and layout templates
Write the layout and drop in placeholders such as {{fld_9a41c07be2d3}}. Placeholders use the stable field ID, not the field label, so renaming a label or a field never breaks a template. The field picker next to the editor inserts the right ID for you. See Stable field IDs.
{{#rows fld_items}}...{{/rows}}repeats a block for every entry of a list answer. Inside it,{{.}}is the entry and{{@index}}is its position.{{submission.id}},{{submission.submitted_at}},{{form.name}}and{{document.title}}are always available.- Dates, numbers and amounts are formatted for the template's language, so
1234.5becomes1.234,50 €in a German template. - You can add a logo or other picture with Insert image, which embeds a PNG, JPEG or GIF image directly in the layout (up to 300 KB and 4,000 pixels per side, at most 10 per template). Pictures are stored inside the template. Formspring never fetches pictures, fonts or styles from a web address while it renders.
Only plain layout markup is kept. Scripts, forms, frames, remote files and event handlers are removed when you save.
The Preview PDF with sample data button renders the draft with sample data so you see the page breaks before anyone depends on it.
Characters and fonts
Documents use a bundled font with broad coverage of Latin, Greek and Cyrillic text, including accents and symbols such as €. It does not contain Chinese, Japanese, Korean, Arabic, Hebrew or Indic scripts.
Formspring does not draw empty boxes in their place. If a template contains such characters you cannot save it, and if an answer contains them the document fails with a message that names the characters (for example 山 (U+5C71)). Change the answer or the template and generate the document again.
PDF form templates
Upload a PDF that has fillable fields. Formspring lists the fields it finds (text, checkbox, radio buttons and drop-downs) and you map each one to a form field by choosing from a list. When you generate a document:
- text fields get the answer, formatted for the template's language;
- a checkbox is ticked when the answer is a yes, a tick or has any selection;
- radio buttons select the option whose name matches the answer;
- the filled fields are locked so the recipient sees what was generated;
- your uploaded file is stored privately and never changed. The result is a new PDF that begins with the exact bytes of your upload.
PDF viewers draw the filled fields with the form's own font, so these forms accept text in Western European writing. A value with other characters fails the document with a message naming the fields; use a text and layout template for those languages. Protected (password) PDFs are refused with a clear message, and a PDF without fillable fields cannot be used as a form template.
Generating a document
On a response, open the Documents and signatures panel, choose a template and press Generate document. Rendering happens in the background on a restricted worker that has no network access.
| Status | Meaning |
|---|---|
| Queued | Waiting for a worker |
| Rendering | Being drawn |
| Ready | You can download it or send it for signing |
| Failed | Shows the reason and a Retry render button |
A failed document is never hidden. Fix the cause (for example an unsupported character in an answer) and press Retry render, or generate a new document. A ready document is never overwritten.
Uploading a PDF
Choose New signing request in Documents and upload the PDF. It can be up to 20 MB and 100 pages. Before it can be used it is checked: a file with a password is refused, and a file that carries scripts, launch actions or embedded files is quarantined and can never be sent. Upload a clean copy instead. Uploaded files are stored privately and never changed; Formspring only reads them and, when a request is completed, adds the signature marks and a signature page to a copy.
Templates that belong to the workspace
A template can belong to one form, or to the whole workspace. A workspace template can name signer roles such as "Client" with {{signer.client}}, and is available when you prepare a request in Documents under Templates. Publishing, archiving and versioning work the same way for both: a published version never changes, and a request made from it keeps pointing at that version. Creating and publishing templates needs the templates:manage permission.
Who can download
Only people who may view that response in your workspace, and hold the documents:read permission, can download its documents. Another workspace, another form, or another response cannot reach it by guessing an address: the answer is always "not found". Short-lived download links (five minutes) are bound to the person who requested them.
Plans and allowances
Documents are included with the Scale plan. Each workspace has a monthly allowance of generated documents:
| Plan | Documents per month |
|---|---|
| Free | Not included |
| Pro | Not included |
| Team | Not included |
| Scale | 2,000 |
A document counts once when you generate it. Retrying a failed document does not count again, and documents that failed do not count at all. When the allowance is used up you are told how many were used and nothing already generated is affected. The panel shows your usage for the month.
API and agents
Everything on this page is available over the API and to agents through the MCP server: list templates, create a template version, generate a document, read its status, retry it and download it. Documents use the forms:read and forms:write abilities for templates and submissions:read and submissions:write for the documents of a response. The workspace library, uploads and signing requests have their own permissions: see Permissions.
