A customer became a new lead
The entry matched nothing because the email differed in case, and a duplicate lead was created.
BoldBellowsCognito Forms to Salesforce automation that chooses the right object
Cognito Forms to Salesforce automation that chooses the right object and upserts it by External ID, once
Cognito Forms to Salesforce automation files each entry as the right lead, contact or case, once. A Cognito Forms entry might be a new lead, an existing customer or a service case, and Salesforce treats each differently. BoldBellows notes the entry ID and the workflow event before anything else happens, waits for the form's calculations, conditions and payment to settle, then decides which sObject the entry belongs to, upserts it by a dedicated External ID, and answers any duplicate or validation rule rather than forcing past it.
View Pricing
One-off setup from $840
No monthly subscription
- Cognito Forms entries in Salesforce as one record each
- The right sObject chosen for each entry
- Duplicate and validation rules answered, never bypassed
- Right object lead, contact, account or case is chosen by your written rule
- External ID field a dedicated field, not an email, is the Salesforce record key
- Rules respected a duplicate or validation refusal is held for a person
- Existing records found a matching lead or contact is updated, not repeated
- Fixed scope What is built, tested and handed over is agreed before work begins
- Fixed scope, fixed fee $840 opens the build, and every extra is priced on the page
Chapter 01 the wrong-object problem
A form entry forced into the wrong object becomes a data-quality problem
Salesforce is strict. A returning customer who fills in your form should update a contact, not become a new lead; a support request should be a case, not a lead at all. Match by email alone and you get duplicates, orphaned cases and requests refused by a validation rule that nobody told you about.
A returning customer became a brand new lead.
A case became a lead
A support request was routed to the same object as sales enquiries.
A validation rule said no
A required field was missing on the entry and the whole request was refused.
Before
After
Before
- Anything the trigger matches is sent on
- Every entry becomes a lead
- A refused write is found by a salesperson for Cognito Forms to Salesforce
After
- A repeat finds its record through a dedicated External ID field
- Each entry is mapped to the right object by a written rule
- A rule refusal waits for a person, with the reason attached with Cognito Forms to Salesforce
Chapter 02 How it works
How an entry ends up as one Salesforce upsert
Nothing is written until the change is judged and the record has been looked for.
Admit only what counts
Each Cognito Forms event is verified and logged; anything outside the agreed scope is set aside with a reason.
Choose the object and the key
The entry ID is stored in the External ID field, the entry settles, and the form and its answers decide whether the target is a lead, contact, account or case.
Upsert and prove
With Cognito Forms to Salesforce in place, the upsert is sent, the returned record ID is stored, and a refusal by a duplicate or validation rule is held with the reason.
What the platforms dictate
- Incomplete entries are not final: An entry that is still incomplete is not treated as a submission, so partial answers never reach the destination.
- External ID upserts: Salesforce can create or update a record by matching an External ID through its sObject REST resource, which is what makes repeating an entry harmless.
- Retry rules: Retries are preceded by a check of Salesforce using a dedicated External ID field, so repeating a request cannot repeat its effect.
Chapter 03 What ships in the build
Everything in the Salesforce route, laid out
Launch is the front door. Route is the workshop. Govern is the inspection that keeps the route honest.
Event qualifier
Reads the Cognito Forms record and confirms it satisfies the trigger before Salesforce is touched.
Stable identity ledger
Maintains the link between a Cognito Forms record and its Salesforce twin, so updates land in the right place.
Mapping contract
Holds the agreed Cognito Forms-to-Salesforce field map as a versioned contract, not a habit.
sObject upsert builder
Prepares the Salesforce lead, contact, account or case with field values that fit the org.
External ID matcher
Separates new, changed and already handled records through a dedicated External ID field.
Object and owner routing
Picks the object and the owner for each entry from the form, a key answer or the amount.
CRM register
Runs a regular comparison between both sides and keeps the mismatches in view, on the Cognito Forms to Salesforce route.
Rule and permission monitor
Notices a new validation rule or a changed permission before writes start to fail.
Escalation list
Shows which exceptions are getting old and who has to act on them.
Whether it is Cognito Forms Salesforce duplicate leads, sync Cognito Forms entries to Salesforce or Cognito Forms Salesforce contact create, start here. Related searches include create Salesforce lead from Cognito Forms entry, Cognito Forms Salesforce integration, Cognito Forms webhook to Salesforce, Cognito Forms submissions Salesforce mapping, Cognito Forms to Salesforce Zapier, Cognito Forms Salesforce CRM sync, Cognito Forms Salesforce API integration, Cognito Forms to Salesforce sync, Cognito Forms Salesforce lead capture, Cognito Forms to Salesforce, Cognito Forms to Salesforce external id, Cognito Forms Salesforce workflow, Cognito Forms Salesforce automation, Cognito Forms Salesforce opportunity and Cognito Forms Salesforce case.
Chapter 04 Who this fits
Made for schools and clubs enrolling people with Cognito Forms that then work entries as leads, contacts and cases in Salesforce
If a form feeds Salesforce, the right object and a single key decide whether data is clean.
Sales operations lead
"I need one record per person."
The External ID makes every upsert land on the same Salesforce record.
Salesforce administrator
"Work inside my rules."
Duplicate and validation rules are answered, never bypassed, for this Cognito Forms to Salesforce route.
Service manager
"Support requests are not leads."
Entries from service forms become cases.
Revenue operations manager
"Why was that record rejected?"
Each refusal is held with the rule that raised it.
Form owner
"Where did that entry go?"
The entry ID is stored on every record.
Chief revenue officer
"I need to trust the pipeline."
Existing customers are updated, not recreated.
Chapter 05 The options
How Cognito Forms gets into Salesforce: CSV imports, a connector, or an object-aware CRM crosswalk
Each can create a lead. Only one can say whether it already exists as something else.
| Question | Importing CSVs | A template zap for Salesforce | BoldBellows build: object-aware crosswalk |
|---|---|---|---|
| What starts the work | A team member checks Cognito Forms | Any event the zap listens to | A form entry that matches your trigger definition |
| How identity is decided | Searched by name or address | Whatever field is mapped first | A dedicated External ID field holding the entry ID |
| What reaches Salesforce | The parts someone thought of | Fields forwarded unchecked | An upsert of the right object with relationships |
| After an uncertain result | It waits until somebody notices | Stops with an error email | Reads Salesforce by a dedicated External ID field before any rewrite |
An old change turns up late
A delayed Cognito Forms event is compared with what Salesforce already holds and is set aside if it would undo something newer.
Matching finds an existing Salesforce lead and contact or violates an org validation rule
A dedicated External ID field turns the question into a lookup, and the answer is one of four: nothing, right, wrong or unclear. Everything else is an update, a no-op or a case for a person.
Before fields or branches are discussed, a dedicated External ID field is fixed, because every later decision reads from it.
Interlude Cost is shaped by objects and External IDs
See the Cognito Forms to Salesforce price, then decide
Answer a few questions on scope and the total settles on a firm figure from $840.
View Pricing
One setup fee · Range shown first
Pricing
Build your Cognito Forms to Salesforce price
Pick a package, answer three short questions about how Cognito Forms data should reach Salesforce, and your price and turnaround move as you choose.
Chapter 06 The process
Six steps from form entries to the right Salesforce records
Six stages, one owner on your side, and a written output at the end of each.
-
About 30 minutes
Map entries to objects
We list which Cognito Forms entries become leads, contacts, accounts or cases in Salesforce and who owns each.
-
Access review
Approve access
The connections between Cognito Forms and Salesforce are made with limited, revocable permissions.
-
Most of the project
Agree keys and rules
With Cognito Forms to Salesforce in place, the External ID field, the matching and validation rules to respect, and the branches are recorded and approved.
-
Before you review
Try to make it fail
Every failure we can think of is tried against a test Salesforce, and the ones that matter become written repair steps.
-
Handover day
Launch with notes
Once tests pass, the route goes live from a set checkpoint and the documentation is delivered.
-
About 30 minutes
Thirty-day look-back
A review at the end of the first month covers volume, exceptions, retries and anything that drifted.
Chapter 07 Turnaround
How many days each package needs
Days are counted from approved access, not from Cognito Forms payment.
Launch
6 to 9 business days
Route
9 to 14 business days
Govern
14 to 20 business days
Chapter 08 Getting started
What you need to hand us
Read access to the Cognito Forms data the route will use
A Salesforce sandbox and an integration user with the object permissions needed
Cognito Forms credentials we can use for the agreed resources and events
The trigger you want: what must happen in Cognito Forms before anything is sent
A decision on which Cognito Forms values must never reach Salesforce
Confirmation of which environment is production
Chapter 09 Trust
Your data stays in its place, except what the map allows
Think of it as a pipe with two labelled ends: Cognito Forms on one side, Salesforce on the other, and nothing kept along the way.
Your tools stay as they are
We work with the supported connection points of Cognito Forms and Salesforce and leave the products exactly as you run them today.
Scoped, revocable access
Each connection has the narrowest permissions that work, recorded in the handover.
Less data, less exposure
Each field sent to Salesforce has a stated purpose. Sensitive values are excluded or masked before anything is written.
Look, compare, then act
An unclear write is settled by finding the record and comparing it with the intended values, not by sending again.
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."
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 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 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 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.
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.
Chapter 11 Questions
Cognito Forms, Salesforce and the right object: questions from sales teams
Read these first; whatever is left can be asked in your quote request.
Can a Cognito Forms to Salesforce Zapier integration retry safely?
A simple connector can give you a lead created for every entry. It will not choose the correct sObject, answer an existing lead or contact, or satisfy an org validation rule. These are the parts the build adds.
What keeps Cognito Forms entries from creating duplicate Salesforce records?
Store the Cognito entry ID in a dedicated External ID field. Every delivery then upserts the same record instead of creating a new one.
Can one form create a Cognito Forms lead, a contact or a case?
Yes. A written rule decides the object from the form, an answer or an amount, so enquiries become leads and service requests become cases.
What happens when the email already exists in Salesforce?
The route finds the existing Cognito Forms lead or contact and updates it according to your rule, rather than creating a duplicate.
What happens when a Salesforce validation rule blocks a record?
On this Cognito Forms to Salesforce route, the refusal is held with the rule that raised it and an owner, so a person decides and nothing is forced past your controls.
Is there a ready-made Cognito Forms to Salesforce connector?
Automation platforms can post an entry as a lead. They rarely choose between objects, wait for a payment to settle or handle a refusal, which is what this build adds.
Can Salesforce updates flow back to Cognito Forms?
Not in this scope: data flows from Cognito Forms into Salesforce only. A two-way flow is a separate engagement with its own acceptance criteria.
Is there a written map at handover in the Cognito Forms to Salesforce route?
Yes, and it is part of every package: our Cognito Forms Salesforce field mapping service assigns each Cognito Forms 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 Cognito Forms workflow for Salesforce with a Cognito Forms Salesforce integration consultant's care behind it, from $840.
Will an update to Salesforce break the 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 agree with your forms
We shape the route that will automate Cognito Forms data to Salesforce and show the price first, from $840.
- From $840, paid once
- Upserted by External ID
- Rules respected
- No monthly fee from us