EV Company, Web app / Integration
Leads from Webflow straight into Salesforce
A forms engine, TCO calculator and partner portal for EV Company's new Webflow site. Every request lands in Salesforce automatically.
- Webflow
- Salesforce
- Node.js
- TypeScript
15
forms connected to Salesforce
- Client
- EV Company
- Role
- Architecture, back end, integrations
- Period
- 2026, ongoing
- Platform
- Webflow + Node.js API
The context
EV Company supplies EV chargers and charging solutions to businesses and consumers. When they moved to a new website on Webflow, everything that came in, from a contact question to a partner quote, had to end up in Salesforce, where sales and customer service work with it.
The problem
Webflow forms don't talk to Salesforce on their own, and every request has different fields: a SIM swap needs something else than a site survey or a quote through a partner. EV Company also wanted to give business customers an estimate of the total cost of ownership of a charger, without exposing prices and margins in the browser.
Core problem
A lead that gets lost on the way is revenue nobody sees. The integration didn't just have to work, it had to notice when something went wrong.
Our approach
We built one API behind the site instead of a separate integration per form. Forms are described in configuration and handled by the same engine.
- 1
A configurable forms engine with fifteen forms, from contact and advice calls to site surveys, job applications and partner quotes, with steps, attachments and saved drafts.
- 2
A TCO calculator that runs on the server, so prices, subsidies and margins never reach the browser.
- 3
A safety net: every submission is stored safely first and then sent to Salesforce. If that fails, the API retries automatically and sends an alert.
What we built
A Node.js API in TypeScript that serves scripts to the Webflow site, validates submissions and passes them on to Salesforce. Partners get their own portal with their product range from the Webflow CMS. An internal backup app shows what came in, even when Salesforce was briefly unreachable. Spam is kept out with Cloudflare Turnstile, a honeypot and timing checks.
Results
Every request from the new site ends up in Salesforce, with attachments and the right fields per form. A new form or field is a matter of configuration.
Facing a similar problem?
Tell us what you're running into and we'll show you how we would approach it.
