Add Form Field to PDF for Make

Q: How are Position X and Y coordinates measured in this module?

Position X is measured in points (72 points = 1 inch) from the left edge of the page. Position Y is measured in points from the bottom-left corner of the page - not from the top. To place a field 1 inch from the top on a standard A4 page (842 pt tall), set Y to approximately 770 (842 minus 72).

Q: How do I add multiple form fields in one Make scenario?

Each module call adds one field. To add multiple fields, chain Make's Iterator module with an array of field definitions, then connect each iteration to a separate Add Form Field to PDF module call, passing the Document Data output from each step into the next. Alternatively, use a loop structure to process fields one by one from a data store or JSON array.

Q: What is the correct Initial Value format for a checkbox?

For a checkbox field, set Initial Value to '1' or 'true' to pre-check the box by default. Leave it empty or set to '0' / 'false' for an unchecked default state. For text fields, Initial Value can be any string - it appears as placeholder text inside the field.

Q: How do I use the Document Data Base64 output in the next module?

Map the Document Data (Base64) output directly to the Document or Buffer input field of the next PDF4me module (e.g. Fill PDF Form) or to a storage module. For Google Drive Upload or Dropbox Upload, select the Data field and choose the Base64 mapping option. Make handles Base64-to-binary conversion automatically for most storage integrations.

What this module does

What this module does: The PDF4me Add Form Field to PDF module places interactive form fields - text inputs, checkboxes, radio buttons, dropdowns, and signature boxes - at precise X/Y coordinates on any page of a PDF inside your Make scenario. Feed it a PDF buffer from Google Drive, Dropbox, or an earlier module, define the field name, type, and position, and receive back a Base64-encoded fillable PDF ready to upload, email, or pass to the Fill PDF Form module. Use Make's Iterator to loop over a list of field definitions and add dozens of fields in a single scenario run - no manual PDF editor needed.

Authenticating Your API Request

Every PDF4me module in Make requires a valid API key. Connect PDF4me once in Make's connection manager - your key is stored securely and reused across all PDF4me modules in all your scenarios automatically.

Get your API Key

Important Facts You Should Not Miss

Position Y is measured from the bottom-left corner - not the top

The coordinate system uses PDF points (72 pt = 1 inch) with the origin at the bottom-left of the page. Position Y = 0 places the field at the very bottom edge. To position a field 1 inch from the top of a standard A4 page (842 pt tall), set Y to approximately 770 (842 − 72). Measure from the bottom up - the opposite of most design tools that measure from the top down.

Each module call adds exactly one field - use an Iterator for multiple fields

The module is designed to add one field per execution. To build a form with many fields, store your field definitions (name, type, X, Y, pages) in a Make data store or JSON array, then use an Iterator to feed each definition through a chain of Add Form Field modules. The Document Data output of each module becomes the Document input of the next - the form accumulates fields step by step.

Document Data output is Base64 - map it directly to the next module

The module returns the updated PDF as Base64-encoded data in the Document Data field. Map this directly to the Document input of the next PDF4me module (Fill PDF Form, Flatten PDF Form, etc.) or to a storage upload module (Google Drive, Dropbox, OneDrive). Make's native integrations handle Base64-to-binary conversion automatically - no intermediate decoding step is required.

Add Form Field to PDF module in Make – PDF4me — Add Form Field to PDF module configured inside a Make scenario

Parameters

⚠️ File Name, Document, Field Name, and Form Field Type are all required. Optional parameters control field placement, default value, and page targeting.

Parameter	Required	What it does	Example
File Name	Yes	Filename of the source PDF including the .pdf extension. Map from the previous module's file name output or enter a static name. Used for output identification and file format validation.	`application_form.pdf`
Document	Yes	The PDF file content as a binary buffer. Map from a Get File module (Google Drive, Dropbox, OneDrive, HTTP) or from the Document Data output of a previous PDF4me module. This is the base PDF that will receive the new form field.	`[Buffer from Google Drive Get File]`
Field Name	Yes	Unique identifier for the form field. Used for field recognition when filling the form programmatically or with the Fill PDF Form module. Use descriptive names without spaces (e.g. FirstName, EmailAddress, AgreeToTerms). Must be unique within the document.	`email_address`
Form Field Type	Yes	The type of interactive field to add. Text - single or multi-line text input. Checkbox - boolean tick box (true/false). Radio - radio button selection (group via shared Field Name). Dropdown - drop-down list selection. Signature - digital signature field.	`Text`
Initial Value	No	Default value pre-populated in the field. For Text fields: any string (appears as placeholder text). For Checkbox: "1" or "true" to pre-check, "0" or "false" for unchecked. Leave empty for blank fields that the recipient fills in.	`Enter your email address`
Position X	No	Horizontal position of the field from the left edge of the page, measured in PDF points (72 points = 1 inch). Default: 0 (left edge). Use a PDF ruler or coordinate tool to determine the exact X value for your layout.	`100`
Position Y	No	Vertical position of the field from the bottom-left corner of the page, measured in PDF points (72 points = 1 inch). Y = 0 is the bottom edge. For A4 (842 pt tall), Y = 770 places the field approximately 1 inch from the top.	`500`
Pages	No	Target pages for the field using 0-based indexing. Use comma-separated indices for specific pages (e.g. "0,2,4"), ranges with hyphen (e.g. "0-3" for first four pages), or leave empty to apply to all pages.	`0`

