Create PDF/A in n8n

Create PDF/A is an n8n module by PDF4me that converts a standard PDF into an ISO-compliant PDF/A archival file. Send a PDF as binary data, Base64, or a URL, pick a compliance level from PDF/A-1b through PDF/A-3a, and receive a validated archival PDF ready for long-term storage.

What this node does

PDF4me: Create PDF/A takes a standard PDF and converts it into a PDF/A archival document in one n8n step. Choose from eight compliance levels covering basic conformance (PDF/A-1b, 2b, 3b), accessibility-tagged conformance (PDF/A-1a, 2a, 3a), and Unicode-mapped conformance (PDF/A-2u, 3u). Returns a validated PDF/A file with embedded fonts and preserved metadata, ideal for legal archives, government submissions, healthcare records, and financial retention workflows that require ISO 19005 compliance.

Related Blog Posts

No blog post yet for this feature — coming soon.

In the meantime, browse the PDF4me blog for tutorials and workflows across every platform.

Visit the blog →

Authenticating Your API Request

Every PDF4me node in n8n requires a valid Credential to connect with. Create or select one that holds your PDF4me API key so the workflow can authenticate PDF/A conversion requests securely.

Get your API Key

Important Facts You Should Not Miss

Allow Upgrade and Allow Downgrade control fallback

These optional Advanced Options let PDF4me apply a higher or lower compliance level than requested instead of failing outright when the exact level cannot be met. Both live under Advanced Options and only appear once you click Add Option.

Document Name is for tracking, not the output filename

Document Name references the source PDF for processing and audit trails. The actual returned filename is controlled separately by Output File Name.

Only the PDF/A-3 family allows embedded files

PDF/A-3b, PDF/A-3u, and PDF/A-3a are the only compliance levels that let you embed additional files (XML, CSV, CAD, Word) inside the archival PDF. PDF/A-1 and PDF/A-2 levels do not support embedding.

Full node panel: source PDF via Binary Data, PDF/A-1b compliance level selected

Parameters

Required in the n8n UI: Input Data Type, Document Name, and PDF/A Compliance. Output File Name (default converted_pdfa.pdf) and Binary Output Property Name (default data) are optional convenience fields, not sent to the PDF4me REST API directly. Allow Upgrade, Allow Downgrade, and Custom Profiles live under the optional Advanced Options panel. Conditional template fields (Input Binary Field, Base64 Document Content, File URL) appear only when their matching Input Data Type is chosen.

Parameter	Required	What it does	Example
Input Data Type	Required	How the source PDF enters the node. Binary Data reads from a previous node (default, most common). Base64 String accepts an encoded PDF. URL downloads the PDF from a public link.	Binary Data
Input Binary Field	Conditional	Name of the binary property on the incoming n8n item that holds the PDF. Required when Input Data Type is Binary Data. Defaults to data.	data
Base64 Document Content	Conditional	Base64-encoded PDF content. Required when Input Data Type is Base64 String.	JVBERi0xLjQK...
File URL	Conditional	Publicly reachable URL to the PDF file. Required when Input Data Type is URL.	https://abc.com/sample.pdf
Output File Name	Optional	Filename of the converted PDF/A file returned by the node. Default is converted_pdfa.pdf. Not sent to the underlying REST API, applied by the n8n node.	converted_pdfa.pdf
Binary Output Property Name	Optional	Name of the binary property the output item exposes. Default is data. Use a different name when a downstream node expects it.	data
Document Name	Required	Name of the source PDF, used for reference and tracking. Maps to the REST API's required File Name field.	document.pdf
PDF/A Compliance	Required	The target archival compliance level. Options: PDF/A-1b, PDF/A-1a, PDF/A-2b, PDF/A-2u, PDF/A-2a, PDF/A-3b, PDF/A-3u, PDF/A-3a.	PDF/A-1b (Level B Basic)
Allow Upgrade	Optional	Advanced Option. When true, PDF4me may apply a higher compliance level than requested if the source PDF already qualifies.	true
Allow Downgrade	Optional	Advanced Option. When true, PDF4me falls back to a compatible lower compliance level instead of failing if the exact level cannot be met.	false
Custom Profiles	Optional	Advanced Option. JSON-like string for additional conversion settings, for specialized requirements only.	{"outputDataFormat":"base64","preserveMetadata":true}

PDF/A Compliance Levels

The eight compliance options group into three families depending on how strict the archival requirement is.

PDF/A-1b, PDF/A-2b, PDF/A-3bBasic conformance

