Peedief
DocumentsTurn HTML or a saved dashboard template into a finished PDF through Peedief's managed rendering service. Agents produce documents without operating a Chromium instance inside the flow.
What This Integration Enables
Peedief has two actions, and the small surface is the argument. Generate PDF from Template renders a template designed in the Peedief dashboard against JSON supplied by the flow, with conditional sections, loops, and nested objects so the payload can mirror the shape of the source record rather than being flattened for the renderer. Convert HTML to PDF renders raw markup for the one-off case, with control over page format, orientation, per-side margins, background graphics, and zoom. Both return a document that has been checked for a valid PDF signature and copied into FlowRunner file storage, because Peedief's own download links expire an hour after they are issued.
What you are buying is the absence of infrastructure. Generating a PDF properly means running a browser, and running a browser means memory limits, font packages, security patches, and a class of failure that only appears under load. Peedief takes that off the table, and FlowRunner's job is to make sure removing the infrastructure does not also remove the oversight. There is no listing action here: the template is addressed by its name exactly as it appears in the dashboard, so the flow references something it does not own and cannot inspect. That is a reasonable trade for a design that a non-developer can keep editing. It is also the precise reason a person should look at the first rendered document before the rest of the batch follows it.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Monthly customer statements from a managed template
The statement cycle starts and the agent assembles each customer's period activity from the billing system. It calls Generate PDF from Template once, reviews the result, and only then renders the remainder of the run. Each finished statement is stored durably and delivered through Gmail. The finance team edits the statement design in the Peedief dashboard whenever the brand or the disclosure language changes, and the flow never changes at all, because the flow only ever sends values.
Order confirmations at checkout speed
A payment succeeds in Stripe and the agent renders an order confirmation from the confirmation template with the line items, totals, and shipping details merged in. Conditional sections in the template handle the cases the data implies: a discount block that only appears when a discount applied, a shipping block that disappears for a digital order. The confirmation is stored and attached to the customer record. No browser is involved anywhere in the flow.
Certificates issued in bulk from a tracked list
A cohort finishes a program and the roster lives in Airtable. The agent renders one certificate per participant, posts the first one to Slack for the program lead to confirm the name formatting and the date, then completes the run. For a one-off award that does not justify a dashboard template, the agent assembles the markup in the flow and uses Convert HTML to PDF instead, setting the page format and margins explicitly so the printed result matches the frame it will be mounted in.
Human-in-Loop Highlight
The gate here is created by something this connector deliberately does not have. Peedief exposes no template listing and no template metadata, so the flow addresses the design by its dashboard name and gets back whatever that name currently resolves to. If a designer renamed it, the run fails outright, which is the good outcome. If a designer restyled it, moved the remit-to block, or changed the disclosure paragraph, the run succeeds and produces hundreds of documents in a layout nobody in the automation ever approved. The agent cannot check that on its own, because there is no action that would let it. So it renders exactly one document, stores it, and asks in the operations channel: "First statement for the June run is ready against the template named customer-statement-v3. Someone last touched that design in the dashboard, and this connector cannot tell me what changed. Open the sample and confirm this is the layout you want on 480 customer statements, or stop the run." That is human-in-the-loop used the way it should be: not as an approval ritual on every document, but as one question at the single point where the agent genuinely cannot see what a person can.
Agent Capabilities
2 actionsPDF Generation
2- Generate PDF from Template Renders a template designed in the Peedief dashboard using the JSON data supplied by the flow, then stores the finished document in FlowRunner file storage. Because the layout lives in the template, the flow only sends values, which keeps invoices, certificates, reports, and order confirmations consistent while the design changes without touching the automation. Templates support conditional sections, loops, and nested objects, and the template is addressed by its name exactly as it appears in the dashboard.
- Convert HTML to PDF Renders raw HTML markup into a PDF with Peedief's managed browser and stores the result in FlowRunner file storage, so no browser has to be maintained inside the flow. Page format, orientation, per-side margins, background graphics, and a zoom factor are all configurable. Use it for one-off documents built from markup assembled earlier in the flow, and prefer the template action for anything repeatable.
Frequently Asked Questions
What can FlowRunner do with Peedief?
FlowRunner agents can run Convert HTML to PDF and Generate PDF from Template in Peedief.
Does connecting Peedief to FlowRunner require OAuth?
No. Peedief connects to FlowRunner with an API key, no OAuth flow required.
Can Peedief trigger a FlowRunner workflow automatically?
Peedief doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Peedief
$100 in credits. No card required. Connect in minutes.