Output Fields

Output Field	Description
`Document Name`	Output PDF filename with the form field added
`Document Data`	The updated PDF with the new form field encoded as Base64 - map directly to the next module's Document input or a storage upload field

Quick Setup

Create or open a Make scenario and add a trigger or module that provides the source PDF - Google Drive Watch Files, Dropbox Watch Folder, or an HTTP module.
Add a Get File module (Google Drive, Dropbox, or OneDrive) to retrieve the binary PDF buffer if the trigger only returns metadata.
Add the PDF4me Add Form Field to PDF module - search PDF4me in the module list and select it.
Authenticate with your PDF4me API key if not already connected (enter it in the Make connection dialog).
Map File Name from the previous module's file name output.
Map Document from the previous module's file buffer or binary data output.
Enter Field Name - a unique, descriptive identifier (e.g. ApplicantName, SignatureField).
Select Form Field Type - Text, Checkbox, Radio, Dropdown, or Signature.
Set Position X and Y in PDF points for precise field placement.
Set Pages to target specific pages (0-based), or leave empty for all pages.
Connect a downstream module - map Document Data to a Fill PDF Form module, or upload to Google Drive/Dropbox.

Scenario Examples

Contract Template → Add Fields → Save to SharePointWhen a new contract type is approved, automatically add name, date, and signature fields to the template PDF and archive it in SharePoint.

Survey Question Array → Iterator → One Field per QuestionTurn a structured list of survey questions into a fillable PDF form by iterating over field definitions stored in a Make data store.

New Job Posting → Add Application Fields → Email Fillable Form to HRAutomatically generate a fillable job application PDF with name, email, phone, and experience fields every time a new position is posted.

Frequently Asked Questions

How are Position X and Y coordinates measured in this module?+

Coordinates use PDF points (72 pt = 1 inch) measured from the bottom-left corner of the page. Position X = 0 is the left edge; Position Y = 0 is the bottom edge. For a standard A4 page (842 pt tall), Y = 770 places a field approximately 1 inch from the top. Use a PDF coordinate tool or the PDF ruler in Acrobat to determine exact values before building your scenario.

How do I add multiple form fields in one Make scenario?+

Chain multiple Add Form Field to PDF modules in sequence. Map the Document Data output of each module to the Document input of the next - the form accumulates fields step by step. For a large number of fields, use Make's Iterator with a data store array of field definitions to process them programmatically without manually chaining hundreds of modules.

What is the correct Initial Value format for a checkbox?+

Set Initial Value to "1" or "true" to pre-check the box by default, or "0" or "false" for unchecked. For text fields, enter any string as placeholder text. Leave Initial Value empty for fields that the recipient fills in themselves - the field renders as a blank interactive element.

Does the Pages parameter use 0-based or 1-based indexing?+

Pages uses 0-based indexing - page 1 of the document is index 0, page 2 is index 1, and so on. Use comma-separated values for specific pages (e.g. "0,2,4"), ranges with hyphen (e.g. "0-3" for the first four pages), or leave empty to apply the field to every page in the document.

How do I use the Document Data Base64 output in the next module?+

Map the Document Data field directly to the Document or Buffer input of the next PDF4me module (e.g. Fill PDF Form, Flatten PDF Form). For Google Drive or Dropbox uploads, select the Data field and choose the Base64 mapping - Make handles the conversion to binary automatically. No intermediate decoding step is needed.

Fill PDF Form

Pre-populate the fields you just created with data from a Make data store, Airtable, Google Sheets, or any connected app - the natural next step after adding fields.

Flatten PDF Form

Lock filled form fields into non-editable content - use after filling to produce a tamper-proof PDF for distribution or archiving.

Read PDF Form Fields

Extract field names and values from an existing fillable PDF - use to verify fields were added correctly or to ingest submitted form data into your Make workflow.