Turn a Markdown Report into a Branded PDF in n8n
Recurring reports, changelogs, and digests deserve better than a plain text email. Feed Markdown into the Rendex Artifact node and get a branded PDF, a PNG, and a hosted share page back in a single call — ready to email or drop into Slack.
Last updated 2026-07-21
The Problem
You already generate the content — a weekly metrics digest, a changelog, an AI-written summary — but shipping it as a polished, on-brand document means wrestling with a PDF library, HTML-to-PDF quirks, and hosting the file somewhere. Inside an n8n worker that usually means bundling Puppeteer or accepting broken fonts and layout.
The Solution
Send the Markdown to Rendex Artifact with your brand header, accent color, and logo. It converts the Markdown to styled HTML, renders a print-ready PDF and a PNG, and hosts a share page — returning signed pdfUrl, pngUrl, and shareUrl. Attach the PDF to an email, or post the shareUrl to Slack. No template CSS to write, no file storage to manage.
How the Workflow Runs
Trigger
A schedule, webhook, or AI step supplies the report Markdown
Build report
Assemble the Markdown body and title (Set / Function / AI Agent)
Rendex Artifact
Render branded PDF + PNG + a hosted share page in one call
Share
Email the PDF, or post the shareUrl to Slack — links come back ready
Input → Rendered Output

Rendered by Rendex
What You Need
- A Rendex API key — the free tier gives 100 renders/month with no card
- n8n (cloud or self-hosted) with the Rendex community node installed
- A Markdown report body from any upstream node (Set, Function, or an AI Agent)
- Optional: an email or Slack node to deliver the finished links
What This Recipe Uses
One call, three outputs
A single Artifact request returns a branded PDF, a PNG, and a hosted share page — no separate render, upload, or hosting steps.
Branding without CSS
Pass a header, accent color, logo URL, and footer. Rendex styles the Markdown into an on-brand document — you never write layout code.
Hosted share link
The shareUrl is a hosted preview page you can drop straight into Slack or an email — no file to store, no attachment required.
Build It
{
"parameters": {
"resource": "artifact",
"operation": "create",
"content": "={{ $json.reportBody }}",
"inputFormat": "markdown",
"formats": ["pdf", "png"],
"artifactOptions": {
"header": "={{ $json.title }}",
"accentColor": "#EA580C",
"footer": "Confidential · your company"
}
},
"name": "Rendex — Create Artifact",
"type": "n8n-nodes-rendex.rendex",
"typeVersion": 1
}curl -X POST https://api.rendex.dev/v1/artifact \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"content": "# Weekly Growth Report\n\n- Signups up 18%\n- 3 new enterprise trials",
"inputFormat": "markdown",
"formats": ["pdf", "png"],
"branding": { "header": "Weekly Growth Report", "accentColor": "#EA580C" }
}'
# -> { "pdfUrl": "...", "pngUrl": "...", "shareUrl": "...", "expiresAt": "..." }100 free API calls/month — no credit card required. Get your API key and start building.
Reach for this workflow whenever a repeating job already produces text you want to deliver as a real document — a Monday growth digest, a per-customer summary, a release changelog. Because the input is plain Markdown, an upstream Set node or an AI Agent can write the body and you only pass a title and accent color for branding. Artifact does the layout, so your output looks designed without anyone touching CSS. Use the PDF when you want a file in the inbox or archive, and the shareUrl when you would rather send a short link recipients can open in the browser. Every format charges a single credit from the same pool as the rendering endpoints, and the whole flow runs on the free tier.