CraftMyPDF n8n integration: the verified node, setup steps and limits

How CraftMyPDF connects to n8n

CraftMyPDF works with n8n through a dedicated node, not a generic HTTP workaround. n8n's own integration listing says the CraftMyPdf node is built and maintained by CraftMyPDF and verified by n8n. That makes it a verified community node: it is installed from the nodes panel by an instance owner or admin, after which every member of the instance can use it.

The underlying package on the npm registry is n8n-nodes-craftmypdf, published by CraftMyPDF, with version 0.2.1 as the latest on 3 October 2026. CraftMyPDF's own integration page describes the node as built into n8n, while its older blog guide describes a community-node install. n8n's listing is the authoritative description: partner-built and verified.

What the CraftMyPDF node can do

The listing shows actions only. It does not show a CraftMyPDF trigger, so a workflow starts from another node such as a webhook, a form or a spreadsheet row.

Plan needed on each side

On the CraftMyPDF side, the Free plan is enough to start. It includes the REST API that the node calls, with 50 PDFs or images a month and 3 templates. The first paid plan, Lite, is $29 a month for 1,200 PDFs, as read on the vendor's pricing page on 3 October 2026. Each PDF created from n8n uses one credit, the same as a direct API call.

On the n8n side, n8n's documentation says verified community nodes are installed from the nodes panel, and that on n8n Cloud the instance owner can switch their availability on or off in the Cloud Admin Panel. Unverified packages installed from npm are available only on self-hosted n8n.

Setup steps in order

1. In CraftMyPDF, open Manage Templates, create a PDF template and design it in the editor.
2. Open the API Integration tab and copy your API key. Copy the template ID from Manage Templates.
3. In n8n, open the canvas and the nodes panel, then search for CraftMyPDF. Verified community nodes appear in a section labeled More from the community.
4. Select the node and choose install. This needs the instance owner or an admin account.
5. Add a trigger node, for example a webhook or form submission.
6. Add the CraftMyPDF node, create a credential with your API key, then enter the template ID and map the data fields.
7. Add a final node to email the PDF or save it to cloud storage.

If your instance cannot use the nodes panel route, the vendor's guide gives the manual command npm install n8n-nodes-craftmypdf for self-hosted installs.

Known limits and what to check after the first run

• Link expiry. Generated files on CraftMyPDF's CDN expire after 5 minutes by default. Raise the expiration setting, up to 7 days, or download the file in the next node.
• Timeouts. The API reference lists a 100 second maximum on the default endpoint. Use Create Async for long reports.
• Rate limit. 100 requests per 10 seconds per IP address, with an HTTP 429 response beyond that. Batch loops in n8n can hit this.
• Credits. There is no automatic upgrade or overage. Watch for the vendor's 80% and 100% usage emails.
• Data shape. Confirm that nested arrays such as line items arrive as JSON and not as a flattened string. Our field map guide helps here.

After the first run, open the PDF, check page breaks on a long record, and confirm the transaction appears in CraftMyPDF. The release checklist lists the rest.

Zapier and Make as alternatives to n8n

CraftMyPDF also documents apps for Zapier and Make.com, both included on every plan. In Zapier you choose CraftMyPDF as the app and Create PDF as the event, then connect with the API key. In Make.com you add the CraftMyPDF app and select Create a PDF. Both offer three payload types: fields generated from the template's sample data, a flat dictionary, or raw JSON.

Choose n8n if you self-host or want the async and merge operations in one node. Choose Zapier or Make if your team already pays for one of them. If you would rather call the service directly, see the CraftMyPDF API page.