Reliable reproduction of the document's visual appearance. PDF/A-1b targets PDF up to 1.4, PDF/A-2b adds transparency and digital signature support on PDF 1.7, PDF/A-3b additionally allows embedding files like XML, CSV, CAD, or Word documents.

PDF/A-1a, PDF/A-2a, PDF/A-3aAccessible conformance

Basic conformance plus document structure, text-span tagging, and language specification for screen-reader compatibility. Required when the archived document must meet accessibility standards.

PDF/A-2u, PDF/A-3uUnicode-mapped conformance

Basic conformance with all text mapped to Unicode for reliable international character support and cross-platform text extraction.

What Fields Does the Output Include?

Field	Type	What it contains
fileName	String	Filename of the generated PDF/A file, set from Output File Name (default converted_pdfa.pdf).
mimeType	String	MIME type of the generated file, application/pdf.
fileSize	Number	Size of the generated PDF/A file in bytes.
success	Boolean	True when the conversion completed successfully. Use to route error-handling branches.
inputDataType	String	Which input mode was used: binary, base64, or url.
sourceFileName	String	The original Document Name that was processed, kept for audit trails.
pdfaCompliance	String	The compliance level that was applied during conversion.
isPdfaCompliant	Boolean	Whether the generated PDF meets the requested PDF/A compliance standard.
complianceLevel	String	Detail on the specific compliance level achieved.
Binary (data)	Binary	The generated PDF/A file under Binary Output Property Name (default data). Pass into Write Binary File, Email, or any storage upload.

How Do I Set Up Create PDF/A in n8n?

1. Add PDF4me to your n8n workflow and set Action to Create PDF/A.
2. In Credential to connect with, select your PDF4me credential or click Create New Credential and paste your API key.
3. Set Input Data Type to Binary Data (default), Base64 String, or URL and fill the matching field.
4. Set Document Name to the source PDF's name for reference.
5. Optionally change Output File Name from the default converted_pdfa.pdf and Binary Output Property Name from the default data.
6. Choose a PDF/A Compliance level based on whether you need basic, accessible, or Unicode-mapped conformance.
7. Optionally click Add Option under Advanced Options to set Allow Upgrade, Allow Downgrade, or Custom Profiles.
8. Execute the node and route the archival PDF into Write Binary File, Email, or cloud storage.

Typical Setups

Workflow ExamplesCommon n8n workflow patterns using Create PDF/A.

Signed contract archival to compliance storage

1. A Google Drive Download node pulls a signed contract PDF (Binary Data, property data).
2. PDF4me Create PDF/A runs with Input Data Type Binary Data and PDF/A Compliance set to PDF/A-2b.
3. A Write Binary File node saves the archival PDF to a compliance-archive folder using $json.fileName.

Accessible government form submission

1. A webhook receives a completed regulatory form as a base64-encoded PDF.
2. PDF4me Create PDF/A is configured with Input Data Type Base64 String and PDF/A Compliance set to PDF/A-1a for screen-reader accessibility.
3. The archival PDF is uploaded to a SharePoint document library for submission.

Financial record retention with embedded audit files

1. An HTTP Request node downloads a generated invoice PDF from a public URL.
2. PDF4me Create PDF/A runs with Input Data Type URL and PDF/A Compliance set to PDF/A-3b, which allows embedding a CSV audit trail alongside the PDF.
3. The result is stored to a long-term financial-records archive.

Patient record preservation after document generation

1. PDF4me Generate Document (Single) produces a patient discharge summary PDF from a template.
2. The output is chained directly into PDF4me Create PDF/A with PDF/A Compliance set to PDF/A-2a for HIPAA-aligned long-term preservation.
3. An email node sends the archival PDF to the records department.

Practical Tips

Allow Downgrade avoids hard failures

If the source PDF cannot fully meet the requested compliance level, enabling Allow Downgrade lets PDF4me fall back to a compatible lower level instead of erroring out the workflow.

Accessible levels need real document structure

PDF/A-1a, PDF/A-2a, and PDF/A-3a require tagged content and language specification. A scanned image-only PDF with no text layer will not gain accessibility from conversion alone.

Document Name is not the output filename

Document Name is a tracking reference for the source file. Set Output File Name separately to control what the returned PDF/A file is called.

Default to Basic unless you need more

PDF/A-1b, PDF/A-2b, or PDF/A-3b cover most archival requirements. Reach for the accessible (a) or Unicode (u) variants only when the recipient or regulation specifically requires them.

Only PDF/A-3 embeds extra files

If your workflow needs to bundle source data (XML, CSV, CAD, Word) inside the archival PDF, you must pick PDF/A-3b, PDF/A-3u, or PDF/A-3a. The 1 and 2 families do not support embedding.

