Generate a PDF from n8n, Make or Zapier with an HTTP request
Published 3 min read
n8n, Make and Zapier can all call any API. rustedf.cloud does not have a dedicated app in them, and it does not need one: its render endpoint is a plain HTTP request, and each of these tools has a generic HTTP step. This guide shows how to set that step up to produce a PDF from the data of a workflow, such as a new order or a new row in a spreadsheet.
The request
Every tool asks for the same four things.
| Field | Value |
|---|---|
| Method | POST |
| URL | https://api.rustedf.com/v1/render |
| Header | Authorization: Bearer <your API key> |
| Body (JSON) | the template id and the data, below |
{ "template_id": "0194f2c0-…", "locale": "en-US", "output": "url", "data": { "number": "2025-0042", "customer": { "name": "Northwind Traders Inc." }, "total": "6480.00" }}Each field of data is where you map a value from an earlier step: the customer name from the
order, the total from the spreadsheet row. Send amounts as text, such as "6480.00".
The steps in each tool are called:
- n8n: the HTTP Request node.
- Make: the HTTP app, Make a request module.
- Zapier: Webhooks by Zapier, Custom Request action.
Names in the tools change from time to time, so look for the generic step that lets you choose a method, a URL, headers and a JSON body.
Get a link instead of a file
By default the response is the PDF itself, which is binary. Not every no-code step handles binary
data well, and the way to save it differs between tools. There is an easier route: ask for
"output": "url".
The response is then JSON, with a signed link that works without an API key until it expires:
{ "id": "0194f2c1-…", "url": "https://api.rustedf.com/v1/files/0194f2c1-…?exp=1760000000&sig=…", "expires_at": 1760000000, "pages": 1, "bytes": 27003, "credits_remaining": 999, "diagnostics": []}Take url and send it where it is needed: an email, a chat message, a row in a sheet. How long
the file is kept depends on your plan. If you must keep the PDF, add a step that downloads it from
the link and stores it in your own storage.
If your tool can save the response as a file, you can leave output out and attach the PDF
directly.
The pitfall with curly braces
n8n, Make and Zapier all use {{ }} for their own expressions. The template language of
rustedf.cloud uses {{ }} too. If you send inline HTML in the body, the tool may try to evaluate
the placeholders of your template before the request is even sent.
The simplest way around it is to save the template in the portal and send only its
template_id and the data, as above. Then no template syntax goes through the tool.
Check the result
Run the step once with test data and open the PDF. While you build the template, call
POST /v1/validate with the same body: it returns what the renderer could not support, without a
PDF and without using a credit.
Errors
A failed render costs no credit. The usual causes are a missing or revoked key (401), no
credits left (402), or a template that does not match the data (422). The body of the error
has a stable code and a readable message, so you can send it to a chat or a log step.
Read Rendering a PDF, Authentication and Errors and limits.
Keep reading
Code and integrations
Generate a PDF in ASP.NET Core: MVC, Razor Pages and minimal APIs
Turn a Razor view into a PDF in ASP.NET Core with one API call: a view renderer, a print-ready view, an MVC action, a Razor Pages handler and the traps to avoid.
3 min read
Code and integrations
Convert a web page to PDF in C# without a headless browser
Fetch a page with HttpClient and turn its HTML into a PDF with one API call in C#. Which pages this suits, which it does not, and how to check before you rely on it.
3 min read
Code and integrations
C# PDF report generator: a paged table with totals and page numbers
Build a PDF report in C# from a list of objects: a table whose header repeats on every page, a total, page numbers and the page count, with one HTTP call.
3 min read
Code and integrations
Save a PDF in C#: to disk, as a download or in blob storage
Save the PDF returned by a render call in C#: write it to disk, send it as a download from ASP.NET Core, keep a signed link or upload it, and avoid saving an error.
2 min read