--- title: "Qwilr Integration" description: "Automate proposals and quotes in Qwilr. Agents create branded pages from templates with merge-field substitutions, publish and update page settings, and read acceptance and analytics data to trigger downstream steps when a buyer views or accepts." url: https://flowrunner.ai/integrations/qwilr date_modified: 2026-08-04T10:04:16-07:00 --- # Qwilr [Documents](https://flowrunner.ai/integrations/category/documents-forms) Automate proposals and quotes in Qwilr. Agents create branded pages from templates with merge-field substitutions, publish and update page settings, and read acceptance and analytics data to trigger downstream steps when a buyer views or accepts. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 6 actions · API key · available [Qwilr website](https://qwilr.com/) · [Platform Documentation](https://api.qwilr.com/) · Capability data verified 2026-08-12 1. A deal reaches the proposal stage in the CRM with client, pricing, and start date on the record 2. List Templates resolves the right proposal template for the deal's product line 3. Create Page From Template generates the page unpublished, with client name, pricing, and dates filled through substitutions and the deal ID attached as metadata 4. The account executive previews the drafted page and approves publication, because the next click puts prices in front of a buyer 5. Update Page sets the published state and the shareable URL posts to the deal channel 6. A polling sweep calls Get Page and watches the viewedAt and accepted fields 7. First view pings the AE; acceptance posts to the revenue channel with acceptor and quote value, and the CRM stage advances ## What This Integration Enables Qwilr's core insight is that a proposal is a web page, and a web page can be instrumented. Unlike a PDF attachment, a Qwilr Page knows whether it was viewed, when it was accepted, who accepted it, and what the quote was worth. FlowRunner agents exploit both halves: they generate pages from templates the moment a deal earns one, filling merge fields from the CRM record, and they poll the acceptance and analytics data so the buyer's actions drive the pipeline instead of waiting for someone to ask. - Create branded proposals and quotes from templates, with substitutions for client name, pricing, and dates - Attach custom metadata at creation that echoes back in Qwilr's acceptance and view webhooks - Publish, unpublish, rename, re-tag, or refresh merge values on existing pages without rebuilding - Read acceptance state, acceptance time, acceptor, view status, and quote and order values per page - Filter the page inventory by tags and status for pipeline reconciliation and cleanup - Keep publication and deletion behind [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) review ### Without FlowRunner **Proposals are rebuilt, not reused**: Every deal gets a hand-assembled page, and the pricing table is last quarter's copy **Send it and go blind**: Nobody knows if the buyer opened the proposal until the buyer decides to say so **Acceptance is a screenshot**: The signed moment lives in an email thread while the CRM stage lags by days ### With FlowRunner **Proposals render from the deal record**: Template plus substitutions produce a branded page in seconds, tagged and traceable **Viewing and acceptance are workflow events**: Agents poll acceptance and analytics fields and move the deal the moment the buyer moves **Revenue reporting reads from the source**: Acceptor, timestamp, and quote value log automatically the day they happen ## Use Case Scenarios ### Deal stage to drafted proposal in one motion When a [HubSpot](https://flowrunner.ai/integrations/hubspot) deal hits the proposal stage, the agent pulls the deal's client name, line items, and close date, resolves the product line's template with List Templates, and calls Create Page From Template with those values as substitutions and the deal ID as metadata. The page is created unpublished and tagged with the deal's segment. The AE gets the preview link in [Slack](https://flowrunner.ai/integrations/slack), fixes anything the template could not know, and approves. Update Page flips it live. Proposal turnaround stops being a function of who is busy. ### The acceptance loop that moves the pipeline A sweep polls Get Page for every published, unaccepted page tagged to open deals. The first time viewedAt appears, the AE gets a quiet ping: the buyer is reading, today is the day to be available. When accepted flips true, the agent logs page name, acceptor, acceptance date, and quote value to [Google Sheets](https://flowrunner.ai/integrations/google-sheets) for revenue reporting, advances the CRM stage, and posts the win to the revenue channel. The gap between a buyer clicking accept and the company acting on it collapses to one polling interval. ### Proposal hygiene across a hundred open pages Quarterly, the agent walks List Pages and reconciles against the CRM: published pages tagged to deals that closed lost, drafts older than the pipeline's memory, quote values that no longer match the deal record. Stale drafts are flagged for deletion, priced pages tied to dead deals are proposed for unpublishing so their links stop offering last quarter's discount, and value mismatches route to the deal owner. A person approves each list, and the agent executes. The page inventory stays as clean as the pipeline claims to be. ## Human-in-Loop Highlight Publication is this connector's point of no return. The moment a page goes live, whether through Create Page From Template's publish option or Update Page's published state, its URL is an offer: prices, terms, and dates a buyer can view, screenshot, and accept. A substitution mapped from the wrong deal field publishes someone else's discount, and unpublishing after the buyer has seen it is a conversation, not a fix. So FlowRunner agents draft unpublished by default and hand the publish decision to the account executive with the preview attached. Delete Page carries the mirror risk: it permanently removes the page and disables its public link, and on an accepted page that link is the record of what was agreed, sometimes the one the buyer bookmarked. Deletion therefore runs only from an approved cleanup list, never inside a loop. The agent does the assembling and the watching; the person owns what the buyer sees. 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 ### Pages 5 - **List Pages** Lists the proposals and quotes in the account with each page's ID, name, published status, tags, and acceptance state, narrowable by tags or status, with cursor-based pagination. The inventory step behind reconciliation and cleanup. - **Get Page** Retrieves a single page by ID with name, published status, tags, and public URL, expanding acceptance and analytics data: accepted, acceptedAt, acceptedBy, viewedAt, and quote and order values, with optional metadata. The polling step that turns buyer behavior into workflow events. - **Create Page From Template** Creates a new page from a template, with a page name, substitutions filling the template's merge fields, optional immediate publication, tags, and custom metadata echoed back in webhooks. Returns the new page ID and shareable URL. The generation step behind proposal automation. - **Update Page** Updates settings on an existing page: publish or unpublish, rename, replace tags, or refresh substitution values, changing only the provided fields. The action that flips a reviewed draft live. - **Delete Page** Permanently deletes a page by ID and disables its public link. Cannot be undone, so it runs only against human-approved cleanup lists. ### Templates 1 - **List Templates** Lists the reusable, block-based templates in the account with each template's ID and name. Templates never go live on their own; they exist to feed Create Page From Template. ## Frequently Asked Questions ### What can FlowRunner do with Qwilr? FlowRunner agents can run List Pages, Get Page, and Create Page From Template in Qwilr, plus 3 more actions. ### Does connecting Qwilr to FlowRunner require OAuth? No. Qwilr connects to FlowRunner with an API key, no OAuth flow required. ### Can Qwilr trigger a FlowRunner workflow automatically? Qwilr doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Qwilr?** This integration exposes Qwilr 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/qwilr. Site index: https://flowrunner.ai/llms.txt