A customer configures a product on your website at 10:30 p.m. on Thursday. They’ve configured it, seen the price, and submitted an inquiry. A sales rep logs into the CRM on Friday at 9:00 a.m. and sees… a notification that “someone submitted something via the form.” Zero context. No configuration details. The price isn’t visible either. A phone call at 10:15 a.m., the question “How can I help you?” The customer thinks: “I just sent you the finished configuration, and you’re asking, ‘What can I do?’”. A competitor that had a configurator integrated with its CRM called yesterday at 10:45 p.m. with a proposal.
What's more, most companies purchase a configurator thinking it will solve their sales chaos. It won't solve the problem...until leads from the configurator are imported into the CRM with full context, ready to be followed up on within hours, not days.
In this article: exactly what to integrate between the configurator and the CRM, what the integration architecture looks like, which CRMs (Pipedrive, HubSpot, Salesforce, Livespace, JSON Hub) are easy to integrate with and which are difficult, and five hidden pitfalls that can derail projects.
A configurator without CRM is just a quote generator. A configurator with CRM is a sales machine.
|
You have a configurator, but your leads are falling through the cracks? A 30-minute diagnostic consultation. We’ll show you where you’re losing leads and how to fix it. |
Schedule a call |
TL;DR · 30 SECONDS
- 5 integration workflows: Lead from the configurator → CRM, quote status → configurator (available variants), configuration history → 360° customer view, quote acceptance → order, product availability → variant lock.
- Architecture: Front-end configurator (Three.js, React) → Back-end API (REST/GraphQL) → CRM (Pipedrive, HubSpot, Salesforce, custom). Webhooks for real-time updates + a queue for reliability.
- 5 hidden pitfalls: 1) duplicate leads (the customer filled out the configurator twice); 2) lost leads due to API timeouts; 3) currency/price mismatches; 4) lack of attribution (you don’t know which configurator the lead came from); 5) CRM rate limits (Pipedrive ~1k requests/min).
- Without integration, the configurator generates a list of leads in Excel that no one can process within 24 hours, causing you to lose 50–70% of your inquiries.
Integration of the configurator with the CRM This is the automatic transfer of data between the product configurator and the CRM (Customer Relationship Management) system. It includes 5 data flows: lead from the configurator → CRM (customer completed = new deal), quote status → configurator (accepted? edited?), configuration history in the 360° customer view, acceptance → production order, inventory availability → blocking variants in the configurator. Without integration, the configurator is an isolated marketing tool.
Why integrate the configurator with the CRM at all?
First of all, before we get into the “how,” let’s focus on the “why.” This question comes up in every third conversation: “We have a configurator, and sales reps get email notifications—so why do we need a CRM?”
Answer: 91% of companies with 11 or more employees use CRM because an email notification isn’t a follow-up. It’s a reminder that a follow-up is needed. In between the two, there are five things that kill leads:
WHERE DO LEADS FROM THE CONFIGURATOR GO WITHOUT CRM?
- The email gets lost...the salesperson gets 200 emails a day, and the configurator notification gets pushed all the way to the bottom
- Lack of ownership, it's unclear which salesperson is responding; either two of them reply, or none do
- No follow-upIf a lead doesn't buy right away, they fall off the radar—no one remembers them two weeks later
- Lack of context in the conversation...the salesperson calls without any prior setup, and the customer has to explain everything from scratch
- Zero analytics, you don't know how many configurations resulted in deals, or what the conversion rate is
A configurator without CRM can generate leads. But convert leads into deals Only a system that captures the configuration, assigns a sales representative, ensures follow-up, escalates after 48 hours of inactivity, and reports on what works and what doesn't can do this.
Why integrate the configurator with the CRM? Five data flows
The "Configurator <> CRM" integration, on the other hand, is not just a single webhook. In fact, it consists of five workflows, each of which addresses a different issue.
FLOW 1 · CONFIGURATOR → CRM
New lead with full context
As a result, when a customer submits a configuration, a new lead automatically appears in the CRM with:
- Customer information (first name, email address, phone number, company name)
- Full product configuration (all selections, options, and parameters)
- The calculated price and the options considered but not selected
- Source tags (Google Ads / organic / Meta / referral)
- Timestamp + link to the PDF of the offer (if a PDF generator is integrated)
FLOW 2 · AUTOMATIC SALES REPRESENTATIVE ASSIGNMENT
Who responds to the lead?
First and foremost, round-robin (in turn), by geographic region, by industry, and by configuration value. Important: The lead is assigned to the CRM with a designated owner, it doesn't "go to the team." The CRM system ensures that two sales reps don't call the same customer and that a lead doesn't get lost between two teams.
FLOW 3 · FOLLOW-UP AUTOMATION
What happens when a customer remains silent
After 24 hours with no contact, a reminder is sent to the sales representative. After 72 hours, an automated email is sent to the customer (“We’ve reviewed your configuration and will respond to your questions”). Then, on the 7th day, the lead is escalated to a manager. Finally, after 30 days, the lead is added to a re-engagement campaign. Every step is logged in the CRM.
FLOW 4 · CRM → CONFIGURATOR
Retargeting users who abandon the configuration process
What’s more, the customer started the setup process but didn’t submit a request—that’s a hot lead. The CRM sends them an email or text message after two hours (“Finish the setup; the link takes you back to the same page”), and the marketing team launches a retargeting campaign on Meta and Google. Without integration, you’ll never see these leads—they disappear without a trace.
FLOW 5 · ANALYTICS
What actually works
Specifically, the CRM reports: how many configurations are generated per month, how many of those turn into deals, which product variant sells best, and how long it takes on average to close a deal from the configurator versus a cold call. Without this data, you lose 70% of the value generated by the configurator.
Integration architecture: what's going on behind the scenes
In technical terms, the "configurator <> CRM" integration can be implemented in three ways. The choice depends on the scale, budget, and the number of changes you make to your price list each month.
| Method | How it works | When to use | Cost |
| Webhook | Event-driven. The configurator sends a POST request to the CRM API with every query | A simple case, <100 leads/month, standard CRM | 0–5,000 PLN |
| Zapier/Make | Iterator without code. Zapier detects a new event and pushes it to the CRM | MVP, quick start, simple mapping | $50–$200/month |
| Custom middleware | The dedicated service performs two-way synchronization, handles conflicts, and implements retry logic | 100+ leads per month, two-way sync, custom logic | 15,000–40,000 PLN (one-time payment) |
| Native integration | Configurator and CRM = one system (e.g., JSON Hub) | Greenfield, a company without legacy CRM | 0 (built-in) |
In practice: For companies starting from scratch, we recommend a native solution (configurator + CRM in one). For companies with existing Pipedrive/Livespace / Salesforce setups, we recommend a webhook or middleware.
Five CRMs and how each one integrates
To sum up: there are four popular international CRM systems on the Polish market, plus one Polish one. Plus our own solution. Below is a ranking from “easiest” to “most difficult” in terms of integration with the configurator.
JSON Hub: Native Integration (Our Solution)
CATEGORY · ALL-IN-ONE
Native integration, a configurator, and CRM all in one
How we integrate: We do not integrate. JSON Hub It’s a platform where the configurator, CRM, quote generator, and dealer portal are all modules of the same system. No data mapping, no sync conflicts, no webhooks. The customer configures → the lead appears in the CRM → a PDF quote is generated automatically → the sales rep sees everything in a single dashboard.
For whom: Manufacturing companies with 50–500 employees, using Polish ERP systems (Comarch, Subiekt), with no legacy CRM.
Pipedrive: REST API, webhooks, quick integration
CATEGORY · GLOBAL CRM FOR SMB/MID-MARKET
REST API + Zapier + webhooks
How we integrate: Pipedrive is solid APIs and webhooks. For simple use cases. Zapier connects the configurator to Pipedrive in 30 minutes. For advanced use cases, custom middleware with bidirectional sync.
Common pitfalls: Pipedrive has separate fields for "organization" and "deal"; a lead from the configurator is one, and a deal is the other. You need to decide whether to create an Activity, a Lead, or a Deal.
HubSpot: marketing automation + Custom Objects
CATEGORY · CRM + MARKETING HUB
Robust API + marketing automation + forms
How we integrate: HubSpot has the most robust marketing automation; sending emails to customers who have abandoned their setup is built-in. It has a comprehensive API and solid webhooks. We can push the setup as a Custom Object in HubSpot.
Common pitfalls: HubSpot Free has limits on API calls and custom objects. If you have more than 500 leads per month, you’ll need the Starter or Professional plan (280–3,000 USD/month).
Livespace: Polish CRM with Polish support
CATEGORY · LOCAL POLISH CRM
Polish support + integration with GUS + API
How we integrate: Livespace has an API, documentation in Polish, support in Polish. Often the best choice for Polish manufacturing companies, it integrates with GUS, Polish ERP systems, and iFirma/wFirma invoicing.
Common pitfalls: Livespace has fewer pre-built integrations with global tools than HubSpot. If you need Salesforce-style customization, Livespace doesn't have Custom Objects like HubSpot does.
Salesforce: enterprise CRM with the most comprehensive API
CATEGORY · ENTERPRISE
The most feature-rich API, but also the most complicated
How we integrate: Salesforce has the most robust API, custom objects, formulas, and approval workflows. The integration is comprehensive, but requires a Salesforce admin. For enterprises with an existing Salesforce instance, it’s a perfect fit.
Common pitfalls: cost ($75–150 per user per month) + training + custom code required for unique business logic. For a manufacturing company with 10 salespeople, that’s overkill.
Five Hidden Pitfalls of Integration
In particular, we’re familiar with them because each one has caught us or our client at least once.
1. Data mapping: “telefon” vs “phone” vs “contact_phone”
For example, the configurator has a "phone" field, Pipedrive has "phone" (with the types mobile/work/home), and HubSpot has "phone" as a string. Without data mapping, you’ll either get confused or lose track of the structure. Solution: Field mapping document for the initial interview stagebefore anyone writes a single line of code.
2. Duplicate leads
The customer configured two variants of the same product in two separate sessions. Without deduplication in the CRM, you end up with two leads, and two sales reps calling the same customer. Solution: deduplication based on email and phone number, plus merge history configurations.
3. Sync conflicts in bidirectional sync
A sales rep updates contact information in the CRM, but in the meantime, the automation system sends out a new configuration using the old data. Who wins? Solution: a clear hierarchy of truth (“CRM wins” or “wins configurator” for specific fields), plus audit log.
4. GDPR and Marketing Consent
The customer configured the product. They only consented to commercial contact, not to marketing. Retargeting ads to them violates the GDPR. Solution: Marketing consent checkbox in the configurator + field in the CRM, plus an automatic opt-out if the customer selects "commercial only."
5. Latency: when a lead appears in the CRM
The webhook failed (e.g., the CRM was unavailable for 5 minutes). The lead was lost. Solution: Retry logic with exponential backoff + dead-letter queueso that no lead is lost due to a temporary outage.
How we do it at JSON Crew
First and foremost, every implementation of our configurator includes CRM integration as part of the MVP, not as an “optional add-on for Phase 2.” This is because a configurator without CRM is Problem #4 on our list of the 5 most common implementation failures, salespeople don't use it because the system doesn't integrate with their everyday work tools.
For customers who already have a CRM:
- Pipedrive/Livespace, our standard integrations, 1–2 weeks for implementation
- HubSpotCustom Objects + workflows, 2–3 weeks
- Salesforce, middleware + approval workflows, 3–4 weeks
- Our own CRM, custom middleware, 2–4 weeks depending on the client's API
However, for customers who don't have a CRM system or want to switch to a different one, we offer JSON Hub. No integration required, because the configurator and CRM are part of the same system. Ten manufacturing companies are already using it.
The questions we hear most often
“We already have a CRM. Do we need to switch?”
No, not if your CRM is used by sales reps and has an API. We can easily integrate with Pipedrive, HubSpot, Livespace, Salesforce, and Dynamics. Changing your CRM is a separate project; please make that decision independently of the configurator.
“We don’t have a CRM system. Where should we start?”
For a manufacturing company in Poland with 5–20 salespeople, we recommend Livespace (Polish, with Polish support) or JSON Hub (our solution, which integrates a configurator and CRM in one). For companies planning to expand internationally, we recommend Pipedrive or HubSpot.
“How long does it take to integrate the configurator with the CRM?”
From 30 minutes (Zapier, simple case) to 4 weeks (custom middleware, bidirectional sync with unique logic). Typical case for a manufacturing company: 1–2 weeks.
“What if the CRM goes down? Will we lose our leads?”
No, not if the integration is well-designed. Retry logic and a dead-letter queue catch every failure. The lead is sent to the CRM once the system is restored. We discussed this in the “hidden pitfalls” section above.
“How much does it cost?”
Integration only (without the configurator): Zapier setup – 2,000–5,000 PLN, custom middleware – 15,000–40,000 PLN. Details on implementing the configurator along with integration, in in a separate article about the configurator's prices.
How do I start integrating the configurator with the CRM?
|
Schedule a diagnostic call 30 minutes, free. Come with three answers: 1. What CRM do you use? (Or do you not have one?) 2. How many leads per month should flow through the integration? 3. Which fields are available in the configurator, and which ones are available in the CRM? |
Fill out the form |
To put it simply: webhooks, Zapier, middleware, or native integration via JSON Hub. Each solution has a different cost and scope. We’ll choose the one that makes the most sense for your scale.
P.S. The most common observation three months after implementing a well-integrated configurator: salespeople stop complaining that “CRM is extra work.” They start complaining when a lead comes to them without configuration, because they’ve already gotten used to having the context provided. This is the moment when the integration has paid off psychologically—sales reps want the system; they don’t hate it.
Frequently Asked Questions
How do I integrate the configurator with the CRM?
Three options: 1) Webhook → CRM API (real-time, most popular, requires ~3–5 days of developer work); 2) Zapier / Make / n8n as an intermediary (no-code, ~1 day, but limited to standard fields); 3) Custom backend → CRM API (most powerful, integrates 5 workflows, 1–2 weeks of work). For most B2B companies, the optimal solution is a webhook + queue (Redis, AWS SQS) for reliability + Zapier as a fallback for edge cases.
Why integrate the configurator with the CRM?
Five reasons: 1) automatic lead creation (each completion of the configurator = a new deal in CRM); 2) 360° customer view (the salesperson sees what variants the customer has configured); 3) the offer status returns to the configurator (the customer sees whether his quote has been accepted); 4) blocking of variants on the configurator side when the warehouse is empty; 5) attribution of marketing campaigns (where the lead comes from). Without integration, the configurator = a list of leads in Excel that no one handles within 24 hours, you lose 50-70% of inquiries.
Webhook vs. API: Which is better for integrating a configurator with a CRM?
Webhook (push): The configurator sends data to the CRM when a lead is created. Best for real-time deal creation. API (pull). The CRM queries the configurator for new data. Better for synchronizing statuses and variants. In practice, most integrations use both: a webhook from the configurator to the CRM (lead, quote) + an API from the CRM to the configurator (status, availability). Add a queue (Redis, AWS SQS) between them for retries in case of a timeout.
How much does it cost to integrate the configurator with the CRM?
It depends on the number of workflows and the CRM system. Lead→CRM webhook (1 workflow): ~3–5 developer days = 3,000–5,000 PLN. Full integration of 5 workflows (lead, status, history, approval, availability): 1–2 weeks = 8,000–15,000 PLN. Custom backend with queue + monitoring: 2–3 weeks = PLN 15,000–25,000. Plus integration testing and maintenance. With a ready-made tool like Zapier: ~PLN 500/month SaaS, but only basic fields.
Does every configurator integrate with every CRM?
In theory, yes (every configuration tool can expose an API, and every CRM has its own API). In practice: Pipedrive, HubSpot, Salesforce, and Zoho have good public APIs and plugin libraries, with standard integration. Polish CRMs (Livespace, SalesManago) have APIs, but the documentation is lacking, and there are no plugins. Custom CRMs or Comarch/Asseco require a tailored approach, sometimes involving reverse engineering. Old, on-premise CRMs without a REST API (rare, but it happens) require database integration, which is time-consuming and costly.
What happens to the lead after the configurator is filled out?
In a well-integrated system: 1) the configurator sends a webhook to the backend; 2) the backend saves the configuration to the database (including attribution, UTM, and source); 3) it creates a deal in the CRM with all the data (customer, variants, price, description); 4) it sends a confirmation email to the customer; 5) it notifies the sales rep via Slack/email; 6) the deal moves into the “New Leads, Contact Within 24 Hours” sales funnel. In a poorly integrated system: the data ends up in Excel, someone checks it once a day, the customer doesn’t receive any feedback for 3 days, and buys elsewhere.
About the author
Jędrzej SiewierskiCEO and co-founder JSON CrewSince 2024, he has been building product configurators for B2B companies (manufacturers of agricultural machinery, hunting weapons, modular homes, and IoT electronics) as well as JSON Hub, his own SaaS platform that integrates CRM, automated quoting, and project management. Co-author of a digital sales transformation methodology: shortening the path from interest to purchase through a configurator + automated quoting + CRM. Stack: Next.js, Three.js, Nest.js, React Native. Contact: contact@jsoncrew.com · LinkedIn.
See configurators with automatic pricing and integration logic
The configurator only makes sense when integrated with the rest of the process—CRM, ERP, and quote generation. Check out the working demo (the part with automatic PDF pricing, exactly as in integration with CRM/ERP) — Click here to try it out without logging in:
- 3D Weapon Configurator — The GLB model in the browser, accessories, body finish. A benchmark for firearms and accessories manufacturers.
- 3D Car Configurator — paint, wheels, spoilers, packages. The UX found in BMWs, Audis, and Skodas—the benchmark for the automotive industry.
- Modular Home Configurator — structure, transportation, systems, automatic PDF pricing. Mechanics for modular home manufacturers.
- Metal Garage Configurator — Step-by-step selection of design, size, and gate. Implementation takes approximately 4 weeks. Demand for this product in the Polish market has increased by 160% year-over-year.
- Configurator cost estimator — Cost estimates in PLN for your business in 3 minutes. EASY/MID/HARD + 3-year TCO + ROI calculation.
