TemplateDocs

TemplateDocs generates documents from Microsoft Word templates. Agents fill a DOCX template with data, receive a Word file or PDF, email it to the recipient in the same step, and version templates by uploading new files.

8 actions API key available

TemplateDocs website Platform Documentation Capability data verified 2026-08-13

A billing run closes and every customer needs their own statement

Agent reads the customer, the line items, and the totals from the ledger

Get Template reads the placeholders the template declares, including which of them are repeating regions

Generate Document fills the template one customer at a time, with no recipient supplied, so the files come back rather than going out

Each generated document is reconciled against the ledger totals before it is treated as final

The finance owner receives the batch with any document that failed reconciliation called out by name

The finance owner approves the batch, and only then does the flow deliver it

What This Integration Enables

TemplateDocs does one thing, which is the point. A Microsoft Word file with placeholders goes in, data goes in with it, and a Word file or a PDF comes out. There is no page builder, no design system, and no template language to learn beyond the placeholders your own document already contains. For a finance team that has spent years refining an invoice layout in Word, that is a shorter route to automated generation than rebuilding the layout in somebody else's editor.

Two details decide how a FlowRunner flow should be built against it. Get Template returns the placeholders the template declares, including which of them are repeating regions for tables and lists, so the flow can fill exactly what the document expects rather than posting a hopeful payload. And Generate Document has a delivery behavior worth naming: supply recipient addresses and TemplateDocs emails them the document as part of the same call. Leave that empty and the file simply comes back to you. FlowRunner's human-in-the-loop approach favors the second shape by default, generating the artifact and letting a person or a later step own the send, because a merge failure and an email to a customer should not be the same API call. Each generated document costs a credit and each stored template uses a quota unit, so a billing refusal is a state to handle as one of your automation exceptions rather than a bug to retry into the ground.

Without FlowRunner

Word is a manual step Somebody opens a template, fills it, saves it under a new name, and repeats that once per record

Field names are guessed A merge fails or silently leaves a blank because the placeholder was called something slightly different

Wording changes have no rehearsal A revised clause goes live on the template and the first person to see it is the customer receiving the next document

With FlowRunner

Generation is part of the run Documents are produced one per record as the billing run closes, as Word when someone will edit and PDF when nobody will

Field names are read, not assumed The flow asks the template which placeholders it declares before filling any of them

Wording changes get a proof The current file is saved, a sample is rendered from the candidate, and a person compares them before the replacement lands

Use Case Scenarios

A statement run that produces files, not surprises

The month closes in Xero or QuickBooks Online and every customer needs a statement. The agent walks the ledger, and for each customer calls Generate Document with the statement template and no recipient, so the finished PDF returns into flow storage instead of leaving the building. Every file is reconciled against the ledger total for that customer before anything is delivered, and the ones that disagree are held. The passing batch goes to the finance owner as a manifest with three sample documents attached, and delivery happens after the approval, through SendGrid or into a shared folder in Google Drive.
Line items that actually repeat

An invoice is not a flat set of fields. Get Template reports a placeholder marked as a repeating region, which is the table or list the document expects, and the agent sends an array into it so the finished invoice has one row per line item rather than one invoice per line item. The output format is chosen for the audience rather than by habit: Word when a contract will be redlined by the other side, PDF when it will not. Documents that need to reach a customer record land against it in HubSpot, and the run summary posts to Slack.
Changing the wording without changing it everywhere at once

Legal revises a payment terms clause. The agent does not simply push the new file. It calls Download Template first and stores the current Word file in flow storage, uploads the candidate as a new template with Upload Template, generates one document from it against a real recent record, and posts both the old and the new output for comparison. Only after that comparison is accepted does Replace Template File land the new wording on the template that production actually uses. The rehearsal costs one credit and one quota unit. The alternative costs whatever the wrong clause costs.

Human-in-Loop Highlight

Replace Template File swaps the Word file behind a template, and every document generated afterward comes from the new one. What makes it worth a person's attention is not the replacement itself but what this connector does not offer alongside it. There is no version list, no history, and no restore. The old wording exists only if something saved it first, and the something is Download Template, called before the replace rather than after somebody notices. So the wording change agent runs the rehearsal and then stops: "Payment terms template. Current file saved to flow storage as invoice-template-2026-09-04.docx. Sample rendered from the candidate against invoice 44012 is attached beside the same invoice rendered from the current file. Clause 4 changes from 30 days to 14 days and the late fee paragraph is new. Replace the production file, or hold?" The controller reads two documents side by side. The agent did the download, the sample, and the diff. It did not overwrite the only copy of what the company used to say.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

8 actions

Templates

List Templates Lists your templates, a hundred to a page. The inventory a flow resolves a template name against.
Get Template Reads one template, including the placeholders it contains and which of them mark repeating regions. Read this before filling a template rather than guessing at the names.
Download Template Downloads the Word file behind a template and stores it in file storage. The only way to keep a copy of the current wording before it is replaced.
Upload Template Uploads a Word file as a new template. Each stored template uses a quota unit, which makes this the safe way to stage a candidate beside the one in production.
Replace Template File Uploads a new version of the Word file behind an existing template. This replaces the file, so every later document is generated from the new one, and this connector offers no way back to the old one.
Update Template Renames a template or changes its settings. This does not touch the Word file behind it, which is what separates it from Replace Template File.
Delete Template Removes a template. Anything that generates from it stops working.

Documents

Generate Document Fills a template with your data and stores the finished document as Word or PDF. Supplying recipient addresses emails it to them in the same call, so leave that empty when the flow should hand the file back rather than send it. Each document uses one credit.

Frequently Asked Questions

What can FlowRunner do with TemplateDocs?

FlowRunner agents can run List Templates, Get Template, and Download Template in TemplateDocs, plus 5 more actions.

Does connecting TemplateDocs to FlowRunner require OAuth?

No. TemplateDocs connects to FlowRunner with an API key, no OAuth flow required.

Can TemplateDocs trigger a FlowRunner workflow automatically?

TemplateDocs doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with TemplateDocs

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us