How to Connect Forms to Salesforce with FormAssembly

FormAssembly’s Salesforce Connector makes it easy to push and pull data between your forms and Salesforce – no custom code required. In this step-by-step guide, we’ll walk through how to configure a form submitted connector that updates or creates Salesforce records when someone submits your form.

Step 1: Open the Connector Configuration Page

You can access the connector setup from two places:

Option A: From the Forms List

  1. Log into your FormAssembly account.
  2. Find the form you want to edit.
  3. Hover over the Configure button and click Connectors.

Option B: From the Form Builder

  1. Click Build on your form.
  2. In the left-hand sidebar, click Connectors.

Both paths will take you to the Connector Timeline, where you can manage when your connectors run.

Step 2: Add a Form Submitted Connector

  1. In the Form Submitted section of the connector timeline, click the + icon.
  2. Choose Salesforce from the list of connector options.
  3. Click Configure to begin setup.

Step 3: Authenticate the Salesforce Connection

If you’ve already connected your account, your username will appear. Click it to authenticate the connector.

If not, you’ll see three authentication options:

  • Connect to Salesforce (Production)
  • Connect to Salesforce Sandbox
  • Use a Custom Domain

Choose the option that matches your Salesforce environment.

Note: Every new connector is disabled by default. Be sure to enable it before moving on. Also, FormAssembly does not auto-save changes, so click “Save” often.

Step 4: Choose Your First Object

Click “Select your first object” to define what the connector should do.

Choose from:

  • Create a new record
  • Update an existing record
  • Look up a record

For this example, we’ll select “Update an existing Contact record.”

Step 5: Set Lookup Criteria

Define how FormAssembly should match existing Salesforce records.

Example:

  • Lookup field: Email
  • Operator: Equals
  • Form field: Email (as entered by the respondent)

Then, configure the behavior:

  • If no match is found: Create a new record, skip, or end execution.
  • If one match is found: Update that record (default behavior).
  • If multiple matches are found: Choose whether to update the most recent, create a new one, or end execution.

Step 6: Map Your Form Fields to Salesforce Fields

Use the Field Mapping section to decide which Salesforce fields to update and where the values should come from.

You can:

  • Map fields from your form (e.g., update Last Name with data from a Text Input).
  • Enter static values using formulas or text (e.g., hard-code an Owner ID).

Step 7: Add Additional Connector Steps (If Needed)

You can chain multiple actions together in one connector.

Examples:

  • Create a Case record for the Contact.
  • Look up an Account related to the Contact.

To reorder connector steps:

  1. Click Reorder Objects.
  2. Drag and drop the steps into your preferred sequence.
  3. Click Done Reordering and Save.

Step 8: Use Helpful Management Features

FormAssembly offers tools to keep your connector organized:

  • Copy Object – Duplicate a step to reuse and modify.
  • Remove Object – Delete steps that are no longer needed.
  • Add Comments – Label each step with notes to clarify its purpose, especially helpful for team collaboration or complex builds.

Step 9: Explore Additional Connector Options

At the bottom of the connector configuration page, you’ll find advanced options to further customize connector behavior. These include logic for conditions, errors, and more. 

Step 10: Save and Test

Once everything is configured:

  1. Save your changes (remember: no autosave).
  2. Test the form to confirm your Salesforce data flows as expected.

Pro Tip: Review connector behavior regularly – especially when your form or Salesforce objects change. Keeping things up to date ensures reliable performance.

That’s It!

By following these steps, you can streamline how your data moves between systems and ensure a seamless experience for both users and admins.

Need help troubleshooting or expanding your connector setup? Check out FormAssembly’s Knowledge Base or reach out to our support team.


Frequently Asked Questions

How to Connect Forms to Salesforce with FormAssembly

Do I need to write code to connect a FormAssembly form to Salesforce?

No. The FormAssembly Salesforce Connector maps form fields to Salesforce objects through a visual setup, with no custom code required. You configure it from the Connector Timeline by selecting a Salesforce object, defining how records are matched, and mapping each field. Advanced users can still add formulas for conditional logic when they need it.

Which Salesforce objects can a FormAssembly form create or update?

A FormAssembly form can create or update any standard or custom Salesforce object, including Leads, Contacts, Accounts, Cases, and Campaign Members. You can chain multiple object steps in one connector, so a single submission can create a Contact, create a related Case, and look up the matching Account in sequence.

How does the Salesforce Connector decide whether to create or update a record?

The connector uses match criteria you define against existing Salesforce records. If it finds no match, it can create a new record, skip the step, or stop. If it finds one match, it updates that record. If it finds multiple matches, you choose whether to update the most recent record, create a new one, or stop the connector.

What is the difference between the Salesforce Submit Connector and the Prefill Connector?

The Submit Connector sends form data to Salesforce after a respondent submits, creating or updating records. The Prefill Connector runs when the form opens and pulls existing Salesforce data into the form, so respondents see their current information instead of re-entering it. Many forms use both connectors together.

Why does Salesforce limit FormAssembly to five active connections per user?

Salesforce allows a maximum of five active OAuth tokens for a given Salesforce user per connected app. A new token is created each time you select Connect to Salesforce. To stay within the limit, reuse an existing authentication on new connectors instead of reconnecting each time.

Share

Related Posts

Higher Education

What Salesforce Education Cloud Actually Does for Universities (And Where the Gaps Are)

Read More Read More
Financial Services

How Credit Unions Use Digital Forms for Loan Applications and Member Onboarding

Read More Read More
Government

6 Digital Forms Every Government HR Department Needs for Employee Onboarding

Read More Read More

Join our newsletter!

Receive the latest data collection news in your inbox.