Documentero

Documentero fills Word and Excel templates with your data and returns a finished DOCX or PDF. Agents generate contracts, quotes, and certificates from records and file the result straight into storage.

2 actions API key available

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

A project is approved and needs a statement of work

Agent gathers the placeholder values from the project record and the rate card

The value set is checked for empty and malformed fields, because no operation reads the template back

Generate And Store Document renders one document into file storage, with the email fields left empty so nobody is contacted

The rendered sample and the exact values that produced it post to the account manager

A person reads the sample, and their approval is what releases the rest of the run

What This Integration Enables

Documentero does one thing: it fills a Word or Excel template with your data and hands back a finished DOCX or PDF. It is not electronic signature, and it does not pretend to be. The template is uploaded once with its placeholders in it, and from then on a flow supplies the values. Two operations cover the entire product, which makes this one of the smallest surfaces in our connectors catalog and one of the easiest to reason about.

The choice between the two operations is the whole design decision. Generate Document returns a short-lived download link, which is right when the document is being handed straight to someone who will open it now. Generate And Store Document follows that link for you and puts the file into flow file storage before it expires, which is right for anything that has to survive the next five minutes. FlowRunner agents default to the second, because a link that has expired is indistinguishable from a document that was never made, and the difference matters to whoever goes looking for it in three months.

Without FlowRunner

Documents built in a word processor Somebody opens last quarter's statement of work and edits the parts that changed

Format decided at the end The customer wants a PDF and the reviewer wants a Word file, so the document is exported twice

Links that expire quietly A generated document is passed on as a URL, and by the time somebody opens it there is nothing there

With FlowRunner

Documents built from the record The values come from the system that holds them, keyed by the placeholder names the template defines

Format decided by destination PDF for the customer and Word for the colleague who has to edit it, chosen in the same call

Files kept on purpose Generate And Store Document follows the link before it expires and puts the file where it belongs

Use Case Scenarios

The statement of work that writes itself

A project is approved in Airtable or the delivery system of record. The agent assembles the client name, the scope lines, the rate, and the milestone dates into a value set keyed by the template's placeholder names, and calls Generate And Store Document in PDF. The file lands in Google Drive in the client's folder and a link posts to the account manager in Slack. Nobody opened a word processor, and the figures in the document are the figures in the system rather than the figures somebody remembered.
Two formats, one set of facts

The same generation runs twice with a different format. The customer receives the PDF, which cannot be casually altered. The delivery lead receives the DOCX, because they are going to edit the scope section before the kickoff call. Both come from one value set, so the two files cannot drift apart the way a PDF exported from a separately edited Word document eventually does. Where the template's own default is correct, the format is left unset; where a flow needs one or the other for certain, it says so explicitly.
A batch, run carefully

Renewal notices go out to a list of clients held in Google Sheets. Rather than looping straight through the rows, the agent renders the first one, files it, and posts it for review. Once a person approves it, the remaining rows run and each finished document is filed against its client record in HubSpot. Where the flow needs Documentero itself to email the finished document, that field is filled in only on the approved run, because filling it in sends a real attachment to up to five real addresses.

Human-in-Loop Highlight

This connector has no inspection surface at all, in either direction. There is no route that lists templates, so the template identifier has to be typed or carried in your own data, and nothing will tell a flow that the identifier it is holding now points at a template somebody rebuilt last week. There is no operation that reports which placeholders a template expects, so a mis-keyed value cannot be caught before it is used. There is no free validation call, so every attempt to find out spends real monthly allowance. There is no generation history, so after the fact nothing lists what was produced. And the API answers failures with HTTP 200 and an error inside the body, which this connector reads and raises properly, but which tells you something about how quietly this platform fails when it is called directly. The consequence is simple: the only moment where a person can affect the outcome is before the first generation. So FlowRunner agents on this connector render exactly one document, keep the email fields empty so nothing reaches anybody, store it, and stop: "First renewal notice for Halden Group is rendered and filed. Placeholder values used: client Halden Group, renewal date 14 November, annual fee 62,400, owner S. Whitcombe. 47 more rows queued. Look right?" A person opens one PDF and answers. On a connector this small, the review is the only control there is, and one sample is cheap compared with forty-eight wrong documents and the quota they spent.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via email

Human decides

Agent resumes with decision

Agent Capabilities

2 actions

Generation

Generate Document Fills a template with your data and returns a download link. The link is short-lived, so this is the right call when the document is being handed straight to somebody who will open it now, and the wrong one for anything that has to be kept.
Generate And Store Document Fills a template and stores the finished document in file storage before its download link expires. The default for agent workflows, because the file survives the flow that made it and can be attached, filed, or forwarded later.

Frequently Asked Questions

What can FlowRunner do with Documentero?

FlowRunner agents can run Generate Document and Generate And Store Document in Documentero.

Does connecting Documentero to FlowRunner require OAuth?

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

Can Documentero trigger a FlowRunner workflow automatically?

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

Start building with Documentero

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us