Updated May 6, 2026
Quick answer:
A Salesforce form is a web form that captures data from a respondent and sends it directly into Salesforce as a new or updated record. Salesforce forms can power lead capture, customer onboarding, support cases, event registrations, donations, applications, surveys, and any other workflow that needs structured data inside Salesforce.
There are three common ways to build them: manual import with a tool like Data Loader, native Salesforce options like Web-to-Lead and Web-to-Case, or a dedicated Salesforce form builder. The first two are limited (Web-to-Lead caps at 500 submissions per 24 hours and supports only the Lead object, with no file uploads or field validation). A dedicated Salesforce form builder removes those limits and adds prefill, conditional logic, multi-object writes, and the data quality controls that downstream automation and Agentforce workflows depend on.
If you have been looking for a way to build Salesforce forms quickly, without writing code, this guide is for you.
You have several options for getting data into Salesforce, but they are not created equally. Some require ongoing manual work, others cannot connect data the way you need, and the native Salesforce options come with limitations that catch teams by surprise. The best Salesforce forms come from a flexible, integrated form builder that is built for the level of customization most organizations need by the time they outgrow Web-to-Lead.
Below, we walk through your options for getting data into Salesforce, why a dedicated form builder is usually the right answer, and how to actually build a Salesforce-connected form without code. Then we cover advanced capabilities, real-world use cases by industry, a library of tutorials, and the modern Agentforce / AI angle that did not exist when most Salesforce form guides were written.
What are Salesforce forms?
A Salesforce form is a web form that captures data from a respondent and writes it directly into Salesforce as a new or updated record. The form lives on your website, a customer portal, an email, or any other surface where you collect input, and the connection to Salesforce ensures the data shows up in the right object (Lead, Contact, Account, Case, Opportunity, or any custom object) without manual re-entry.
Salesforce forms power workflows like:
- Lead capture from your marketing site or paid landing pages.
- Customer onboarding and account setup forms.
- Support case intake.
- Event registration and webinar signups.
- Donation forms and grant applications.
- Patient intake, student applications, and program signups.
- Internal forms for non-Salesforce users to update CRM data.
The defining characteristic is the live connection to Salesforce. Anything that sends data into Salesforce in real time and on submission counts as a Salesforce form.
How to get data into Salesforce: 4 options compared
There are essentially four ways to get external data into Salesforce. The right one depends on the volume of data, how often you collect it, and how much customization the workflow requires.
Option 1: Manual entry
Someone in the organization opens the record in Salesforce and types the data in. This works for very low volume or one-off entries, but it is error-prone, time-consuming, and does not scale. Most teams quickly outgrow it.
Option 2: Bulk import with Data Loader
Salesforce’s Data Loader is a desktop application that bulk-imports CSV files into Salesforce, supporting up to 150 million records per job through Bulk API 2.0. It is useful when you receive a one-time data dump (for example, a CSV of attendees from a conference) or when you need to migrate data from a system that does not have a direct Salesforce integration. Data Loader is current as of Version 66.0, Spring ’26. It is a manual operation by design, and not a substitute for live data collection.
Option 3: Native Salesforce options (Web-to-Lead and Web-to-Case)
Salesforce offers two built-in HTML form generators: Web-to-Lead and Web-to-Case. Both let you generate a basic HTML form and embed it on a page so submissions create Lead or Case records automatically. They are easy to set up but come with significant limitations:
- Web-to-Lead caps at 500 submissions per 24-hour period; additional submissions queue.
- Files and attachments are not supported.
- There is no inline field validation. If a respondent enters bad data or skips a required field, the form fails silently and the admin gets an email.
- Web-to-Lead writes only to the Lead object. Web-to-Case writes only to the Case object. There is no cross-object logic, no custom-object support, and no AppExchange-object support.
- There is no native deduplication. Repeat submissions create duplicate records.
- Customization is limited. Branding, multi-page logic, conditional fields, and prefill are out of scope.
These tools work for the simplest possible use case (capture name and email, write to Lead) but most organizations hit one of the limitations above within weeks.
Option 4: A dedicated Salesforce form builder
A dedicated form builder is a third-party platform that connects to Salesforce through its API and gives you a drag-and-drop builder, prefill, conditional logic, multi-object writes, file uploads, validation, and so on. FormAssembly’s Salesforce integration is purpose-built for this category and is the option this guide focuses on. The tradeoff is a paid platform, but for any volume above the most basic Web-to-Lead use case, the productivity, data quality, and design control are usually worth it.
Web-to-Lead vs. a dedicated Salesforce form builder
Most teams considering a Salesforce form builder are weighing it against the native Web-to-Lead option. The table below summarizes the practical differences.
| Capability | Salesforce Web-to-Lead | Dedicated Salesforce form builder (FormAssembly) |
|---|---|---|
| Submission limit | 500 leads per 24-hour period; additional submissions queue. | No 500/day cap. Submissions scale with your plan. |
| File and attachment support | Not supported. | Supported. Attachments route directly into Salesforce Files. |
| Field validation and inline error messages | Not supported without custom JavaScript. Failed submissions silently email the admin. | Built-in validations and inline error messages, no code required. |
| Object support | Lead object only. | Any standard or custom object, including AppExchange objects, with full create/update logic. |
| Deduplication / update existing records | No native deduplication. | Conditional create-or-update logic. Match on any field; update existing records or create new ones. |
| Prefill from Salesforce | Not supported. | Native prefill connector pulls live Salesforce data into the form. |
| Customization and design | Limited. No drag-and-drop builder; manual HTML. | Drag-and-drop builder with templates, theming, conditional logic, and multi-page forms. |
| Data quality for Agentforce / AI | No structured validation layer; AI inherits whatever quality the form delivers. | Validation, normalization, and structured field mapping at the point of intake, the foundation for reliable AI workflows. |
The pattern: native options work for the simplest possible use cases, but break down quickly as soon as your forms need to do anything beyond capturing a name, email, and message and writing it to a Lead.
Why use a dedicated Salesforce form builder?
Beyond the comparison above, a dedicated form builder gives you four advantages that compound as your CRM matures.
Cleaner data at the point of intake
Validation, masking, conditional logic, and field-level requirements all run before the data ever touches Salesforce. That keeps your CRM clean by default rather than relying on downstream cleanup. As your team layers automation and AI on top of Salesforce, that data quality becomes a multiplier on everything else.
Multi-object and multi-step writes
Most real-world forms touch more than one object. A donation form might create or update an Account, a Contact, an Opportunity, and a custom Donation record in a single submission. A patient intake form might create a Contact, a Case, and several custom records linked together. Native Salesforce options cannot do this; a dedicated form builder can.
Prefill and live lookups
Sending a respondent a form that already knows who they are, what their account number is, and which products they own makes the experience faster and the data cleaner. Prefill from Salesforce and live lookups against Salesforce data are table stakes for any modern form builder.
Forms that update Salesforce, not just create records
Web-to-Lead can only create. A dedicated form builder can create, update, or conditionally do either based on whether the record already exists. That single capability eliminates a huge category of manual cleanup.
Advanced capabilities of a Salesforce form builder
Once you move past native Salesforce options, the question becomes what is actually possible. Below is a tour of the advanced capabilities a modern Salesforce form builder offers, anchored in what FormAssembly supports.
Send data to any standard or custom object
FormAssembly forms can write to any standard object (Lead, Contact, Account, Case, Opportunity, and so on), any custom object, and any object installed by an AppExchange app. This is the foundation of multi-object and complex CRM workflows.
Prefill forms with Salesforce data
With prefilled forms, respondents do not have to retype information you already have. The FormAssembly Prefill Connector pulls live Salesforce data into the form when it loads, which is especially valuable for renewals, account updates, customer onboarding, and any flow where the respondent is already known to the CRM.
Conditionally create or update records
Sometimes you want to update an existing record rather than create a new one (for example, a returning customer filling out a contact form should update their existing Contact, not create a duplicate). FormAssembly’s connectors support conditional create-or-update logic out of the box, with matching on any field you choose.
Send file uploads to Salesforce Files
FormAssembly forms accept file uploads and route them into Salesforce Files, mapped to the appropriate record. This works with the Files tab in Lightning Experience and supports common file types including PDFs, images, and documents.
Perform live lookups with dynamic picklists
FormAssembly’s Salesforce Dynamic Picklists feature lets a form perform live lookups against Salesforce based on what the respondent has entered. This is how you build forms that show, for example, the right list of accounts, the right list of products, or the right list of programs without hardcoding any of it.
Create Chatter posts (and connect to Slack)
FormAssembly can create Chatter posts when a form is submitted, useful for internal notifications. Note that Salesforce is publicly positioning Slack as the modern collaboration target, with Salesforce Channels rolling out across editions; Chatter remains supported but is no longer the strategic destination. If your team has migrated to Slack, configure your post-submit notifications to land there instead.
Use the FormAssembly AppExchange app
FormAssembly publishes a non-native AppExchange app. Non-native means the heavy lifting happens on FormAssembly’s infrastructure rather than inside your Salesforce org, which keeps your storage and platform limits clean while still giving you a deep, real-time integration.
How to build a Salesforce form without code
This is the four-step path from “I need a form” to “the form is live and writing data into Salesforce.” The example below builds a simple lead-capture form. More complex flows (multi-object, prefill, file upload) layer on the same foundation.
Step 1: Build the form in the form builder
Start in FormAssembly’s drag-and-drop form builder. You can begin from a blank canvas, a premade template, an existing form, or by importing fields directly from a Salesforce object using the Salesforce Import Tool. Add the fields you need, in the order you want them, and apply customizations:
- Required fields ensure you collect what you need to run the workflow.
- Conditional fields hide and reveal fields based on what the respondent has answered, so the form feels short.
- Multiple pages break long forms into shorter steps. The outline view makes it easy to manage every page and field in one place.
- Validations force data to match a specific format (email, phone, date, custom regex) before submission.
- Predefined content lets you drop in commonly used field groups (contact info, address, payment) without rebuilding them every time.
Step 2: Add a Salesforce connector
Once the form looks the way you want, head to the Connectors page. There are three connector types you can layer on:
- Salesforce Prefill Connector runs in the Form Opened step and pulls Salesforce data into the form before the respondent sees it.
- Salesforce Submit Connector runs in the Form Submitted step and sends data to Salesforce. This is the one most forms need.
- Salesforce Save Connector captures partial submissions when used with FormAssembly’s Save and Resume feature, so you can sync incomplete forms to Salesforce.
Step 3: Connect your account, pick an object, and map fields
- Connect your Salesforce account. A few clicks of OAuth and you are in. You can swap accounts later if needed.
- Pick the object you want the form to write to. Choose Lead, Contact, Account, Case, Opportunity, or any custom or AppExchange object. Required fields for that object are added to the connector automatically.
- Map fields. Drag form fields onto Salesforce fields, or accept the auto-mapping if your field names match. Add any non-required fields you also want to write.
Step 4: Save, test, and publish
Save the connector, submit a test entry, and verify the record landed in Salesforce the way you intended. From there, embed the form on your site, share it as a link, or publish it to a Salesforce Experience Cloud page. Most simple Salesforce lead-capture forms can be live in under an hour from start to finish.
Salesforce form use cases by industry
Salesforce forms apply to nearly every industry and team that uses the CRM. Below are common use cases by vertical.
Higher Education
Higher education institutions use Salesforce forms for application intake, prospective-student inquiries, scholarship and financial aid forms, alumni updates, and forms embedded inside Salesforce Experience Cloud portals for current students.
Financial Services
Financial institutions use Salesforce forms for client onboarding, KYC and account opening, loan applications, beneficiary updates, and intake for compliance workflows.
Healthcare
Healthcare providers use Salesforce forms for new-patient registration, intake, consent forms, referral routing, and outreach surveys. HIPAA-compliant infrastructure is essential.
Government
Government agencies use Salesforce forms for program signups, constituent service requests, license and permit applications, and reporting workflows.
Nonprofit
Nonprofits use Salesforce forms for donation intake (often into NPSP or NPC), grant applications, volunteer signups, and program enrollment.
Across every vertical, the pattern is the same: structured data needs to land cleanly inside Salesforce, often across multiple objects, with the right validation and audit controls.
Salesforce forms in the age of Agentforce
Salesforce forms used to be primarily about getting data in. In 2026, the more important framing is what happens after the data lands.
With Agentforce, Einstein, and the broader Salesforce AI stack, the value of every record in your CRM is a function of how clean, complete, and well-structured the data is. AI agents that are recommending next-best actions, scoring leads, drafting emails, or making decisions on behalf of a salesperson all inherit the quality of the data they are reading. Bad-quality form intake (missing fields, free-text where a picklist should be, duplicates) does not just clutter the CRM; it directly degrades the AI workflows downstream.
This is why having a “data intake layer for Salesforce” has become more important, not less, since Agentforce launched. A Salesforce form builder that validates, normalizes, deduplicates, and structures data at the point of intake is the cheapest and most leveraged way to make AI on top of Salesforce actually work.
If your team is preparing for Agentforce, evaluating any AI-assisted Salesforce workflow, or simply trying to get more out of your existing automation, the data layer is where the work starts. (For a deeper dive on this, see our Salesforce Connector upgrade FAQ.)
Salesforce form tutorials
Lead capture is the most common Salesforce form use case, but it is far from the only one. The tutorials below walk through specific, real-world configurations.
Update Salesforce records for non-Salesforce users
Need staff who don’t have Salesforce licenses to update Salesforce data? Web forms can match the layout of the relevant object and give those users a familiar interface for inputting information. Read the tutorial.
Send a prefilled Salesforce form
Pull live information from Salesforce into a form so respondents only have to confirm or update what is already there. Read the tutorial.
Set up new Accounts, Contacts, and Opportunities at once
Create multiple linked records in a single form submission. Read the tutorial.
Back up form submissions into Salesforce Notes
Configure FormAssembly to keep a Salesforce Note copy of every web form response for full audit visibility. Read the tutorial.
Create a Lead, or update a Contact if one already exists
Avoid duplicate Salesforce records by routing form submissions to the right object based on whether the person already exists. Read the tutorial.
Build client onboarding forms linked to Salesforce
Replace paper forms and long email chains with automated client onboarding flows. Read the tutorial.
Display Salesforce images on a web form
Pull product photos, profile pictures, or other images from Salesforce into your forms. Read the tutorial.
Quickly create a form to populate any Salesforce object
Use the Salesforce Import Tool to generate a form mapped to a specific object’s fields with a few clicks. Read the tutorial.
Search Salesforce records using multiple criteria
Implement multi-criteria search inside a form to help users locate the right Salesforce record before completing the submission. Read the tutorial.
How to evaluate a Salesforce form builder
As you compare Salesforce form builders, look beyond the marketing claims and pressure-test on these dimensions.
Drag-and-drop ease of use
The form builder should be approachable for both technical and non-technical users. If only the IT team can build forms, you have introduced a bottleneck. The right tool lets marketing, sales ops, support, and program teams build their own forms within sensible governance.
Connections to other systems
Salesforce is the anchor, but real workflows also touch payment processors (Stripe, PayPal, Authorize.Net), spreadsheets (Google Sheets, Excel), and document tools. A flexible form builder integrates cleanly with all of them so you do not need a different tool for every connection.
Authentication for restricted forms
FormAssembly Enterprise supports SAML, LDAP, Salesforce Experience Cloud authentication, and CAS, so you can restrict who can fill out which forms. This matters for student-only forms in higher ed, employee-only forms in financial services, and any internal-only workflow.
Compliance and security
HIPAA, GDPR, PCI DSS, SOC 2 Type II, and ISO 27001 are the certifications most enterprise Salesforce buyers should look for. Encryption in transit (TLS 1.2 or higher) and at rest (AES-256) should be baseline.
Data quality controls
Validation, deduplication, conditional logic, and structured field mapping are not optional once you have automation or AI running on top of your Salesforce data. Verify that the form builder handles these cleanly before they become your problem.
Frequently asked questions
What are Salesforce forms?
Salesforce forms are web forms that capture data from a respondent and write it directly into Salesforce as a new or updated record. They power lead capture, customer onboarding, support intake, event registration, donations, applications, and any other workflow where structured data needs to land in Salesforce.
How do I create a form in Salesforce without code?
Use a dedicated Salesforce form builder. The four steps are the same in any modern tool: build the form in a drag-and-drop builder, add a Salesforce connector, pick the object you want to write to and map fields, then save, test, and publish. With a tool like FormAssembly, a simple lead-capture form can be live in under an hour.
Is Salesforce Web-to-Lead enough for my team?
It depends on your volume and complexity. Web-to-Lead works for the simplest possible use case (capture name and email, write to the Lead object). It caps at 500 submissions per 24 hours, does not support file uploads, has no field validation, no deduplication, and only writes to the Lead object. If any of those constraints affect your workflow, you have outgrown Web-to-Lead.
What is the difference between Web-to-Lead and a dedicated Salesforce form builder?
Web-to-Lead is a built-in HTML form generator with strict limits on volume, customization, and object support. A dedicated form builder gives you a drag-and-drop builder, prefill, conditional logic, multi-object writes, file uploads, validation, and the data quality controls AI workflows depend on. The trade-off is paid software, but the productivity and data quality gains usually pay for the platform many times over.
Can a Salesforce form write to a custom object?
With Web-to-Lead, no. With a dedicated form builder like FormAssembly, yes. FormAssembly supports any standard object, any custom object, and any object installed by an AppExchange app, with full create-and-update logic across multiple objects in a single submission.
How do I prefill a Salesforce form with existing data?
Use a prefill connector. The connector runs when the form is loaded, queries Salesforce for the relevant record, and populates the form fields with the data already in the CRM. Common use cases include account renewals, customer updates, and any flow where the respondent is already known.
Are Salesforce forms ready for Agentforce and AI?
Only if the underlying data is. Agentforce and Salesforce AI workflows inherit the quality of the data sitting in your CRM, so the value of any AI work is bounded by the cleanliness of intake. A dedicated Salesforce form builder that validates, normalizes, and structures data at the point of capture is the most leveraged way to prepare your CRM for AI workflows.
Make Salesforce data work for you
Take the next step toward streamlined Salesforce data collection. Read more in our Salesforce + FormAssembly eBook, or request a free trial to build your first Salesforce-connected form today.
