Fill It, Sign It, Ship It. Make.com Automates the Whole Thing!

You have a fillable PDF form, data in JSON, and a signature image. Manual flow: fill the fields, place the signature, save, upload. Make plus PDF4me does it in one scenario: download the template, JSON, and signature from Dropbox (or Google Drive); run Fill a PDF Form and Sign PDF; then upload the signed document. No code. Ideal for contracts, agreements, and any form that must be filled and signed before delivery.

Why-Based Q&A​

---

What You'll Get​

Input: A fillable PDF form, a JSON file (or string) with field values, and a signature image file. Output: One PDF with all fields populated and the signature image placed (e.g. on the last page), ready to upload or pass to the next module.

---

What You Need​

---

The Scenario at a Glance​

1. Dropbox – Download a File (1) — Blank fillable PDF form.
2. Dropbox – Download a File (2) — JSON data for the form fields.
3. Dropbox – Download a File (3) — Signature image (PNG/JPG).
4. PDF4me – Fill a PDF Form — Template + JSON → filled PDF.
5. PDF4me – Sign PDF — Filled PDF + signature image → signed PDF.
6. Dropbox – Upload a File — Save the signed PDF to your folder.

Complete scenario overview​

Six steps: three Download modules, Fill a PDF Form, Sign PDF, Upload. The filled PDF from step 4 goes into Sign PDF; the signed PDF from step 5 goes into Upload.

---

Step 1: Download the PDF Form (Template)​

Scenario so far: First Download only.

1. Add Dropbox → Download a File.
2. Connection — Select your Dropbox connection.
3. Way of selecting files — Select a file (or Map for dynamic paths).
4. File — Path to your fillable PDF form, e.g. /Blog Data/Sign and fill pdf/sample_fill_form.pdf.
5. Run the module. The output (e.g. Data or File) is the template for Fill a PDF Form.

Download a File: PDF form​

Download the PDF form template. Map the output to Fill a PDF Form as Template.

---

Step 2: Download the JSON Data​

Scenario so far: Download PDF → Download JSON.

1. Add a second Dropbox → Download a File.
2. File — Path to your JSON file, e.g. /Blog Data/Sign and fill pdf/sample_fill_form_data.json.
3. Run the module. The file content (or parsed JSON) will be passed to Fill a PDF Form. Ensure keys match the PDF form field names.

Download a File: JSON data​

Download the JSON data. Keys must match form field names. Content is passed to Fill a PDF Form (Input type: Json).

---

Step 3: Download the Signature Image​

Scenario so far: Download PDF → Download JSON → Download signature.

1. Add a third Dropbox → Download a File.
2. File — Path to your signature image, e.g. /Blog Data/Sign and fill pdf/signature.png. PNG or JPG.
3. Run the module. The output will be passed to Sign PDF as Image File.

Download a File: Signature image​

Download the signature image. Output is passed to Sign PDF as Image File.

---

Step 4: Fill the PDF Form​

Scenario so far: Three Downloads → Fill a PDF Form.

1. Add PDF4me → Fill a PDF Form.
2. Template — Map the PDF file from the first Download (e.g. Data or File).
3. Template Name — e.g. sample_fill_form.pdf.
4. Select Input type — Json.
5. Data (or JSON input) — Map the content from the second Download. If Make returns a buffer, you may need to use a tool to get text or map the JSON from the Download output.
6. Run the module. Document (or Doc Data) = filled PDF. Pass this to Sign PDF as PDF File.

Fill a PDF Form​

Fill a PDF Form: template from step 1, JSON from step 2. Output is the filled PDF for Sign PDF.

---

Step 5: Sign the PDF​

Scenario so far: Three Downloads → Fill a PDF Form → Sign PDF.

1. Add PDF4me → Sign PDF.
2. PDF File — Map the filled PDF from Fill a PDF Form (e.g. Document or Doc Data).
3. PDF File Name — e.g. filled_form.pdf.
4. Image File — Map from the third Download (signature image).
5. Image Name — e.g. signature.png.
6. Pages — e.g. last (or first, all).
7. Horizontal Alignment / Vertical alignment — e.g. Right / Bottom.
8. Image Width in MM / Image Height in MM — e.g. 50 / 20.
9. Horizontal Margin in MM / Vertical Margin in MM — e.g. 15 / 15.
10. Transparency — e.g. 100.
11. Run the module. Doc Data (or Name) = signed PDF for Upload.

Sign PDF​

Sign PDF: filled PDF from step 4, signature image from step 3. Set page, alignment, size, and margins.

Sign PDF options (position and size)​

Fine-tune position (alignment, margins) and transparency. Output is the signed PDF buffer.

---

Step 6: Upload the Signed PDF​

Scenario so far: Three Downloads → Fill a PDF Form → Sign PDF → Upload.

1. Add Dropbox → Upload a File.
2. Connection — Same Dropbox connection.
3. Folder — e.g. /Blog Data/Sign and fill pdf/Output.
4. File — Map Doc Data (or the signed PDF buffer) from Sign PDF.
5. File Name — e.g. Sign_Fill_Make.pdf.
6. Run the scenario. The filled, signed PDF is saved to your folder.

Upload a File​

Upload the signed PDF from Sign PDF to your output folder.

---

Input and Output: What Goes In, What Comes Out​

Input: PDF form and JSON​

Blank fillable form: template for Fill a PDF Form. Field names must match the JSON keys.

JSON data: keys match form fields. Second Download provides this to Fill a PDF Form.

Output: Filled and signed PDF​

Filled and signed PDF: fields from JSON and signature image placed (e.g. last page). Saved via Upload.

---

Use Cases: When to Sign and Fill PDFs in Make​

---

Quick Reference: Key Settings​

For details: Fill a PDF Form, Sign PDF — Make.

---

Troubleshooting​

---

What's Next?​

---