--- title: "Eledo Integration" description: "Eledo renders a designed template plus your data into a PDF. Agents generate invoices, contracts, and certificates on demand and either receive the file or hand out a download link." url: https://flowrunner.ai/integrations/eledo date_modified: 2026-09-04T14:07:24-07:00 --- # Eledo [Documents](https://flowrunner.ai/integrations/category/documents-forms) Eledo renders a designed template plus your data into a PDF. Agents generate invoices, contracts, and certificates on demand and either receive the file or hand out a download link. 6 actions · API key · available [Eledo website](https://eledo.online/) · [Platform Documentation](https://eledo.online) · Capability data verified 2026-08-13 1. An invoice is approved for issue in the accounting system 2. Get Template Schema reports the exact keys and types the invoice template expects 3. Agent maps the invoice record onto those keys and flags anything required that is empty 4. Generate PDF renders the invoice and stores the file in flow storage as the durable copy 5. The template version used is recorded alongside the file, so this month's output stays reproducible 6. The rendered invoice and the proposed delivery method post to the controller 7. The controller decides whether it goes out as a kept file or as a one-time link that deletes itself on first download ## What This Integration Enables Eledo renders a template you designed plus the data you supply into a PDF, and it gives you two ways to take delivery of the result. Generate PDF returns the bytes and stores them in FlowRunner file storage, leaving nothing behind on Eledo. Create File does the opposite: it keeps the document on Eledo and hands back a download URL you can pass on. Those are not two flavors of the same call. They are two different answers to the question of who ends up holding the document, and a finance workflow should answer that deliberately. The other operation worth planning around is Get Template Schema, which returns the exact shape of data a template expects: the keys, their types, and which of them are lists. Reading the schema once when a flow is built is the difference between a mapping and a hopeful guess, and it is what lets an agent report a missing field before it renders rather than after somebody notices a blank line on an invoice. Template versions are optional everywhere, and leaving them empty means the output follows whatever the template looks like today. For anything auditable, naming the version is what keeps last quarter's document reproducible after the design has moved on. ### Without FlowRunner **Guessing at field names**: The template is filled by trial and error until the output stops showing gaps **Documents that change under you**: A template edit last week silently changes how last month's invoice re-renders **Delivery as an afterthought**: Every document is handled the same way, whether it is a permanent record or a one-time payslip ### With FlowRunner **Field names read from the template**: Get Template Schema returns the keys, the types, and which of them are lists, before anything is filled **Documents pinned to a version**: A named template version keeps an auditable document reproducible after the design moves on **Delivery as a decision**: Kept file or single-use link is chosen per document type, by a person, and recorded ## Use Case Scenarios ### The invoice that renders from the ledger An invoice is approved in [QuickBooks Online](https://flowrunner.ai/integrations/quickbooks-online) or [Xero](https://flowrunner.ai/integrations/xero). The agent calls Get Template Schema once at build time so the mapping matches the template exactly, then Generate PDF for each approved invoice with the template version pinned. The stored PDF is attached to the customer email through [Gmail](https://flowrunner.ai/integrations/gmail-service) and filed against the customer record in [Google Drive](https://flowrunner.ai/integrations/google-drive-api). The document the customer receives and the document the auditor will ask for later are the same file, generated once, kept once. ### A link instead of an attachment Some documents are better handed over as a URL: a certificate a customer will open on a phone, or a summary that goes into a chat message where an attachment would be awkward. The agent calls Create File instead of Generate PDF, and posts the returned URL into the conversation in [Slack](https://flowrunner.ai/integrations/slack) or out to the recipient. Nothing is stored on the FlowRunner side, which is the right trade when the document is transient and the wrong one when it is a record. ### Payment confirmations without a template rebuild A payment settles in [Stripe](https://flowrunner.ai/integrations/stripe). The agent calls List Templates to resolve the receipt template for the entity that took the payment, since Eledo exposes both your own templates and public ones, checks the schema, and renders the confirmation. Get Profile runs at the top of the flow as a cheap connection check that costs nothing and needs no identifiers, so a broken key is reported as a broken key rather than as a batch of missing receipts. ## Human-in-Loop Highlight Eledo's single-use option is the rare case where the read is the destructive operation. Create File with Single Use set produces a link that works exactly once, and the download is what removes the file. That is genuinely the right behavior for a payslip or a one-time certificate. It is exactly wrong for an invoice a customer will open twice, or for anything a support agent may need to re-send. Worse, the danger does not sit on the call that made the choice. It sits on Download File, which looks like an ordinary read: nothing in an identifier says whether the file behind it is single use, so a monitoring step that verifies the file exists, or a retry after a timeout, destroys the customer's only copy and returns nothing the second time. FlowRunner agents therefore never set single use on their own initiative and never re-read a file they did not create. The agent renders, files the durable copy, and asks: "The February invoice for Marchmont Ltd is rendered. Sending it as a kept file, or as a single-use link? Single use means the customer can open it once, and a resend request cannot be answered from Eledo." The controller answers, the answer is recorded on the record, and the flow follows it. A document that deletes itself is a policy choice about a customer relationship, and it does not belong in a default. 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 6 actions ### Documents 3 - **Generate PDF** Fills a template with your data and stores the finished PDF in flow file storage. The durable path: the bytes come back, nothing is left on Eledo, and later steps can attach or forward the file. - **Create File** Fills a template and keeps the result on Eledo, handing back a download URL instead of the bytes. Useful when a link is what you actually want to pass on, and the place where the single-use option is chosen. - **Download File** Downloads a file Eledo is holding and stores it in flow file storage. If the file was created as single use, this deletes it, so a second download returns nothing. Treat it as a one-way action unless the flow created the file itself. ### Templates 2 - **List Templates** Lists the templates you can fill, your own or the public ones, so a flow resolves a template by name rather than carrying a hard-coded identifier. - **Get Template Schema** Reads the shape of data a template expects: the keys, the types, and which ones are lists. The discovery call worth making once at build time rather than guessing at every render. ### Account 1 - **Get Profile** Reads the account the key belongs to. The cheapest connection check available, and worth putting at the top of a batch so a bad key fails as a bad key. ## Frequently Asked Questions ### What can FlowRunner do with Eledo? FlowRunner agents can run Generate PDF, Create File, and Download File in Eledo, plus 3 more actions. ### Does connecting Eledo to FlowRunner require OAuth? No. Eledo connects to FlowRunner with an API key, no OAuth flow required. ### Can Eledo trigger a FlowRunner workflow automatically? Eledo doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Eledo?** This integration exposes Eledo to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/eledo. Site index: https://flowrunner.ai/llms.txt