Integrations

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.

Setup

Settings → Community Nodes → Install n8n-nodes-relaypdf
Credential: RelayPDF API → paste pdf_live_… (no Bearer prefix)
Node: Resource PDF → Operation Create → Source Template
Template ID: invoice
Template Data: {{ $json }}
Response: Binary  Output field: data

On n8n Cloud, search RelayPDF in the nodes panel after the node is verified. Until then, install n8n-nodes-relaypdf on self-hosted, or use HTTP Request as the fallback.

Store the key in the RelayPDF API credential. Do not put it in workflow JSON or query strings.

Binary mode writes field data. Point Gmail, Slack, and Drive at that same field. Pin earlier nodes for the recipient after a File/binary response.

Use Source Template with a published dashboard slug. HTML and Markdown are for one-off layouts built in a Code or Set node.

Office files go through Convert File. The node reads n8n binary and sets sourceFilename from the incoming file name.

Async mode can wait and return bytes, or return pollUrl for GET /v1/jobs/:id. Failed jobs are not billed.

HTTP Request remains the escape hatch: POST https://api.relaypdf.com/v1/pdf with Header Auth Authorization Bearer pdf_live_… and Response Format File.

All integrations →Docs hub →