Skip to main content
Because Blink PDF exposes a plain REST endpoint, it works out of the box with every major no-code and low-code automation platform. You don’t need a dedicated integration or plugin — any tool that can make an HTTP POST request can call /v1/render and receive a PDF. This guide walks you through the exact configuration for n8n, Make (formerly Integromat), and Zapier.

​
How the Integration Works

Every automation platform listed here has a native HTTP node. You configure it with:
  • Method: POST
  • URL: https://api.blinkpdf.io/v1/render
  • Header: x-api-key: bp_...
  • Header: Accept: application/pdf
  • Body (JSON): { "markdown": "...", "metadata": { "title": "..." } }
  • Response type: Binary (the response is a PDF file)
The Markdown content you send in the body typically comes from an earlier step in your workflow — a form submission, a database query, a CRM record, or an AI node.
Your API key is a secret credential. Store it in your platform’s built-in credential or environment variable manager rather than hardcoding it directly in the node configuration.

​
n8n

In n8n, use the Set node before the HTTP Request node to assemble your Markdown string from multiple upstream fields. This keeps your HTTP node body clean and easy to read.

​
Make (Integromat)

​
Zapier

Zapier’s free and lower-tier plans throttle the number of tasks per month. Each call to Blink PDF counts as one Zapier task. Factor this into your plan selection on both the Zapier and Blink PDF sides.

​
Common Automation Patterns

Form → PDF → Email

A form submission triggers the workflow. The form data is assembled into a Markdown summary or receipt, rendered by Blink PDF, and emailed to the submitter as an attachment.

CRM → Invoice → Drive

A new deal or order in your CRM triggers invoice generation. Line item data fills a Markdown template, Blink PDF renders it, and the PDF is saved to Google Drive or Dropbox.

Schedule → Report → Slack

A daily or weekly schedule trigger pulls data from a database or analytics tool, formats it as a Markdown report, renders to PDF, and posts the file to a Slack channel.

AI Node → Summary → Storage

An AI node (like n8n’s OpenAI integration) generates a Markdown summary from raw input. Blink PDF converts it to PDF, and the file is saved for archival or sharing.
Blink PDF’s median render time of ~100ms means it adds negligible latency to your automation workflows. Even at Free plan rates (10 requests/min), you can process a document every six seconds continuously — and Pro (120/min) leaves plenty of headroom.