AUTHOR
TipTap A4 authoring
Headings, lists, tables, images from the Media Library, colors, alignment, find & replace, and shared header/footer with {{page}} / {{pages}}.
WPsigner addon · Version 1.5.17
Document Builder is a TipTap A4 editor for NDAs, SOWs, and service agreements. Assign fields to signers while you write, preview the PDF, skip the drag-and-drop fields step, and continue the normal WPsigner send flow — all self-hosted.
Requires WPsigner Pro 3.0.2+. Complements — does not replace — the core upload-PDF workflow.
TipTap canvas with headers, footers, and page breaks
Generate and review before you send
Gravity Forms, WPForms, and Fluent Forms feeds
Drafts and PDFs stay on your WordPress server
Document → PDF → signature
Author HTML contracts in WordPress, convert them to PDF with WPsigner’s engine, and hand off to the same send, remind, and audit tools you already use.
AUTHOR
Headings, lists, tables, images from the Media Library, colors, alignment, find & replace, and shared header/footer with {{page}} / {{pages}}.
ASSIGN
Insert Signature, Initials, Text, Date, Name, Email, Checkbox, Dropdown, Attachment, and more — assigned to each signer as you draft.
SEND
When you continue, Document Builder syncs placeholders into WPsigner fields and jumps straight to Review (idb_ready).
One clear workflow
Everything in the builder is aimed at one outcome: a clean PDF and a WPsigner send flow your team already trusts.
Convert the draft with TCPDF/FPDI from WPsigner, preview before send, and download the preview PDF.
Save, load, export, and import HTML templates — including header/footer and signers — also listed in the WPsigner Templates hub.
Choose whether all signers act at once or one after another before you leave the builder.
Choose the right source
Use Document Builder when you want to author the contract in WordPress. Use core PDF templates when you already have a designed PDF.
Editing or field-mapping an existing uploaded PDF
Native DOCX import (HTML import/export and rich paste are supported)
Google Docs sync (A4 UI only — not a live Docs connection)
Multi-signer mapping from a single form submission (feeds use one signer from the form)
Running a Document Builder feed and a core PDF-template feed on the same form at once
Re-editing content after a document leaves draft status
Document Builder
Keep drafting, field placement, PDF preview, and send on the same self-hosted WordPress stack your agency already runs.
Signature, Initials, Text, Number, Date, Name, Email, Phone, Company, VAT, Title, Checkbox, Checkbox Group, Radio, Dropdown, Text Area, Attachment — with required/optional controls where applicable.
Optional mapping names on fields so Gravity Forms, WPForms, and Fluent Forms can prefill values from submissions.
Re-open Document Builder content while the WPsigner document is still in draft — then continue to send when ready.
Start from WPsigner → Document Builder or New Document → Document Builder alongside the upload-PDF path.
On form submit: create from a saved builder template, prefill, mark sent, then open the signing page or email the request.
Large HTML or many embedded images can hit WordPress post size limits — keep drafts lean for reliable PDF generation.
3-step wizard
Install alongside WPsigner Pro, then follow the three-step wizard.
Install the addon ZIP with WPsigner 3.0.2+ active. Open WPsigner → Document Builder or New Document → Document Builder.
Enter valid emails, set parallel or sequential signing, then continue to the document step.
Write the agreement, insert fields per signer, optionally load a template and set header/footer.
Generate a preview, download if needed, then continue to WPsigner Review — Fields drag-and-drop is skipped.
Finish the normal WPsigner review and send flow. Save as a template anytime for reuse or form feeds.
Form submission → contract
Save a Document Builder template first, then connect a feed. On submit, WPsigner creates the document, prefills mapped fields, and either opens signing or emails the request.
Document Builder feed with signer name/email mapping and confirmation redirect into the signing flow.
Same template + mapping model: create from builder template, prefill, send or open signing.
Parity with WPForms/Gravity — one builder feed per form, delivery open or email.
You cannot enable a Document Builder feed and a core PDF-template feed on the same form at the same time.
Before you install
Check these before you roll Document Builder out to your team.
Know before you draft
Builder authors HTML and generates PDF — it does not edit an uploaded PDF layout.
Form feeds map one signer from the submission (name + email), not a full multi-signer roster from the form.
Re-edit of builder content is available only while the document remains a draft.
Very large HTML or many data-URI images can fail PDF generation due to WordPress size limits.
Author once · send with WPsigner
Keep drafting, field placement, PDF preview, and send on the same self-hosted WordPress stack your agency already runs.
WPsigner Addon
Install Document Builder from your account addons, or browse the full addon catalog.
Clear answers
Check these before you roll Document Builder out to your team.
An official addon that lets you write contracts in a TipTap A4 editor inside WordPress, convert them to PDF, assign signer fields while drafting, and continue the normal WPsigner send flow.
Yes. Document Builder requires WPsigner 3.0.2 or newer. Signing, reminders, and audit trails remain part of the core product.
No. Core WPsigner still supports uploading a PDF and placing fields. Document Builder is for authoring the document as HTML and generating the PDF from that draft.
No. Smart Signing Forms are public intake forms. Document Builder is an admin authoring tool for full contracts you send through WPsigner.
Gravity Forms, WPForms, and Fluent Forms via Document Builder feeds. Save a builder template first, map signer name/email and fields, then choose open-signing or email delivery on submit.
No. A form can use either a Document Builder feed or a core PDF-template feed — not both at once.
Builder content can be re-edited while the WPsigner document is still in draft. After it leaves draft, use normal WPsigner document handling.
On your WordPress server with the rest of your WPsigner data. Processing is self-hosted by default.