# n8n → PDF with makesPDF

> For AI agents: a documentation index is available at https://makespdf.com/llms.txt — every docs page also has a markdown twin (append .md to the page URL), including this one: https://makespdf.com/docs/integrations/n8n.md

[n8n](https://n8n.io/) can call makesPDF through its MCP client nodes, which connect to our hosted MCP server. The **MCP Client Tool** node gives the tools to an AI Agent; the **MCP Client** node runs one tool as an ordinary workflow step. Every makesPDF MCP tool is available to both.

## Connect

You need a makesPDF [API key](https://makespdf.com/settings/api-keys?ref=n8n).

1. Add an **MCP Client** node for a plain workflow step, or an **MCP Client Tool** node under an AI Agent.
2. Set the endpoint to `https://makespdf.com/api/v1/mcp`. The **MCP Client** node has **MCP Endpoint URL**; in n8n's docs the **MCP Client Tool** field is called **SSE Endpoint**, so use the field for the server URL.
3. Choose the **Streamable HTTP** transport where the node asks for one (the **MCP Client** node has **Server Transport**).
4. Set **Authentication** to **Bearer** and create a credential whose token is your API key, with no `Bearer ` prefix.
5. On the **MCP Client Tool** node, leave **Tools to Include** on **All**, or pick **Selected** to expose only the tools you need.

## Render a PDF

On the **MCP Client** node, pick a tool from **Tool** (n8n fetches the list from the server) and fill in its arguments. **Input Mode** has **Manual** and **JSON**; use **JSON** for `data`, which is nested. Under an AI Agent, describe the document and the agent picks the tool.

| Tool | Arguments | What it does |
| --- | --- | --- |
| `render_markdown` | `markdown`, optional `options` | Markdown → PDF (1 credit per 10 pages) |
| `render_template` | `templateId`, `data` | A stored or library template filled with your data |
| `validate_markdown` | `markdown` | Free accessibility check before you render |
| `list_templates` | optional `q`, `category`, `tags` | Find a library template such as `invoice-classic` |

The result carries `pageCount`, `creditsDeducted`, `artifactId` and a `downloadUrl`.

## Get the file

`downloadUrl` is a signed link that needs no API key, so any step that downloads a URL can fetch the PDF; in n8n that is the **HTTP Request** node. The link expires 15 minutes after the render. To fetch an older render, call `get_render_download_url` with its `artifactId` for a fresh link (free).

## Prefer a regular node?

If you would rather have a makesPDF node with named fields than an MCP tool call, install the community node [`@makespdf/n8n-nodes-makespdf`](https://www.npmjs.com/package/@makespdf/n8n-nodes-makespdf).

## OAuth (untested)

n8n releases that include [PR 42608](https://github.com/n8n-io/n8n/pull/42608) can sign in with OAuth using a Client ID Metadata Document. That needs `N8N_OAUTH_CIMD_ENABLED=true` and a public HTTPS URL for the instance. makesPDF supports that kind of sign-in, but we have not tested it with n8n, so use the API key.

## Billing and limits

Renders bill your makesPDF credits exactly like the API: 1 credit per 10 pages on success, nothing on failure. Validation and listing tools are free. On the Free and Hobbyist plans, unless the account holds Growth credits, each page carries a small makespdf.com link. n8n's own charges are separate. The full tool reference is on the [MCP page](https://makespdf.com/docs/mcp).
