How to Build a Salesforce Form That Creates and Updates Records

Noca Forms: AI form builder you can set up from a plain-language prompt, connected to your CRM, ERP and other systems. Free plan available.

To build a Salesforce form that creates and updates records, connect your form builder to Salesforce, design the form, map each field to a Salesforce object, and set a matching rule (such as email) that decides whether to update an existing record or create a new one. Add approvals or signatures where needed, then test with real data.

What you’ll build

In this guide you will build a customer onboarding form in Noca that:

  1. Looks up the customer’s existing Account in Salesforce, or creates one if it does not exist.
  2. Creates or updates the primary Contact, matched by email.
  3. Creates a related Onboarding record (a custom object) with the customer’s answers.
  4. Routes high-value onboardings for approval.
  5. Generates a welcome pack or service agreement and collects a signature.
  6. Updates the Account status in Salesforce when everything is complete.

If you are new to the concept, read What Is an AI Form Builder? first.

Prerequisites

  • A Salesforce org and an integration user with create, read and edit access to Account, Contact and any custom objects you use.
  • A Noca account with the Salesforce integration.
  • A list of the fields you need and which Salesforce field each one maps to.
  • Agreement on the matching rule: which field identifies an existing record (email, account number or a Salesforce ID).

How to build the form, step by step

Step 1: Connect Salesforce

Add the Salesforce integration in Noca and authenticate with your integration user. Confirm that the objects and fields you need are visible. Limiting the integration user’s permissions to those objects keeps the form from writing anywhere it should not.

Step 2: Build the form

Open the Noca AI Form Builder and describe what you need, for example: “A customer onboarding form with company name, website, billing address, primary contact name, email and phone, number of users, preferred start date and a signature. If number of users is over 500, ask for the procurement contact.” Noca drafts the fields, validation and conditional logic. Adjust labels and order in the visual editor.

Useful touches:

  • Use dropdowns whose options match your Salesforce picklist values exactly, so every answer is a valid option.
  • Where possible, send the form only after you know who the customer is, so the workflow can look up their Account instead of asking for everything again.
  • Add validation for email, phone and dates to keep bad data out of Salesforce.

Step 3: Map fields and set create-or-update rules

Map each form field to its Salesforce field. Then set the logic for each object:

  • Account: search by website domain or account number. If found, update the billing address; if not, create a new Account.
  • Contact: search by email within that Account. Update phone and title if found, or create the Contact and link it to the Account.
  • Onboarding record: always create a new record and link it to both the Account and Contact.

Decide which fields a form may overwrite. For example, the form can update the phone number but should never overwrite the Account Owner.

Step 4: Add approval, document and signature steps

Add an approval step for onboardings above a threshold, such as more than 500 users, routed to the account executive. Then generate a document from a Word template, such as a service agreement filled with the form answers and Salesforce data, and send it for e-signature. If you are comparing document tools for this step, see Best AI Document Generation Software in 2027.

Step 5: Update Salesforce

When the agreement is signed, update the system of record:

  • Attach the signed PDF to the Account.
  • Set the Account’s onboarding status to Active.
  • Create a task for the customer success manager.
  • Post a message to Slack or Microsoft Teams.

Step 6: Test

Test three paths in a sandbox or with test records: a brand-new customer (everything is created), an existing customer with a known email (records are updated, not duplicated), and an existing Account with a new contact (a Contact is added). Check required fields, picklist values, the approval threshold and the signed file location.

Example scenario: partner onboarding without duplicates

Illustrative scenario based on a typical setup, not a specific Noca customer.

A B2B company onboarded partners through a generic web form that dumped submissions into email. Admins retyped each one into Salesforce and often created duplicate Accounts. With a Noca form that matches by domain and email, returning partners update their existing records, new partners get clean Accounts and Contacts, large partners are approved by the channel manager, and the signed partner agreement is attached to the Account automatically.

Common mistakes to avoid

  • No matching rule. Without one, every submission creates a new record and duplicates pile up.
  • Free-text fields for picklists. Use dropdowns tied to Salesforce values to avoid failed writes.
  • Overwriting protected fields. Decide explicitly which fields the form may change.
  • Admin-level integration users. Grant only the access the form needs.
  • Testing only the happy path. Test new, existing and partially existing records.

Next steps

Once this form works, reuse the pattern for lead capture, case intake and renewal requests. To compare tools, see Best AI Form Builders in 2027 and Best Salesforce Form Builders in 2027. If documents are a big part of your Salesforce process, our list of Conga Composer alternatives covers the generation side.

Frequently asked questions

Can a form update existing Salesforce records instead of creating new ones?

Yes. Set a matching rule, such as email or account number, so the form searches Salesforce first. If a match is found the record is updated, and if not, a new record is created.

Can one form create records in several Salesforce objects?

Yes. A single submission can create or update an Account, a Contact and a custom object, and link them together. Map each field to the right object and set the order of operations.

How do I prevent duplicate records from form submissions?

Use a reliable matching field, such as email for Contacts and domain or account number for Accounts. Combine it with validation so the matching field is always present and correctly formatted.

Can a Salesforce form include an e-signature?

Yes. Noca supports signature capture in the form itself and full e-signature workflows for generated documents. The signed copy can be attached back to the Salesforce record.

Do I need Salesforce Experience Cloud to share forms externally?

Not with an external form builder. Customers fill in the form outside Salesforce, and the integration writes the data to Salesforce without them ever logging in to Salesforce.

What permissions does the Salesforce integration user need?

It needs create, read and edit access to every object and field the form writes to, and read access to anything it looks up. Avoid using an administrator account, so the form cannot change data it should not touch.

Back to top