Getting Started

Application Overview

PDFFILLR automates PDF form filling end-to-end. You choose how data arrives (through conversation, a cloud link, or a local file) and the platform handles everything else: field detection, data mapping, and document delivery.

3 Input Modes4-Stage PipelinePDF + JSON Output
What you will learn
What PDFFILLR is and the problems it solves
The three-step workflow every session follows
The three input modes and when to use each
The four internal pipeline stages
Key platform features and guarantees
How to choose the right mode for your workflow

1. What is PDFFILLR?

PDFFILLR is a document automation platform that takes a blank, fillable PDF and produces a completed, filled version automatically. Think of it as a pipeline: you provide a PDF and a data source, and a filled document comes out the other side with every form field populated correctly.

It is designed for workflows where the same type of form needs to be filled repeatedly: investor onboarding packets, KYC forms, subscription agreements, regulatory filings. Instead of having someone manually type the same information into a PDF every time, PDFFILLR does it in seconds and never makes a typo.

Every PDFFILLR session returns two things: the completed PDF ready to download or share, and a JSON object containing all the field values that were collected. The JSON is useful if you want to store the data in a database or pass it to another system alongside the document.

You always get both outputs
Every session returns a filled PDF and a structured JSON payload, regardless of which input mode you use. You can use just the PDF, just the JSON, or both.
Example JSON payload
session_response.json
{
  "status": "completed",
  "session_id": "sess_8fK2mNpQ",
  "fields_filled": 14,
  "pdf_url": "/files/out/KYC_8fK2mNpQ.pdf",
  "data": {
    "full_name": "Jane Doe",
    "date_of_birth": "1990-04-15",
    "nationality": "US",
    "risk_profile": "moderate",
    "signature_date": "2025-01-15"
  }
}

2. How It Works

Every PDFFILLR session follows the same three-step workflow, regardless of which input mode you choose. The only thing that changes between modes is how your data is collected in step two.

01
Submit a PDF→ Document received
Upload any fillable AcroForm PDF (a subscription form, KYC document, or LP agreement) through the dashboard, a cloud URL, or a local file upload.Supports standard AcroForm PDF documents.
02
Data is collected and mapped→ Field-value pairs ready
Depending on the mode you chose, an AI chatbot gathers information through conversation, or the platform reads and structures data from your uploaded file. Every value is validated before being matched to a PDF field.This is the step where you pick your input mode.
03
Filled document is delivered→ Filled PDF + JSON payload
The completed PDF is written and made available for immediate download. You also receive a structured JSON payload of all collected field values, useful for databases, CRMs, or downstream workflows.Both PDF and JSON are returned every time.
Tip
Step two is where the three input modes differ. Read the PDF Filling Modes section below to pick the right mode before you start.

3. Key Features

These are the three properties that make PDFFILLR reliable enough to use in production, not just for demos or one-off tests.

Precision Field MappingEvery form field is read and catalogued before any data is written. Each collected value is routed to the exact field by name and type: text to text boxes, booleans to checkboxes, enums to dropdowns.
No missed fields. No misplaced values.
Single-Pass ProcessingExtraction, mapping, and writing run as one optimised pass with no intermediate files or round trips. A 50-field subscription form that once took hours of manual entry completes in seconds.
From upload to filled PDF in seconds.
Secure by DefaultAll document data is encrypted in transit and at rest. Files are processed in isolated, ephemeral containers and discarded immediately after the session ends, unless you configure persistent storage.
Your documents never linger on our servers.

4. PDF Filling Modes

Before filling a PDF, you choose an input mode. The mode tells PDFFILLR where your data is coming from and how to collect it. Everything after that point, including field detection, mapping, and writing, runs the same way regardless of mode.

AI
Conversational AI
Use whenA user is filling the form in real time through your app.

An AI-powered conversation guides the user step-by-step through the form. The chatbot asks questions in plain language, validates each answer on the spot, prompts for corrections if needed, and fills the PDF automatically once all fields are complete.

  • No manual form entry, data collected through natural language conversation
  • Real-time validation: asks again if an answer fails field constraints
  • Ideal for KYC, investor onboarding, and subscription agreements
URL Upload
Cloud Source
Use whenYour source data is already stored in Google Drive or Dropbox.

Paste a document link from Google Drive or Dropbox. PDFFILLR fetches the remote file, extracts structured data from its contents, and maps it directly to the target PDF fields. No intermediate download required.

  • Works with Google Drive and Dropbox document links
  • Supports OAuth token passthrough for private or restricted files
  • Entire flow runs from the URL, no local file required
Local File Upload
Direct Upload
Use whenYou have a PDF file ready on your device.

Upload a PDF directly from your machine. PDFFILLR reads the file, extracts the relevant field data, and uses it to populate the target form. The filled document is available for download the moment processing completes.

  • Accepts PDF files only
  • Data is extracted and mapped to form fields in a single pass
  • Filled PDF is available for immediate download on completion

Which mode should I use?

Your situationRecommended mode
A user needs to fill a form by answering questionsAI
Your source data is a document in Google Drive or DropboxURL Upload
You have a local PDF file on your device to uploadLocal File Upload

5. Filling Process

Once you submit a PDF and your data, PDFFILLR runs four internal stages to produce the filled document. These stages run automatically; you do not trigger or configure them manually.

This runs automatically
You do not need to understand these stages to use PDFFILLR. This section is for developers who want to know what is happening under the hood, for example when debugging a field that is not filling as expected.
01ExtractionRead the PDF and catalogue its structure.

PDFFILLR scans the uploaded PDF and builds a field schema: every field's name, data type (text, checkbox, radio, dropdown, date), and position on the page. This schema is the map that all later stages use to place values correctly.

OutputField schema
02MapperMatch incoming data to the right fields.

Each value in the collected payload is paired with a field in the schema using name-based lookup or your config-file mapping rules. Type coercion is automatic: booleans become checkboxes, strings become dropdown selections.

OutputValue-to-field binding map
03EmbeddedWrite values into the PDF field layer.

Matched values are written into the PDF's AcroForm field layer. Fonts, layout, and visual formatting are untouched; only the field values change. No visual artefacts are introduced to the document.

OutputPre-filled field layer
04FillingProduce and deliver the final output file.

All embedded values are committed, the form is optionally flattened to prevent further editing, and the output PDF is generated. The document is returned for download or written to your configured storage destination.

OutputCompleted PDF
Ready to try it?
Head to the TypeScript SDK guide to start integrating PDFFILLR into your application.

Next steps

Was this page helpful?