Advanced Options are optional

Leave Allow Upgrade, Allow Downgrade, and Custom Profiles unset unless you have a specific reason to override the default conversion behavior.

Cheat Sheet

Field	Value
Action	Create PDF/A
Input Data Type	Binary Data
Input Binary Field	data
Document Name	document.pdf
Output File Name	converted_pdfa.pdf
Binary Output Property Name	data
PDF/A Compliance	PDF/A-1b (Level B Basic)
Allow Upgrade	true
Allow Downgrade	false
Credentials	PDF4me API credential

Frequently Asked Questions

What is PDF/A?+

PDF/A is an ISO-standardized (ISO 19005) subset of PDF built for long-term archival. It requires embedded fonts, restricted color spaces, and preserved metadata so the document renders identically decades from now, regardless of the software used to open it.

How do I convert a PDF to PDF/A in n8n?+

Add the PDF4me node, set Action to Create PDF/A, provide the source PDF as Binary Data, Base64, or URL, set Document Name, choose a PDF/A Compliance level, and execute. The node returns the converted PDF/A file plus conversion metadata such as isPdfaCompliant.

How do I save a PDF in PDF/A format?+

Manually, most PDF editors offer a Save As or Export to PDF/A option under compliance or accessibility settings. In an automated n8n workflow, PDF4me Create PDF/A performs this conversion programmatically for every PDF that passes through the node, no manual export step needed.

What is the difference between PDF/A-1b, PDF/A-2b, and PDF/A-3b?+

PDF/A-1b is the basic conformance level supporting PDF versions up to 1.4. PDF/A-2b builds on PDF 1.7 and adds support for transparency, image compression, and digital signatures. PDF/A-3b adds the ability to embed additional files such as XML, CSV, CAD, or Word documents inside the archival PDF.

What do Allow Upgrade and Allow Downgrade control?+

Allow Upgrade lets PDF4me apply a higher compliance level than requested when the source PDF already qualifies. Allow Downgrade lets PDF4me fall back to a compatible lower level when the exact requested level cannot be achieved, instead of failing the conversion.

Do I need to tag my PDF before requesting an accessible compliance level?+

PDF/A-1a, PDF/A-2a, and PDF/A-3a require structured, tagged content to be meaningful for screen readers. A scanned image-only PDF with no underlying text layer will convert but will not gain real accessibility benefits without OCR and tagging first.

Related Actions

Convert to PDF

Convert Word, Excel, or image files to PDF first if the source document is not already a PDF, then chain into Create PDF/A for archival.

Flatten PDF

Flatten form fields and annotations into static content before archiving, so the PDF/A output is a locked visual record.

Linearize PDF

Optimize a PDF for fast web viewing. Use this for distribution copies, separate from the archival PDF/A master file.

Same Task on Other Platforms

Create PDF/A in Make

Same conversion as a Make module, visual scenarios with cloud-storage triggers wired to the same compliance levels.

Create PDF/A in Zapier

Trigger PDF/A conversion from any of 6,000+ SaaS apps and webhooks through Zapier.

Create PDF/A in Power Automate

Microsoft 365 flows with SharePoint, Outlook, Teams, and Dataverse integrations.

Create PDF/A REST API

The raw POST /api/v2/PdfA endpoint, for custom backend code or Postman testing.

Use Cases

Government and Regulatory Compliance

• Convert documents to PDF/A format for government submissions, regulatory filings, and official documentation that requires long-term archival compliance and legal validity
• Process legal documents, contracts, and official records by converting them to PDF/A format for court submissions, legal proceedings, and regulatory compliance
• Transform historical documents, archives, and official records to PDF/A format for long-term preservation, digital archiving, and compliance with archival standards

Financial and Banking Documentation

• Convert financial statements, audit reports, and banking documents to PDF/A format for regulatory compliance, financial reporting, and long-term record keeping
• Process tax documents, compliance reports, and financial records by converting them to PDF/A format for regulatory submissions, audit trails, and financial compliance
• Transform insurance documents, claims records, and financial contracts to PDF/A format for long-term storage, regulatory compliance, and legal documentation

Healthcare and Medical Records

• Convert medical records, patient files, and healthcare documentation to PDF/A format for HIPAA compliance, medical record keeping, and long-term patient data preservation
• Process clinical reports, laboratory results, and medical imaging documents by converting them to PDF/A format for medical record management, compliance, and archival
• Transform pharmaceutical documentation, clinical trial records, and medical research data to PDF/A format for regulatory compliance, research documentation, and long-term preservation

Get Help

n8n Integration Guiden8n SampleGetting Started