Actions80
- Add Attachment To PDF
- Add Barcode To PDF
- Add Form Fields To PDF
- Add HTML Header Footer
- Add Image Stamp To PDF
- Add Image Watermark To Image
- Add Margin To PDF
- Add Page Number To PDF
- Add Text Stamp To PDF
- Add Text Watermark To Image
- AI-Invoice Parser
- AI-Process Contract
- AI-Process HealthCard
- Classify Document
- Compress Image
- Compress PDF
- Convert HTML To PDF
- Convert Image Format
- Convert JSON To Excel
- Convert Markdown To PDF
- Convert PDF To Editable PDF Using OCR
- Convert PDF To Excel
- Convert PDF To PowerPoint
- Convert PDF To Word
- Convert To PDF
- Convert URL to PDF
- Convert VISIO
- Convert Word to PDF Form
- Create Images From PDF
- Create PDF/A
- Create Swiss QR Bill
- Crop Image
- Delete Blank Pages From PDF
- Delete Unwanted Pages From PDF
- Disable Tracking Changes In Word
- Enable Tracking Changes In Word
- Extract Attachment From PDF
- Extract Form Data From PDF
- Extract Pages From PDF
- Extract Resources
- Extract Table From PDF
- Extract Text By Expression
- Extract Text From Word
- Fill PDF Form
- Find And Replace Text
- Flip Image
- Flatten PDF
- Generate Barcode
- Generate Document Single
- Generate Documents Multiple
- Get Document From Pdf4me
- Get Image Metadata
- Get PDF Metadata
- Get Tracking Changes In Word
- Image Extract Text
- Linearize PDF
- Merge Multiple PDFs
- Overlay PDFs
- Parse Document
- Protect PDF
- Read Barcode From Image
- Read Barcode From PDF
- Read SwissQR Code
- Remove EXIF Tags From Image
- Repair PDF Document
- Replace Text With Image
- Replace Text With Image In Word
- Resize Image
- Rotate Document
- Rotate Image
- Rotate Image By EXIF Data
- Rotate PDF Page
- Sign PDF
- Split PDF By Barcode
- Split PDF By Swiss QR
- Split PDF By Text
- Split PDF Regular
- Unlock PDF
- Update Hyperlinks Annotation
- Upload File To PDF4me
Overview
This node operation converts Markdown content into a PDF document. It supports multiple input methods for the Markdown source, including binary data from a previous node, base64-encoded strings, raw Markdown code entered manually, or a URL pointing to a Markdown file. The output is a PDF file generated from the provided Markdown content.
This node is useful in scenarios where users want to automate the transformation of Markdown documentation, notes, or reports into PDF format for sharing, archiving, or printing. For example, it can be used to convert README files hosted online into PDFs, transform Markdown-based meeting notes into polished documents, or generate PDF reports from Markdown templates dynamically.
Properties
| Name | Meaning |
|---|---|
| Input Data Type | Choose how to provide the Markdown file to convert. Options: • Binary Data (Markdown file from previous node) • Base64 String (Markdown content already encoded in base64) • Markdown Code (raw Markdown text) • URL (link to Markdown file) |
| Input Binary Field | Name of the binary property containing the Markdown file (used only if Input Data Type is Binary Data). |
| Base64 Markdown Content | Provide the Markdown content already encoded in base64 format (used only if Input Data Type is Base64 String). |
| Markdown Code | Write raw Markdown code manually; this will be converted automatically to base64 (used only if Input Data Type is Markdown Code). |
| Markdown URL | URL to the Markdown file to convert (used only if Input Data Type is URL). |
| Output File Name | Name for the output PDF file. Default is markdown_to_pdf_output.pdf. |
| Document Name | Name of the source Markdown file with extension (e.g., sample.md). This is used as the original filename reference. |
| Output Binary Field Name | Name of the binary property to store the output PDF file. Default is data. |
| Advanced Options | Custom JSON profiles to adjust extra options for the API call. Users can specify additional parameters according to the external service's documentation (e.g., output format). |
Output
The node outputs a binary file representing the generated PDF document. The binary data is stored under the specified output binary field name (default data). The output JSON also includes metadata such as the filename.
The output structure typically looks like:
{
"json": {
"fileName": "my-markdown-converted.pdf"
},
"binary": {
"data": {
"data": "<binary PDF data>",
"mimeType": "application/pdf",
"fileName": "my-markdown-converted.pdf"
}
}
}
This allows downstream nodes to access the PDF file directly for further processing, storage, or sending via email.
Dependencies
- Requires an external PDF conversion API service that accepts Markdown input and returns PDF output.
- Needs an API key or authentication token configured in n8n credentials to authorize requests to the PDF conversion service.
- Network access to fetch Markdown files if using the URL input option.
Troubleshooting
Common Issues:
- Invalid or missing Markdown content: Ensure the input data is correctly provided according to the selected input type.
- Incorrect binary property name: When using binary data input, verify the binary field name matches the actual property containing the Markdown file.
- Network errors when using URL input: Confirm the URL is accessible and points to a valid Markdown file.
- API authentication failures: Check that the API key or credentials are properly set up in n8n.
Error Messages:
- "Invalid Markdown content" — The input Markdown could not be parsed or was empty. Verify the input data.
- "Failed to fetch Markdown file from URL" — The URL might be incorrect or inaccessible. Test the URL externally.
- "Authentication failed" — The API key or token is invalid or missing. Reconfigure credentials.
- "Conversion service unavailable" — The external API may be down or unreachable. Retry later or check service status.
Links and References
- PDF4me API Documentation — For details on custom profiles and advanced options.
- Markdown syntax guide — Useful for preparing Markdown content before conversion.
- n8n documentation on binary data handling — To understand how to work with binary inputs and outputs in workflows.