Connecting Your Website to Salesforce. Notes From a Real Lead Pipeline
How I built a website lead pipeline that syncs to Salesforce for a B2B manufacturer. What breaks, what to log, and how to make sure no lead goes missing.
Sales says leads are missing. Marketing says the form is working. Both are kind of right.
The form sends. Something in between drops it. Nobody can prove where.
At Forza I built the lead pipeline that took website requests and synced them to Salesforce, on an Express and PostgreSQL backend. Here's how I approach that kind of build.
The website shouldn't talk straight to Salesforce
The easy way is to post the form directly to Salesforce. It works until it doesn't. Salesforce is down for a minute, a field gets renamed, a required value is missing. The lead is gone and the visitor saw a success message.
The pattern I use:
- The form posts to our own API. Express and Node.
- The API validates it and saves it to our own PostgreSQL database first.
- Then it syncs to Salesforce.
- If the sync fails, the lead is still saved and gets retried.
Your database is the source of truth. Salesforce is where sales works it.
Log every step
Accuracy and audit trails mattered at Forza, so I built it that way from day one. Every lead should have a record of when it came in, what was sent, what the CRM said back, and whether it worked.
When sales asks "did we get this lead?" the answer takes ten seconds. Not a week of guessing.
Map fields on purpose
Write down every form field and where it goes in Salesforce. Product interest, company, state, how they heard about you. Decide what happens when one is empty.
This is boring and it's where most of the bugs live.
Clean the data on the way in
Trim spaces. Normalize phone numbers and states. Catch obvious spam before it ever reaches sales. Dedupe repeat submissions.
Sales trusts the pipeline more when the junk doesn't show up.
Give people a way to see it
Not everyone needs a Salesforce seat. At Forza I built internal tools with Microsoft Azure SSO and role based access, so people sign in with the account they already have and only see what their role allows.
For Central Florida B2B teams
If you're a manufacturer or distributor in the Orlando area and you're using Salesforce, HubSpot, or any CRM, the same rules apply. Save it yourself first. Log everything. Map fields on purpose.
If leads are going missing and nobody can say where, email me. That's a problem I like.