APITemplate.io

Generate PDFs and images from reusable templates or raw HTML with APITemplate.io, returning hosted download URLs. Agents render invoices, receipts, certificates, and marketing assets from record data as a step in a workflow.

7 actions available

A batch of records needs documents (invoices to bill, certificates to issue)

Agent pulls the field values each template expects from the source system

Create PDF merges each record's data into the saved template and returns a download URL

Agent confirms every record returned a document before moving on

Agent posts the run summary and download links to the owning channel

Each generated PDF is passed to the delivery step that sends it to the recipient

A batch bound for customers pauses for an owner to approve one sample before the whole run goes out

What This Integration Enables

Agents can generate documents and images as a step inside a workflow. The core actions render a PDF or an image from a saved template by merging data into it, or render a PDF directly from raw HTML and CSS when no template exists. Agents can list the templates in the account, list previously generated objects to retrieve their download URLs, delete old objects, and check remaining account credits as a connection test. The value is not that FlowRunner can call a rendering API. The value is that producing a batch of customer documents stops being a manual chore and becomes a governed step, with a human pulled in to approve the output before an entire run is sent out.

Without FlowRunner

Hand-built documents Someone opens a layout and produces each invoice or certificate one at a time

No batch check Failures in a run are noticed only when a customer says a document never arrived

Ad hoc file handling Generated files are saved and shared wherever the person happened to be working

With FlowRunner

Merged from record data The agent renders every document from the template and source data in one pass

Verified batch The agent confirms each record produced a document before the run moves downstream

Hosted URL handoff Every document comes back as a hosted download URL ready for the next step

Use Case Scenarios

Invoices generated from records

A billing run needs a PDF invoice for every open row. The agent reads the rows from [Airtable](/integrations/airtable), then calls Create PDF for each one, merging the customer name, line items, and total into a saved invoice template. Each call returns a hosted download URL. The agent confirms every row produced a document, then hands each PDF to the delivery step. The work shifts from a person rendering invoices one at a time to an agent producing the full run and flagging any row that failed.

PDF from raw HTML when no template fits

A workflow needs a one-off document that no saved template covers, such as a custom summary assembled from several systems. The agent builds the HTML and CSS in an earlier step, then calls Create PDF from HTML with the body and rendering settings. APITemplate.io returns a hosted PDF URL with no template required. The agent stores or forwards the file. The one-off document gets produced without anyone opening a design tool.

Marketing images with a human gate before the batch ships

A campaign needs a personalized image for each recipient. The agent calls Create Image against an image template, overriding named layers with each recipient's details, and gets back JPEG and PNG URLs. Because the whole batch is about to go to customers, the agent does not send it automatically. It renders one sample, posts it for the owner to review, and waits. Once the owner approves the sample, the agent releases the rest of the run and archives the outputs to [Google Drive](/integrations/google-drive-api). The routine rendering is automated; the decision to send the batch stays with a person.

Human-in-Loop Highlight

The consequential moment with APITemplate.io is releasing a whole batch of generated documents to customers, not rendering one file. A wrong value in a template renders wrong across every record in the run, and nobody sees it until the documents are already out. So before an agent sends a customer-facing batch, it pauses and posts one rendered sample to the owner through [Slack](/integrations/slack): "The invoice run is generated, 214 PDFs, here is a sample of the first one. Approve to send the batch, or flag the template to fix?" The owner checks the sample and approves or corrects. The agent treats the batch release, not the individual render, as the point that needs human judgment, because that is where a template mistake becomes a customer mistake at scale.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via Slack

Human decides

Agent resumes with decision

Agent Capabilities

7 actions

PDF Generation

Create PDF Generates a PDF from a saved template by merging your data into it. Provide the template ID and a data object whose keys match the template's placeholders. Used to render invoices, receipts, contracts, or certificates from record data; returns the hosted download URL for the generated PDF.
Create PDF from HTML Generates a PDF directly from raw HTML and CSS with no saved template. Provide the HTML body, optional CSS, and optional rendering settings such as page size, margins, and orientation. Used when a workflow needs a one-off document that no template covers; returns the hosted download URL.

Image Generation

Create Image Generates a JPEG and PNG image from a saved image template. Provide the template ID and an overrides object that replaces the text, images, and other layer properties defined in the template. Used to produce personalized social or marketing assets; returns hosted download URLs for both outputs.

Templates

List Templates Lists all PDF and image templates in the account, including each template's ID, name, and format. Used to discover a template ID to pass to Create PDF or Create Image.

Objects

List Generated Objects Lists previously generated PDFs and images, most recent first, each with its transaction reference, template ID, download URL, and creation time. Used to retrieve download URLs for earlier outputs or to audit a run, with pagination via limit and offset.
Delete Object Deletes a previously generated PDF or image and its hosted file, identified by the transaction reference returned when it was created. This action cannot be undone. Used in retention and cleanup workflows to remove old generated files.

Account

Get Account Information Retrieves account information, including remaining API credits and plan details. Used as a connection check to confirm the API key and region are configured correctly before a run.

Start building with APITemplate.io

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us