--- title: "Stylish Cost Calculator Integration" description: "Stylish Cost Calculator is a WordPress quote and cost calculator plugin. Agents read the calculators defined on a site, pull the quote submissions they collect, and pick up each new quote in real time." url: https://flowrunner.ai/integrations/stylish-cost-calculator date_modified: 2026-09-04T19:20:34-07:00 --- # Stylish Cost Calculator [Forms](https://flowrunner.ai/integrations/category/documents-forms) Stylish Cost Calculator is a WordPress quote and cost calculator plugin. Agents read the calculators defined on a site, pull the quote submissions they collect, and pick up each new quote in real time. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 1 trigger · 7 actions · API key · available [Stylish Cost Calculator website](https://stylishcostcalculator.com/) · [Platform Documentation](https://help.stylishcostcalculator.com/en/category/integrations-1ac70xi/) · Capability data verified 2026-08-26 1. On New Quote fires when a visitor submits a quote request against the calculator 2. The agent parses the submitted fields and the calculated quote, which arrive as JSON held as text 3. Get Calculator Schema maps those fields back onto their labels so the configuration is readable 4. The agent compares the total against the range this calculator normally produces 5. The lead opens in the CRM with the chosen options and the quoted figure attached 6. The quote posts to the sales channel with the exact configuration the visitor picked 7. A rep decides whether an out of range total is honored or re-quoted before anyone replies ## What This Integration Enables Stylish Cost Calculator is not a hosted service with an API you sign into. It is a WordPress plugin, and every call this connector makes goes to the customer's own site through the plugin's single integration endpoint. That matters more than it sounds. There is no vendor middle layer, no per account rate limit, and no place other than your own WordPress install where these quotes exist. FlowRunner agents read the calculators defined on the site, pull the field schema that explains what a submission's values mean, read the stored quote submissions, and subscribe to new quotes as they land. The write surface is deliberately narrow: this connector cannot change a price, edit a calculator, or update a quote's status. Everything consequential therefore happens one system later, on a number the visitor has already seen on screen. That is where FlowRunner's [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) step belongs, and it is also why the two operations that do change something on the site, the webhook subscription pair, deserve more care than their size suggests. ### Without FlowRunner **Quotes arrive as email**: The calculator emails a notification, and the pipeline lives in whoever opened it first **Configuration lost in translation**: The rep sees a total but not the options that produced it, so the callback starts from scratch **Stale lead statuses**: The plugin's own pipeline states drift because updating them is a second job in a second admin ### With FlowRunner **Quotes arrive as records**: Each submission becomes a CRM lead with its fields mapped through the calculator's schema **The configuration travels with the number**: The rep opens the lead already knowing what the visitor selected and what it priced at **Odd totals are caught before contact**: A figure outside the usual range reaches a person before it reaches the customer ## Use Case Scenarios ### A quote request becomes a qualified lead A visitor configures a job on the calculator and submits. On New Quote fires with the submitted fields and the calculated total. The agent calls Get Calculator Schema so it can turn raw field values into the labels the sales team recognizes, then opens the lead in [HubSpot](https://flowrunner.ai/integrations/hubspot) or [Pipedrive](https://flowrunner.ai/integrations/pipedrive) with the configuration written into the record. The quote posts into the [Slack](https://flowrunner.ai/integrations/slack) channel where the duty rep is watching. The rep opens the lead already knowing what was asked for and what it priced at. ### The nightly reconciliation between the site and the pipeline The plugin keeps its own lead pipeline on each quote row, with states running from new through qualified and assigned to closed. On a schedule, the agent calls List Quotes for each calculator, compares those rows against the CRM, and reports the ones that exist on the [WordPress](https://flowrunner.ai/integrations/wordpress) site but never became a lead, usually because a delivery was missed while the site was down. The agent cannot change the plugin's status, so the reconciliation report is the output: a short list of quote ids that need a person, appended to [Google Sheets](https://flowrunner.ai/integrations/google-sheets) and posted to the channel. ### Wiring a new calculator without breaking the old automation A marketing site adds a second calculator for a new service line. The agent runs Verify Connection, calls List Calculators to resolve the new numeric id, reads Get Calculator Schema to build the field mapping, and prepares the subscription. It does not register it yet. The plugin gives each calculator exactly one webhook slot per platform, and this connector cannot read what is currently in that slot, so the agent presents what it is about to do and waits. ## Human-in-Loop Highlight Subscribe Webhook looks like setup and behaves like a takeover. The vendor is explicit that each calculator holds one webhook registration per platform, so pointing a calculator's slot at FlowRunner replaces whatever address was in it, including a live automation the agency built last year. This connector has no operation that reads the current value first, and Delete Webhook clears the slot rather than restoring what was there, so the previous URL is not recoverable from here. The failure is quiet: quotes keep arriving on the site, the old automation simply stops receiving them, and nobody notices until a week of leads is missing. So the agent stops: "Calculator 4, Kitchen Remodel Estimate, is about to have its webhook slot pointed at FlowRunner. If a Make scenario is registered there today, it will stop receiving quotes and I cannot read or restore the address it holds. Confirm the takeover, or name a different calculator?" The sales ops owner checks the plugin's integrations screen and answers. The agent does the discovery and the mapping. The step that can silently unhook a live site waits for a person. 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 7 actions ### Connection 1 - **Verify Connection** Calls the plugin's integration endpoint with no method selected, which is the authentication check the vendor documents. Worth running first, because a site without the premium plugin answers with its ordinary homepage rather than an error. ### Calculators 2 - **List Calculators** Returns every calculator defined on the connected WordPress site with its numeric id. The id every quote and webhook operation needs. - **Get Calculator Schema** Returns one calculator's field schema: the sections, elements, and quote form fields a submission will carry. Used to map an incoming quote onto the fields of the CRM that receives it. ### Quotes 1 - **List Quotes** Returns the stored quote submissions for one calculator, each carrying the submitted fields, the calculated quote, and the plugin's own pipeline status. The endpoint offers no server side filter, so narrowing happens after the response arrives. ### Webhooks 2 - **Subscribe Webhook** Registers a callback URL the plugin posts to whenever a new quote is submitted against a calculator. A calculator holds one slot per platform, which is why this page's human gate exists. - **Delete Webhook** Removes the subscription registered against a calculator so the plugin stops posting new quotes to it. The calculator id doubles as the webhook id, so there is no separate handle to hold onto. ### Advanced 1 - **Send Custom Request** Calls the plugin's integration endpoint with query parameters of your choosing, on top of the action and key the connection already supplies. The escape hatch for plugin options this connector does not name. ## Triggers 1 triggers ### Event Triggers 1 - **On New Quote** Fires when a visitor submits a quote request against the chosen calculator, delivering the submitted form fields and the calculated quote. FlowRunner registers the subscription when the flow starts and removes it when the flow stops. Several FlowRunner triggers can watch the same calculator safely, because they share one registration and each delivery is matched back to all of them. ## Frequently Asked Questions ### What can FlowRunner do with Stylish Cost Calculator? FlowRunner agents can run Verify Connection, List Calculators, and Get Calculator Schema in Stylish Cost Calculator, plus 4 more actions. ### Does connecting Stylish Cost Calculator to FlowRunner require OAuth? No. Stylish Cost Calculator connects to FlowRunner with an API key, no OAuth flow required. ### Can Stylish Cost Calculator trigger a FlowRunner workflow automatically? Yes. Stylish Cost Calculator supports 1 trigger that can start a FlowRunner workflow automatically. **Work at Stylish Cost Calculator?** This integration exposes Stylish Cost Calculator 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/stylish-cost-calculator. Site index: https://flowrunner.ai/llms.txt