A customer became a new lead
A returning contact was created as a lead because no one checked for the existing record.
BoldBellowsFormsite to Salesforce automation that picks the right object first
Formsite to Salesforce automation that upserts each completed result as the right object, once, through an External ID
Formsite to Salesforce automation upserts each result as the right lead, contact or case, once. Formsite connects natively to Salesforce, and that suits a simple lead. Real forms are not simple: one result may be a lead, an existing customer or a service case, and a returning contact must not become a new lead. BoldBellows stamps each result with its form directory, result ID, completion event and revision time, acts only once the form has completed the result, then picks the object, upserts through an External ID field and holds anything a validation or duplicate rule refuses.
View Pricing
One-off setup from $870
No monthly subscription
- Salesforce records from Formsite, upserted once
- Object chosen before fields are written
- External ID makes every resend an update
- Object decided first a written rule picks lead, contact, account or case
- Upsert by External ID a resend lands on the record that exists
- Rules respected a validation or duplicate refusal is held, not forced
- Revisions merged an edited result changes the same record
- Evidence kept Each decision stores the identifiers and timestamps behind it
- Fixed scope, fixed fee $870 opens the build, and every extra is priced on the page
Chapter 01 the wrong-object problem
A result filed as the wrong object costs more than a lost one
A Formsite result may come from a stranger, a customer with an open account or someone reporting a fault. Create a lead for all three and a customer is chased as a prospect while a service issue sits in a sales queue. Formsite then resends an edited result, and the same person gets a second lead.
A returning customer became a brand new Salesforce lead.
A fault filed as a sale
A service request was routed to sales and answered late.
The same lead twice
Someone corrected their answers and a second lead appeared.
Before
After
Before
- A retried delivery adds another record
- Every result becomes a lead
- A duplicate rule refusal is found by chance
After
- An External ID field holding the Formsite result ID links every record to its source
- A written rule picks the object before any field is set
- A refusal is held with the rule that caused it
Chapter 02 How it works
How a completed Formsite result becomes the right record in Salesforce
Three moves: decide whether it counts, locate the Salesforce record, then write and prove it.
Interpret the source state
The route reads the Formsite record behind the event and confirms the form result meets the documented rule.
Choose the object and the key
After completion is verified and the ID noted, the form and its answers decide whether the target is a lead, contact, account or case, and the External ID is prepared.
Upsert and prove
The upsert is sent, the record ID that comes back is saved on the result, and any refusal by a duplicate or validation rule is held with the reason.
What the platforms dictate
- Totals and payments settle in the form: Calculated totals and payment status are part of the result, so the route waits for the final values.
- Upsert with an External ID: Salesforce can create or update a record in one request using an External ID field, which is how a resent result changes one record instead of adding a second.
- Uncertain results: A missing confirmation starts a lookup in Salesforce by an External ID field holding the Formsite result ID; a new write is never the first response.
Chapter 03 What ships in the build
The parts of a Formsite to Salesforce build, and what each does
Start with Core, which admits events and claims identity; Scale then shapes the record; Stewardship checks Salesforce long after go-live.
Trigger gatekeeper
Lets only the agreed form results through and keeps a reason for every one it stops.
Stable identity ledger
Maintains the link between a Formsite record and its Salesforce twin, so updates land in the right place.
Payload trimmer
Cuts each Formsite payload down to the fields Salesforce needs before the record is prepared.
Object and field builder
Writes the right object with its mapped fields, record type and owner.
External ID matcher
Reads an External ID field holding the Formsite result ID on every event so a repeat is recognised before it writes.
Object and owner routing matrix
Picks the object and owner by looking at the form, a chosen answer and the amount.
Record register
Finds records where Salesforce has drifted from Formsite and shows how long they have been wrong.
Rule and field monitor
Notices a new validation rule, a removed field or a changed picklist before writes begin to fail.
Case register
Keeps evidence, status and next step for every Formsite record that could not be confirmed.
From Formsite to Salesforce to Formsite Salesforce duplicate prevention and Formsite Salesforce duplicate leads, one route. Related searches include Formsite Salesforce opportunity, Formsite to Salesforce sync, Formsite Salesforce workflow, Formsite Salesforce API integration, Formsite Salesforce lead capture, Formsite to Salesforce external id, Formsite to Salesforce Zapier, Formsite Salesforce integration, Formsite Salesforce automation, sync Formsite results to Salesforce, Formsite Salesforce contact create, Formsite submissions Salesforce mapping, Formsite Salesforce CRM sync, Formsite Salesforce case and create Salesforce lead from Formsite result.
Chapter 04 Who this fits
If you are among the nonprofits taking applications through Formsite, you may also need to manage customers in Salesforce
If Salesforce runs the business, each result must land as the right record exactly once.
Salesforce administrator
"Keep my data clean."
An External ID and a written object rule prevent duplicates.
Sales operations lead
"Route leads to the right owner."
Owner and queue rules are applied before the write.
Service manager
"Faults must not land in sales."
Service results become cases in the right queue.
Form administrator
"Trace a record back to its result."
Each record stores the Formsite result ID.
Revenue lead
"Count real pipeline."
Records appear once, with settled totals.
Founder
"I do not want a clean-up project."
Refusals are recorded with an owner, not lost.
Chapter 05 The options
Web-to-lead forms, a zap or an object-aware upsert route: choosing how Formsite reaches Salesforce
Each can create a lead. Only one decides the object and prevents a copy.
| Question | Web-to-lead forms | A no-code Formsite to Salesforce recipe | Our object-aware upsert route |
|---|---|---|---|
| What starts the work | Whoever is watching Formsite | Whatever the trigger allows | An approved form result, judged before any write |
| How identity is decided | Matched by eye | The title or a label | An External ID field holding the result ID |
| What reaches Salesforce | A pasted summary | A raw payload | The correct lead, contact, account or case, upserted once |
| After an uncertain result | Staff search Salesforce manually | A blind retry | Finds the record first, then decides |
Events arrive out of order
Delivery order is not trusted. Each Formsite event is ranked by its own time against the state already held in Salesforce.
A new validation or duplicate rule refuses a write the mapping once allowed
The record is held with the refusing rule named, so a person can fix the rule or the mapping. A search on an External ID field holding the Formsite result ID finds what exists; a comparison says whether it matches; the outcome is written down. Creation is allowed in one case alone: the Formsite record is confirmed missing.
Everything in this route hangs from an External ID field holding the Formsite result ID, so it is agreed before any mapping begins.
Interlude The price follows leads, contacts, accounts and cases
Build your Formsite to Salesforce quote, one choice at a time
Answer a few questions on scope and the total settles on a firm figure from $870.
View Pricing
One setup fee · Range shown first
Pricing
Build your Formsite to Salesforce price
Pick a package, answer three short questions about how Formsite data should reach Salesforce, and your price and turnaround move as you choose.
Chapter 06 The process
Six steps from form results to a CRM you can trust
Every step ends with something you can inspect: a map, a key, a test result or a signed note.
-
About 30 minutes
Decide the objects
We list which Formsite forms and answers produce leads, contacts, accounts or cases, and who owns each.
-
Access review
Approve access
The connections between Formsite and Salesforce are made with limited, revocable permissions.
-
Most of the project
Agree fields and rules
The External ID field, record types, owners, picklist values and duplicate handling are written down and signed off.
-
Before you review
Rehearse the failures
Duplicates, out-of-order events, blank values and timeouts are staged in a test area so the repairs are proven.
-
Handover day
Launch with notes
Once tests pass, the route goes live from a set checkpoint and the documentation is delivered.
-
About 30 minutes
Settle in
We watch the live route through its first cycle, compare both sides and tune thresholds where the data says to.
Chapter 07 Turnaround
How many days each package needs
Days are counted from approved access, not from Salesforce payment.
Core
4 to 7 business days
Scale
7 to 11 business days
Stewardship
11 to 16 business days
Chapter 08 Getting started
What you need to hand us
Read access to the Formsite data the route will use
Salesforce admin access, its objects, record types, rules and owners
Read access to the Formsite objects this route depends on
A plain-language list of the form results to include and exclude
The people who should be told when something fails
A time window in which testing can happen safely
Chapter 09 Trust
Scoped access, small payloads, and no changes to either tool
Think of it as a pipe with two labelled ends: Formsite on one side, Salesforce on the other, and nothing kept along the way.
Published interfaces only
Every request goes through the public interfaces of Formsite and Salesforce. No core file, theme or application code is touched.
Scoped, revocable access
Each connection has the narrowest permissions that work, recorded in the handover.
Data kept to the job
The record carries the values the business needs and no more; the rest of the Formsite record is never copied across.
Retries that cannot duplicate
Every repair starts from an External ID field holding the Formsite result ID and a read of Salesforce, so trying again is safe by construction.
Minimal logging
Diagnostic records are deliberately thin, so there is little to protect.
Full handover
There is no lock-in; the notes explain every setting we chose.
"The right object matters more than the right field, so the build decides lead, contact or case before it upserts." with Formsite to Salesforce
Steven GrratFounder, BoldBellows
Chapter 10 In their words
What BoldBellows clients say
Verified reviews from business owners who use BoldBellows automations every day, from marketing and data to support and operations.
AI Data Entry & Reporting Automation
We used to spend hours collecting data and building weekly reports by hand. BoldBellows automated all of it.
The reports are clean, visual and easy to read, and our managers rely on them for quick decisions. Human error is gone and our numbers are more accurate across the board.
AI CRM Automation
Our CRM was barely used because updating it by hand was tedious. BoldBellows automated data entry, tagging, segmentation and follow-ups.
Now the CRM is always up to date and our campaigns are far more accurate. It improved our whole sales pipeline.
AI Customer Journey Automation
We wanted a smoother path from first contact to purchase. BoldBellows built an AI system that guides each customer there automatically.
It sends personalized messages, recommends products and follows up at just the right moment. Customer retention has improved dramatically.
AI Document & Contract Automation
Onboarding was slow because we wrote every contract by hand. BoldBellows automated the lot: contracts, welcome emails and client setup.
What took 48 hours now takes under 10 minutes, and clients regularly tell us how professional it feels.
AI Social Comment & DM Automation
We get thousands of comments and messages every week. BoldBellows built an AI system that replies instantly, filters spam and surfaces the important ones.
Engagement is up and our page looks active around the clock. It’s like having a full social media team that never stops.
AI Voice Assistant
BoldBellows built a custom AI voice assistant for our customer hotline. It answers questions, books appointments and handles simple requests.
Customers love how fast it is, and our call-centre workload dropped dramatically. One of the smartest upgrades we’ve made.
AI Automation Partner
BoldBellows is hands-down the best AI automation partner we’ve worked with. Their systems are fast, reliable and built around how our business actually works.
Every automation they’ve delivered, from customer service to content, runs flawlessly. We’ve saved time, cut costs and grown faster than we expected.
AI Chatbot & Customer Support
BoldBellows built an AI support chatbot for our online boutique, and it has changed how we run the business. We used to have two full-time staff answering the same questions all day. Now the AI handles order tracking, product recommendations and even refund requests on its own.
What surprised me most is how natural it sounds. Customers compliment the ‘agent’ without realizing it’s AI. Our support workload dropped by 75% and customer satisfaction went up dramatically.
AI Content & Social Media Automation
Our marketing agency couldn’t keep up with content. BoldBellows set up an AI content engine that writes blog posts and captions and even designs our social media creatives.
It spots trends and suggests topics for us, so we stay ahead of competitors. We now produce three times the content with the same team, and engagement has soared. They didn’t just automate our workflow, they lifted our whole brand.
AI Lead Qualification & Sales Automation
Our sales team wasted hours chasing cold leads. BoldBellows built an AI lead-scoring system that reads behavior, email engagement and buying signals.
It filters out weak leads and sends personalized follow-ups automatically, so our team only talks to people who are ready to buy. Conversions rose 40% in the first month. It paid for itself straight away.
AI Video & Voice Automation
We publish product videos every week, and BoldBellows introduced us to AI video automation. The system writes the script, voices it and produces the finished video in minutes.
The quality is remarkable: professional voiceovers, clean visuals and smooth editing. Production time went from three days to under 30 minutes, and we scaled our video marketing without adding cost.
AI Email & Smart Inbox Management
Our inbox used to be chaos. BoldBellows built an AI email system that sorts messages, drafts replies and flags anything urgent.
It learns how we write and gets better every week. We reply faster and no longer miss important messages. It feels like having a personal assistant working around the clock.
AI Workflow Automation for Agencies
Running a digital agency with many clients was overwhelming. BoldBellows built one automation dashboard that tracks tasks, sends updates and creates client reports automatically.
Clients love the transparency and we love the time we get back. Productivity is up, and project delays have dropped to almost zero.
AI Booking & Scheduling Automation
Our coaching business needed a better way to schedule. BoldBellows automated all of it: bookings, reminders, cancellations and follow-ups.
No-shows fell by 60% and clients enjoy how smooth it is. It feels personal, not robotic. One of the best upgrades we’ve made.
AI Translation & Localisation
When we expanded abroad we needed fast, accurate translations. BoldBellows built an AI translation system that turns our content into several languages instantly.
The translations read naturally and suit each culture. We now serve customers in five new countries without hiring translators. BoldBellows helped us go global.
AI HR & Recruitment Automation
Our HR team was drowning in applications. BoldBellows automated screening, skills-based filtering and interview scheduling.
It saves us hours every week and means we only interview qualified people. Hiring is now faster, better organized and more professional.
AI Accounting & Invoice Automation
BoldBellows automated our whole invoicing process: creating invoices, sending reminders and tracking payments.
Late payments dropped sharply, and our accounting team finally has time for strategy instead of repetitive admin. Worth every penny.
AI E-commerce Listings Automation
BoldBellows automated our product listings. The AI writes descriptions, organizes photos and publishes listings across several marketplaces.
It even answers customer questions instantly. Our store looks more professional and sales have noticeably increased.
Chapter 11 Questions
Formsite and Salesforce: questions from administrators
Read these first; whatever is left can be asked in your quote request.
Can a Formsite to Salesforce Zapier integration retry safely?
For a record created for every completed result alone, a basic zap is enough. What it will not do is decide the object before the field, respect validation and duplicate rules or recover when an upsert answer is lost. This build covers exactly what a basic connector leaves open.
How do I create Salesforce leads from Formsite?
Formsite's webhook reaches the route, which picks the object, upserts through an External ID and stores the record ID it gets back.
Formsite connects to Salesforce natively. Why use this?
The native link suits a plain lead. This build chooses the object by rule, respects validation and duplicate rules, handles edited results and records every refusal.
Can one form create a Formsite lead, a contact or a case?
Yes. A written rule picks the object from the form, an answer given or an amount, so enquiries become leads and fault reports become cases.
Can an edited result create a second record?
No. Matching on the External ID updates the record that exists, so nothing is duplicated.
What if a validation or duplicate rule refuses the write?
The record is held with the rule named and a clear owner, and nothing is forced past your own controls.
What about a form someone saves for later?
It waits. Salesforce only receives the record once the form is submitted in full.
Is there a written map at handover on the Formsite to Salesforce route?
Yes, and it is part of every package: our Formsite Salesforce field mapping service assigns each Formsite field a destination, a type and a format for your sign-off before the build starts.
Can we combine several triggers?
Yes. The route is built around your logic, so it is a custom Formsite workflow for Salesforce with a Formsite Salesforce integration consultant's care behind it, from $870.
Will an update to Salesforce break the route on the Formsite to Salesforce route?
If the platforms change, the route degrades gracefully: it holds the affected record and flags it. Follow-up support once your review window ends is quoted on its own.
Give Salesforce records that are right the first time
We shape the route that will automate Formsite data to Salesforce and show the price first, from $870.
- From $870, paid once
- Right object
- Rules respected
- No monthly fee from us