Creating a template from a fillable PDF
If you already have a fillable PDF form, DocuPotion can read the form fields straight out of your PDF and turn the whole thing into a reusable template, ready to generate filled copies on demand. This is the fastest route when you have an established form (an application, an intake sheet, a government or industry document) that you fill in over and over by hand.
This guide explains what kind of PDF works, how the upload turns into a template, and how the form's fields are mapped to the merge fields you will send data to.
- Which PDFs work, and which do not
- Uploading your fillable PDF
- How your form fields become merge fields
- How grouped fields are handled
- Reviewing the detected fields
- Sending real data into the template
Which PDFs work, and which do not
This route works with fillable PDFs: PDF documents that contain real, interactive form fields (the kind you can click into and type in directly inside a PDF reader). These embedded fields are what DocuPotion reads to build your template.
A few kinds of file will not work on this route:
- Flat or scanned PDFs. If the document is just a picture of a form with no clickable fields (often the result of scanning a paper form), there are no fields to read. DocuPotion will tell you it found no fillable fields.
- Password-protected or corrupted files. If the file cannot be opened and read, it will be declined with a message saying so.
Not sure if your PDF is fillable?
Open it in a PDF reader and try clicking where you would type. If a cursor appears in a box and you can type into it, the form has real fields and will work. If clicking does nothing, it is likely a flat or scanned document.
Uploading your fillable PDF
In the template section of your DocuPotion dashboard, click on the New Template button and choose the Upload a fillable PDF option:
Drop your fillable PDF into the upload area. Only fillable PDF files are accepted on this route. It may take a minute or two for DocuPotion to analyse your PDF for fillable PDFs.
Once the analysis is complete, you'll be brought to the DocuPotion template editor.
How your form fields become merge fields
Every interactive field inside your PDF has an internal name. Sometimes those names are clear, like full_name or date_of_birth . Often they are not, with names like Text1 , untitled_4 , or topmostSubform[0].Page1[0].f1_07[0].
DocuPotion reads each of these form fields and maps it to a merge field: the named placeholder your template will fill with data. Wherever possible, cryptic field names are turned into meaningful ones based on the label printed next to the field on the form, so an unhelpful Text1 sitting beside a "Company name" label becomes a sensible merge field like company_name .
The result is a mapping from each original PDF form field to a clear merge field name. That merge field name is what matters to you from here on: it is the name you will use when you send real data into the template. Just as with any template, the merge field names are the contract between your data and the document.
The mapping is to your original form's fields
Because the template is built on top of your actual PDF, each merge field stays linked to the matching field in the original document. When you supply data, it lands in exactly the right place on the page, preserving the original layout.
How grouped fields are handled
Paper-style forms often split a single piece of information across several boxes. DocuPotion recognises these patterns and groups them under one merge field rather than creating a separate field for every box:
- Character boxes. A row of single-character boxes (common for things like a company number, reference code, or postcode, where each character gets its own square) is treated as one field. You supply the whole value once, and it is distributed across the boxes.
- Stacked text lines. A multi-line area made of several stacked boxes under a single label (an address block, for example) is grouped into one field, so you provide the value once rather than line by line.
This grouping keeps your field list short and sensible. The number of merge fields you end up with will usually be smaller than the raw number of boxes on the form, and that is intentional.
Reviewing the detected fields
Before you rely on the template, take a moment to review the detected field list against the original form:
- Coverage. Are all the fields you actually fill in represented? A field that was missed usually means the box was not a real interactive field in the source PDF.
- Names. Are the merge field names clear enough for you and any connected systems to recognise? These are the names you will map your data to.
- Grouping. Did anything that should be one value get split, or anything that should be separate get merged? Character boxes and stacked lines are expected to be grouped (see previous section).
Once you are happy, fill the template with a set of sample values in the Data tab and generate a sample PDF by clicking on the Download Sample button.
Testing with realistic data now is the surest way to catch a field that is mapped to the wrong spot before you generate documents in bulk.
Sending real data into the template
To generate finished documents, you send your live data using the merge field names from the mapping, and DocuPotion fills the form and produces a completed PDF document for each record.
You can connect your data via one of our integrations or using our REST API. In each case, line up your data's field names with the merge field names DocuPotion detected.