Integrations

Use RelayPDF from your existing stack.

Pick CLI or MCP when a coding agent or script should generate documents. Pick the official n8n node or Zapier app when the workflow already lives there. Make still calls the REST API with HTTP modules — there is no official Make app yet.

CLI and MCP are first-party. n8n uses `n8n-nodes-relaypdf`. Zapier uses the official Platform app (invite until directory review).

RelayPDF MCP integration

Remote hosts call POST https://api.relaypdf.com/mcp with a bearer key. Local agents run npx @relaypdf/cli mcp after relaypdf setup. Same tools; hosted results are 24-hour URLs.

Open guide →

RelayPDF CLI integration

Use the official CLI for local scripts, CI helpers, and agent workflows that need reproducible commands.

Open guide →

RelayPDF in n8n

Install n8n-nodes-relaypdf, add a RelayPDF API credential, and pick an operation. Default output is a binary PDF on field data so Gmail, Slack, and Drive attach it without an HTTP Request node. Recurring invoices use a published templateId plus templateData.

Open guide →

RelayPDF in Make

In Make, configure an HTTP module for RelayPDF endpoints and pass JSON payloads directly. No custom connector is required to start.

Open guide →

RelayPDF in Zapier

Search RelayPDF in the Zap editor, connect a pdf_live_ key, and pick an action. Create PDF, Convert File, and Merge return a File field Gmail, Drive, and Slack can attach. Recurring invoices use a published templateId plus templateData. Convert and raster jobs wait via Zapier callbacks so LibreOffice can outlive the action timeout.

Open guide →