--- title: "Lumin Integration" description: "Lumin is a New Zealand document workflow platform combining PDF editing, Lumin Sign eSignatures, and AgreementGen template generation. Agents send documents for signature in order, chase signers, require verified identity, render templates into PDFs, and file documents into a workspace." url: https://flowrunner.ai/integrations/lumin date_modified: 2026-09-04T14:07:24-07:00 --- # Lumin [Documents](https://flowrunner.ai/integrations/category/documents-forms) Lumin is a New Zealand document workflow platform combining PDF editing, Lumin Sign eSignatures, and AgreementGen template generation. Agents send documents for signature in order, chase signers, require verified identity, render templates into PDFs, and file documents into a workspace. 19 actions · API key · available [Lumin website](https://www.luminpdf.com/) · [Platform Documentation](https://github.com/luminpdf/luminsign-docs) · Capability data verified 2026-08-13 1. A deal is marked closed won and the agreement has to reach the customer 2. Get Template reports the signer roles, merge tags, form fields and AgreementGen variables this template defines, by name 3. Generate Document From Template renders the finished PDF without sending it to anybody 4. Agent confirms every required tag was filled and no priced clause came back blank 5. Agent posts the rendered document to the deal owner alongside the values it merged in 6. The owner reads the actual clauses and approves, and only then does Send Signature Request From Template email the signers ## What This Integration Enables Lumin is a New Zealand document workflow platform, and it bundles three things most vendors sell separately: PDF editing, eSignatures under the Lumin Sign name, and template based document generation under AgreementGen. For a revenue team the practical consequence is that the template, not the signature, is the product. An agreement is defined once with signer roles, merge tags, form fields and AgreementGen variables, and every deal afterwards is that template filled with different values. Get Template will tell a flow exactly what those names are, because they are the keys the send operations expect and a mismatch is silent rather than loud. FlowRunner agents send signature requests from files or templates, collect signatures in a fixed order so an approver only sees the document after the first party signs, require a signer to present a verified credential before signing, chase outstanding signatures and read back per address whether each reminder was sent, bounced or hit the daily cap, and pull the signed agreement and its Certificate of Completion into file storage where they will not expire. They can also link an agreement back to the CRM record it came from, so the document stays traceable to the deal. Lumin's file operations return signed URLs valid for 30 minutes, which is fine for a browser and wrong for an archive, so flows that mean to keep something use Download Signature Request File rather than storing a link. All of that is assembly and bookkeeping, which agents handle well. What a template based contract still needs is somebody who reads the rendered clause before it reaches a customer, and that is where FlowRunner's [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) design places its gate. This connector defines no triggers, so status is read by polling Get Signature Request rather than waiting on an event. ### Without FlowRunner **Contracts rebuilt per deal**: Someone copies the template, edits the numbers, and re-checks the clauses each time **Merge failures found by the customer**: A renamed template variable leaves a blank or a wrong figure that the counterparty is the first to read **Signed documents scattered**: The executed agreement and its certificate live in an inbox rather than against the deal ### With FlowRunner **Contracts generated from the record**: Merge tags and variables are filled from the deal data that already exists **Merge proved before the send**: The document is rendered and read as a finished PDF while nobody outside the company has seen it **Evidence filed with the deal**: The signed agreement and its Certificate of Completion land against the record they belong to ## Use Case Scenarios ### Closed won to countersigned, with a proof in the middle A deal closes in [HubSpot](https://flowrunner.ai/integrations/hubspot). The agent reads Get Template so it maps against the template's current roles and variable names rather than last quarter's, then calls Generate Document From Template to render the agreement as a finished PDF that goes to nobody. Any merge tag or form field the template marks as required has to be supplied or the call is refused outright, so an omission fails here rather than reaching a customer. The rendered PDF goes to the deal owner for approval, and Send Signature Request From Template issues the real request once the answer comes back. Where the counterparty is buying at a size that warrants it, the same call requires a verified credential before signing. ### A chase loop that reports what actually happened A scheduled sweep calls Get Signature Request for everything still open and reads each signer's own status. For the ones still waiting, Send Reminder Emails goes out, and its response is worth reading rather than discarding: it reports per address whether the email was sent, bounced, or hit Lumin's cap of 10 reminders per signer per day. A bounce is a data quality problem and a cap is a patience problem, and the agent routes them differently, posting the bounces into [Slack](https://flowrunner.ai/integrations/slack) for correction and leaving the capped ones alone until tomorrow. ### Signing inside your own product, filing outside it Rather than depending on an email a signer might never open, the agent calls Get Signing Link for one signer and presents the document inside your own application, where the customer already is. When the request is approved, Get Signature Request Artifact returns the signed agreement, the Certificate of Completion, or the two merged into a single PDF. Because those URLs expire 30 minutes after they are issued, the agent uses Download Signature Request File to bring the document into FlowRunner file storage and then files it into [Google Drive](https://flowrunner.ai/integrations/google-drive-api) against the account. Nothing in the archive depends on a link that has since gone dead. ## Human-in-Loop Highlight Send Signature Request From Template fills merge tags, form fields and AgreementGen variables by name, and that is the whole risk. A template that has been edited since the flow was built may have a renamed variable, a new required field, or a clause that now reads from a key nothing supplies. Lumin refuses the call outright when a required tag is missing, which is the loud failure and the easy case. The quiet case is a template whose payment terms clause now pulls from a variable your mapping does not set, so the agreement renders cleanly, paginates properly, and states terms nobody chose. After that request is sent, there is almost nothing to fix. Update Signature Request Due Date is the only in flight edit Lumin accepts, and it is refused on anything already approved, rejected, failed, canceled or still processing. Correcting the text means Cancel Signature Request and a fresh request to a customer who has already read the first one. So the agent renders instead of sending. Generate Document From Template produces the finished PDF and gives it to nobody, and the agent posts it with the merge report: "Agreement rendered for Kaimai Freight from template MSA 2026. All 11 required tags filled. Two optional variables were left empty: liability\_cap and support\_tier, so those clauses render with the template defaults. Send for signature, or fix the mapping first?" A person reads the clause, not the variable list. That is the difference between an agent that drafts contracts and an agent that sends them. 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 19 actions ### Signature Requests 10 - **Send Signature Request** Creates a signature request from one or more files and emails every signer a link. Signers can sign at once or in a set order, each can be required to present a verified credential first, and text tags already written into the file can be converted into signature fields. - **Send Signature Request From Template** Creates a signature request from an existing template and emails every signer a link. Merge tags, form fields and AgreementGen variables are filled by name, so the template is read first rather than assumed. This is the operation the human gate on this page precedes. - **Get Signature Request** Returns one request with its status, expiry, a browser link, and every signer with that signer's own status. Since this connector has no triggers, this is how a flow knows where a document has reached. - **Update Signature Request Due Date** Moves the due date of a request still waiting on a signer, and only from the account that created it. This is the only in flight edit Lumin accepts, which is worth knowing before a flow assumes it can correct anything else. - **Cancel Signature Request** Cancels a request so its outstanding signers can no longer sign it. The only route back from a document that went out wrong. - **Send Reminder Emails** Emails a reminder to the signers named. A reminder aimed at someone who has already signed is ignored without error, Lumin caps reminders at 10 per signer per day, and the response reports each address separately including whether it was sent, bounced or hit the limit. - **Get Signing Link** Returns a signing URL for one signer, so the document can be signed inside your own application instead of through an email link. The response also reports that signer's current status. - **Get Signature Request Artifact** Returns a signed download URL for one artifact: the signed agreement, the Certificate of Completion, or both merged into a single PDF. The certificate and the merged PDF require the request to be approved, and the URL expires 30 minutes after issue. - **Get Signature Request File URL** Returns a signed download URL for the document of a request without choosing an artifact. It expires 30 minutes after issue, so a flow downloads or stores it promptly. - **Download Signature Request File** Downloads the document as a PDF into FlowRunner file storage and returns the stored URL. Unlike the signed URLs above, the stored file does not expire, which makes this the operation to use for anything being archived. ### Templates 3 - **List Templates** Returns a page of the workspace's templates, covering AgreementGen, Sign and PDF templates alike, with a total count so a flow can walk the pages. - **Get Template** Returns one template's signer roles and their order, its merge tags, its form fields with the role each is assigned to, and its AgreementGen variables. These names are the exact keys the send operations expect, so this is read before every generated send rather than cached. - **Generate Document From Template** Renders a template into a downloadable PDF without sending it to anybody. Required tags and fields must be supplied or the call is refused. This is the proof step behind the human gate on this page. ### Documents and Agreements 3 - **Create Document** Saves a PDF into the workspace, either by importing it from a URL or by rendering a PDF template, and files it in the personal list, the shared workspace list, or a specific space and folder. - **Create Agreement** Creates an AgreementGen document from an AgreementGen template, filling its variables and form fields by name. Records from a CRM or another system can be linked to it, so the document stays traceable back to the deal or contact it came from. - **Get Agreement File** Returns a signed download URL for an AgreementGen document, valid for 30 minutes after issue. ### Account and Workspace 3 - **Get User Information** Returns the identifier, name and email of the account the credential belongs to. The cheapest authenticated call in the API, which makes it the natural connection check. - **Get Workspace Information** Returns the workspace the credential is authorized for, with its owner, the current user's role in it, and how many members and spaces it holds. - **List Workspace Members** Returns a page of workspace members with each member's role and their joined and last active times. Used to resolve the right internal signer or approver before a request goes out. ## Frequently Asked Questions ### What can FlowRunner do with Lumin? FlowRunner agents can run Send Signature Request, Send Signature Request From Template, and Get Signature Request in Lumin, plus 16 more actions. ### Does connecting Lumin to FlowRunner require OAuth? No. Lumin connects to FlowRunner with an API key, no OAuth flow required. ### Can Lumin trigger a FlowRunner workflow automatically? Lumin doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Lumin?** This integration exposes Lumin 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/lumin. Site index: https://flowrunner.ai/llms.txt