Turn Markdown into a Branded PDF in Activepieces
Drop the native Rendex Render to Image piece into an Activepieces flow, set the source to Markdown, and turn a doc, changelog, or approved article into a polished PDF — GitHub-flavored styling baked in, no CSS to write. The result comes back as a file the next step can attach, upload, or email.
Last updated 2026-07-15
The Problem
Plenty of content lives as Markdown — release notes, internal docs, approved articles, generated reports — but Markdown isn't what you hand to a customer or file for the record; that needs a PDF. Converting it in a no-code flow usually means either an HTML step where you hand-write CSS to make the Markdown look decent, or a headless-browser/pandoc service you have to host. Both are more work than the task deserves, and neither is something an Activepieces builder wants to own.
The Solution
The native Rendex piece has a Render to Image action with a Source dropdown — pick Markdown, set Format to PDF, and pass your Markdown string. Rendex renders it with GitHub-flavored styling (headings, tables, code blocks, task lists) into a clean, branded PDF and returns it as a proper Activepieces file, so the next piece can email it, upload it to Drive or S3, or post it to Slack — no CSS, no browser, no base64 handling. And because Activepieces exposes every piece as an MCP tool, the same Render to Image action is callable by your AI agents, so the human flow and the agent share one rendering step.
How the Workflow Runs
Markdown ready
A trigger surfaces the Markdown — a Git commit, a form field, an approved record, or a schedule.
Render to Image piece
The native Rendex piece renders the Markdown to a PDF and returns it as an Activepieces file.
Attach / upload
Pipe the file into any piece — email it, upload to Drive/S3, or post it to Slack.
Input → Rendered Output
Rendered by Rendex
What You Need
- A Rendex API key — the free tier includes 100 renders/month with no card required.
- An Activepieces account (cloud or self-hosted) with the Rendex piece added and authenticated with your key.
- A Markdown source in the flow — from a Git piece, a form field, a database record, an LLM step, or a Text piece.
- A destination piece: email, Google Drive / S3 upload, or a Slack post.
What This Recipe Uses
Markdown in, PDF out
Set the Render to Image source to Markdown and format to PDF. Rendex applies GitHub-flavored styling — headings, tables, code blocks, task lists — so the document looks right with zero CSS.
Returns a real Activepieces file
The native piece hands back a proper file (not base64), so the next step attaches, uploads, or posts it directly — no decoding or Custom Code step in between.
Callable as an MCP tool
Activepieces exposes every piece as an MCP tool, so the same Render to Image action is available to your AI agents — one rendering step serves both the human flow and the agent.
Native piece, no code
Authenticate once and the Render to Image step drops into any flow — no HTTP module to configure, no headless browser to run, no CSS to maintain.
Build It
# Activepieces — step config (no code)
Trigger: New release note approved # or Git commit, form, schedule
Step: Rendex — Render to Image
Source: Markdown
Markdown:
# v1.6.1 — Watch dry-run
- New: Test a watch before you commit
- Fixed: flag-on transition baseline
Format: PDF
Next: Gmail — Send Email
Attachment = {{ Rendex: file }}# The Render to Image piece posts this under the hood (Source = Markdown).
curl -X POST https://api.rendex.dev/v1/screenshot \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
--output release-notes.pdf \
-d '{
"markdown": "# v1.6.1 — Watch dry-run\n\n- New: Test a watch before you commit\n- Fixed: flag-on transition baseline",
"format": "pdf"
}'100 free API calls/month — no credit card required. Get your API key and start building.
Reach for this when Markdown needs to become a real document inside a no-code flow — publishing release notes as a downloadable PDF, turning an approved article into a client-ready file, archiving a generated report, or emailing a policy doc for signature. Markdown is the easiest format to produce and the worst to hand over, and the usual fixes (hand-authored CSS on an HTML step, or a self-hosted pandoc/browser) are exactly the overhead Activepieces is meant to remove. The native Render to Image piece closes the gap: choose Markdown as the source, PDF as the format, and Rendex applies GitHub-flavored styling so tables, code blocks, and task lists look right without a line of CSS. The output is a first-class Activepieces file, so attaching, uploading, or posting it is just the next step — no encoding in between. The bonus is reach: because Activepieces surfaces every piece as an MCP tool, the same action your flow uses is one an AI agent can call, so you build the rendering step once and both consume it. It runs on the free 100 renders a month.