APITemplate.io n8n integrationAutomate APITemplate.io with n8n.
Your workflow ends with a file someone still makes by hand. The APITemplate.io n8n integration puts 3 operations across 3 resources into your canvas, so a run renders an image or a PDF from a saved template. No trigger ships with it, so something else starts the run.
Verified Trustpilot reviews · AI, automation & growth agency
What does the APITemplate.io n8n integration give you?
APITemplate.io stores your document and image templates. The n8n node calls that account from inside a workflow and hands back the rendered file as a binary field, which is n8n's way of carrying a real file between nodes instead of plain text. Three operations are exposed: read the account, create an image, create a PDF. Everything else about design and layout stays in your templates.
The clearest case is billing paperwork. A form submission arrives, the workflow maps the buyer name and the line totals onto a saved template, pdf.create renders it, and the file goes out through Gmail without anyone opening a word processor. The file never touches a shared drive unless you decide it should.
Social visuals follow the same shape with a different resource. Take a quote, a product name or a headline, push it through image.create with the text values overridden per run, then post the result to X (Formerly Twitter) or drop it in a channel with Slack for approval first. One template, a different picture every time.
Batch work is the third pattern. Rows from Google Sheets loop through the node one item at a time, each one producing its own certificate, badge or report. Since the node has no trigger, a Schedule Trigger at a fixed interval or an n8n Webhook, a URL another service calls, is what gets the batch moving.
Prefer the HTTP Request node when you need something outside those 3 operations. It reaches any endpoint of the APITemplate.io API and reuses the same credential through predefined authentication, so listing templates or deleting an old render stays possible even though the dedicated node does not cover it.
Worth knowing before you build: the node has no trigger, so it can only react, never start. Template Name or ID ties each call to one template, so a redesign happens in APITemplate.io, not in the workflow. And a required field left empty stops the node rather than rendering a half-filled document. If you want the wider picture on the platform first, the n8n review covers where it fits and where it does not.
How do you connect APITemplate.io to n8n?
- 01
Create the APITemplate.io account
You need an account on apitemplate.io before n8n has anything to talk to. The templates you build there are what the node will render later, and each one gets an identifier the node reads from your account. Nothing is installed on the n8n side: the node ships with n8n, on n8n Cloud and on a self-hosted instance alike, so the only thing missing at this point is the key.
- 02
Copy the API Key
In APITemplate.io, open API Integration and copy the API Key. That key is the single supported authentication method for this node, so there is no OAuth screen and no scope list to review. Treat it like a password: anyone holding it can render documents billed to your account. Keep the tab open until the credential is saved in n8n.
- 03
Save the credential in n8n
In n8n, go to Credentials, create an APITemplate.io credential, paste the key in the API Key field and save. A credential is created once and reused by every workflow: the node offers it in a dropdown, and you never paste the key into a node again. Drop the APITemplate.io node on the canvas, pick the credential, and the resource and operation lists become selectable.
What the APITemplate.io node can do
The APITemplate.io node exposes 3 operations across 3 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.
Account
1 operationGet an account
account.getWhat you see in n8n
Notes & use cases
Reads back the account behind the credential you selected. There is nothing to configure, which makes it the fastest way to confirm that the API Key works before the rest of the workflow depends on it.
Image
1 operationCreate an image
image.createWhat you see in n8n
Notes & use cases
Renders one image from an image template and returns it as a file on the item, ready for the next node.
Key parameters
- Template Name or ID: the image template to render, picked from the dropdown or set with an expression such as
{{ $json.templateId }}when the choice changes per item. - Put Output File in Field: the name of the binary field receiving the file, the name the posting node asks for later.
- Overrides (JSON): the per-run values, each object naming a layer and what replaces it, as in
text_1.
Create a pdf
pdf.createWhat you see in n8n
Notes & use cases
Fills a PDF template with the values you pass and returns the document as a file, one render per incoming item.
Key parameters
- Template Name or ID: the PDF template being filled, chosen in the list or built from an expression when the document type varies.
- Put Output File in Field: where the finished PDF lands on the item, before an email or storage node picks it up.
- Properties (JSON): the values injected into named properties of the template, written as JSON when JSON Parameters is on.
- File Name: under Options, the downloaded name including its extension, such as
report.pdf.
Need help automating APITemplate.io with n8n?
A person reads every message.
