Validate PDF/A in Make
What this module does
PDF4me — Validate a PDF/A document checks whether a PDF conforms to PDF/A (ISO 19005). It is read-only: it does not repair or rewrite the file. Use it after generation or before archive upload to gate scenarios on compliance—paired with routing, notifications, or conversion steps when validation fails.
Authenticating Your API Request
Every PDF4me module in Make needs a valid Connection. Create or select a connection that matches your PDF4me API credentials so scenarios can call validation securely.
Important Facts You Should Not Miss
File Content must be the actual PDF bytes from a prior module (e.g. Data from Dropbox Download). Mapping metadata or empty buffers leads to failed or meaningless checks.
Choose Map when filename and content come from dynamic previous-module output. Use a fixed source module (e.g. Dropbox) when you always read the same logical file shape.
If the document is not PDF/A, route to Create PDF/A or repair flows, then validate again—do not assume a pass after conversion without a second check.
Typical pattern: after a download step, map Filename from 1. File Name and File Content from 1. Data.
Key Features
- ISO 19005–oriented check for long-term preservation workflows
- Flexible input: prior Dropbox, cloud storage, or HTTP module output
- Map mode for dynamic bundles of name + binary from step 1
- Scenario-friendly: branch on validation output for approvals or retries
- Pairs with ZUGFeRD and conversion: validate after hybrid invoice or PDF/A creation
Parameters
Required: Connection, Filename, and File Content. Configure how the File is supplied (direct module vs Map) before saving the module.
| Parameter | Required | What it does | Example mapping |
|---|---|---|---|
| Connection | Yes | PDF4me API connection for the scenario. | Your PDF4me connection |
| File | Yes | How the PDF is chosen: e.g. Dropbox Download or Map. | Map |
| Filename | Yes | Original filename with extension for the PDF under test. | 1. File Name |
| File Content | Yes | Binary PDF body from the source module. | 1. Data |
Quick Setup
- Add PDF4me → Validate a PDF/A document.
- Select Connection (or add one via Add).
- Under File, pick Map if inputs come from a previous module’s output.
- Map Filename to the prior step’s file name field (e.g.
File Name). - Map File Content to the prior step’s binary field (often
Data). - Save and run the scenario; use filters or routers on the module output for pass/fail logic.
Workflow Examples
Workflow ExamplesOpens by default — common Make patterns around PDF/A validation.
- Dropbox — Download a File for incoming PDFs.
- Validate a PDF/A document with Map: name + Data from download.
- On success: upload to archive folder or update a record.
- On failure: route to Create PDF/A or notify the owner.
- Generate or merge the final customer-facing PDF.
- Run Validate a PDF/A document on the output buffer.
- Use results for compliance logging before ERP handoff.