Document automation

Document automation, from template to delivery

Design a document once and automate the rest — generate from a form, a CSV, the REST API, or Claude, one at a time or thousands.

  1. 1

    Design the template

    Build the recurring document once and bind the fields that change.

  2. 2

    Connect your data

    Fill a form, upload a CSV, call the REST API, or describe it to Claude.

  3. 3

    Generate and deliver

    Receive presigned PDF URLs ready to send or store; poll batch jobs until the ZIP is ready.

Recurring documents are the same shape every time — only the data changes. ImaginePDF turns that pattern into a pipeline: design the template once, then drive it from whatever source fits.

Fill it by hand for a one-off, render a CSV for a batch, call the REST API from your product, or ask Claude to draft a new one. The template is the constant; the trigger is up to you.

What you get

Design once, automate forever

A single template feeds every channel, so the document stays consistent however it is generated.

Trigger from your stack

Call the REST API with a workspace key, then use the returned URL or poll an asynchronous batch job.

Bulk or on-demand

Render a single document instantly, or a batch of up to 100 rows from a dataset.

Or just describe it

Use Claude to draft a brand-new document on request — then it joins the same automated pipeline.

How it works

  1. 1

    Design the template

    Build the recurring document once and bind the fields that change.

  2. 2

    Connect your data

    Fill a form, upload a CSV, call the REST API, or describe it to Claude.

  3. 3

    Generate and deliver

    Receive presigned PDF URLs ready to send or store; poll batch jobs until the ZIP is ready.

In code

generate.sh — bash
# fire one document from your app
curl https://api.imaginepdf.com/api/v1/designs/tmpl_payslip/generate \
  -H "X-API-Key: pc_live_..." \
  -H "Content-Type: application/json" \
  -d @data.json

# → presigned PDF URL

What's supported — and what isn't

Supported

  • Four ways to generate from one template: visual editor, CSV, REST API, and Claude
  • Single documents on demand or batches of up to 100 rows
  • Presigned PDF delivery and asynchronous batch status polling
  • Workspace roles so templates, fonts, and datasets are shared by the team

Current limitations

  • Integrations are via the REST API and the open-source plugin — no Zapier/Make or self-hosting today
  • Up to 100 rows per batch job; batch generation is a paid-plan feature
  • Generated PDF links are presigned with a 1-hour expiry

Frequently asked questions

What kinds of documents can I automate?
Anything repeatable — invoices, payslips, certificates, delivery notes, tickets. Design the template once and drive it from your data.
How do I trigger generation?
Four ways: fill a form, upload a CSV, call the REST API from your app, or ask Claude. They all render the same template.
Do you integrate with Zapier or Make?
Not today. Integrations go through the REST API and the open-source Claude Code plugin, which cover custom and AI-driven workflows.
Can a human review before sending?
Yes. Render a free preview or a single PDF to check it, then run the batch when you are happy.

Start generating PDFs free

Design on a visual canvas, let Claude draft it, or call the API — and generate one PDF or thousands. No watermark.