Plumsail Documents
DocumentsGenerate finished documents with Plumsail Documents. Agents merge CRM or spreadsheet data into a prebuilt Process template to produce DOCX or PDF output, running synchronously for fast templates or start-then-fetch for long jobs.
What This Integration Enables
Document generation is where clean data goes to get mangled by hand. Plumsail Documents holds the template and output settings as a Process; FlowRunner supplies the merge data and the judgment about when a document should exist at all. Agents call Generate Document for fast, single-request rendering, or split long jobs into Start Process and Get Process Result so a heavyweight render never blocks the workflow. Every finished file lands in FlowRunner file storage with a URL, which means the document is immediately a workflow object: attachable to a CRM record, postable to Slack, archivable to Drive. The division of labor is the point. The template, its layout, branding, and output format, stays governed in Plumsail where a document owner controls it. The merge data comes from systems of record, not from whoever last opened the file. And the decision about which documents need a human's eyes before they leave the building lives in the workflow, where it is enforced rather than remembered. - Render invoices, contracts, quotes, and certificates by merging CRM, order, or spreadsheet data into prebuilt templates - Choose the synchronous path for fast templates or start-then-fetch for large documents, per workflow step - Discover available templates with List Processes to wire new document types into automations - Put a human between the rendered document and the customer who receives it - Attach, post, and archive finished files anywhere, since every render returns a storage URL the rest of the workflow can use
Without FlowRunner
With FlowRunner
Use Case Scenarios
The contract that renders itself when the deal closes
When a [HubSpot](/integrations/hubspot) deal hits Closed Won, the agent pulls the deal's line items, terms, and signer, validates the merge fields, and calls Generate Document against the MSA Process. The rendered PDF posts to the deal channel in [Slack](/integrations/slack) for the account owner's review. On approval, the file archives to [Google Drive](/integrations/google-drive) and attaches to the deal. Legal built the template once; nobody has touched a Word file since.
Order confirmations at order speed
A [Shopify](/integrations/shopify) order arrives. The agent maps the order lines and customer details into merge data, runs Generate Document against the invoice Process, and files the PDF to the customer's folder with the order record linked to the stored file URL. The invoice exists before the warehouse picks the order, and the format is identical for order one and order ten thousand.
Two hundred certificates from one spreadsheet
A training company finishes a cohort. The agent reads the roster from [Google Sheets](/integrations/google-sheets), and because certificate rendering is heavier than a quick merge, it uses the start-then-fetch pattern: Start Process fires per row, and Get Process Result collects each finished PDF as it becomes available. The coordinator spot-checks a sample posted to Slack, approves the batch, and the send goes out. The afternoon this used to consume goes back to the humans.
Human-in-Loop Highlight
Generate Document produces the artifact your customer signs, pays, or files, and a rendered document has a way of laundering bad data into something that looks official. A wrong price in a CRM field is a data bug; the same wrong price on a generated contract PDF that went out for signature is a commercial commitment you now have to walk back. So for customer-facing documents, FlowRunner puts the review after the render and before the release: the agent validates merge fields, runs the Process, and presents the finished PDF itself to the account owner, because humans catch things in a laid-out document that they miss in a JSON blob. Internal reports and archive copies flow straight through. The ones that reach a counterparty wait for a person, and the approval is recorded next to the file.
Agent Capabilities
4 actionsDocument Generation
3- Generate Document Runs a Process and returns the generated document in a single synchronous request, storing it in FlowRunner file storage and returning a URL. The simplest path when the template renders quickly: one call in, finished file out.
- Start Process Starts a document generation Process by ID, feeding it merge data as JSON, and returns a reference to the generated document. The first half of the asynchronous pattern for long-running or heavyweight renders.
- Get Process Result Downloads the document produced by a Process run into FlowRunner file storage and returns its URL. Pairs with Start Process; large documents may take a moment to become available. Output format is set by the Process configuration in Plumsail.
Discovery
1- List Processes Lists the document generation Processes in your account with each Process ID and name, the IDs that Start Process and Generate Document take as input. A public list endpoint may not be exposed on all account tiers; the dashboard is the fallback.
Frequently Asked Questions
What can FlowRunner do with Plumsail Documents?
FlowRunner agents can run Start Process, Get Process Result, and Generate Document in Plumsail Documents, plus 1 more action.
Does connecting Plumsail Documents to FlowRunner require OAuth?
No. Plumsail Documents connects to FlowRunner with an API key, no OAuth flow required.
Can Plumsail Documents trigger a FlowRunner workflow automatically?
Plumsail Documents doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Plumsail Documents
$100 in credits. No card required. Connect in minutes.