Salesforce Integration Basics: A FormAssembly Webinar Recap

Quick Answer

Salesforce integration basics come down to six questions: How do you find the right record? Should you create or update it? What does it connect to? Does one submission hold more than one record? Should the action run at all? And what happened when something went wrong?

FormAssembly’s Salesforce connector answers each one with lookup conditions, update-or-create settings, related-record mapping, repeatable sections, skip-if formulas or preconditions, and connector logs. Master these six things, and you’ll be well on your way to building everything from event registrations to multi-object application workflows.

---

Most teams don’t struggle with connecting tools and platforms to Salesforce. They struggle with the first bit of complexity: the duplicate contact that appears every time someone resubmits, the long notes fields that flood a records, or the hours of manual data cleanup that follow.

In the recent webinar, “FormAssembly + Salesforce: Back to the Basics,” the FormAssembly team walked through live demos of the core concepts behind FormAssembly’s Salesforce integration. The demos used the form-native Salesforce connector and the Salesforce workflow connector. 

Read on for a recap of the presentation, organized around the questions the session answered, or watch the webinar on-demand here.

How do you find the right Salesforce record from a form?

You can find the right Salesforce record from a form by using a lookup. A lookup tells the connector what counts as a match by comparing Salesforce fields to form fields. The simplest version matches on one field, such as email address. When one field isn’t enough, add conditions, such as email + first name + last name.

In the form-native connector, you can combine conditions with AND and OR. In the Salesforce workflow connector, you choose whether every condition, any condition, or a custom logic string (like “A and (B or C)”) must be satisfied.

The same lookup concept works for contacts, accounts, opportunities, cases, and custom objects. The question never changes: what do you have that reliably identifies this record?

Should a form create or update a Salesforce record?

Both, depending on whether the record already exists. The lookup result drives the decision. If a match is found, the connector updates it. If no match is found, the connector creates a new record, which prevents duplicates without leaving gaps.

Learn more about updating records in Salesforce here.

In the form-native connector, you can configure the update step to control this:

• If one match: Update the record.
• If multiple matches: Update the most recent record or create a new one.
• If no match: Skip the step, end execution, and log an error or create a new record.

A lookup isn’t a standalone step. Its result informs what happens next. After that, you map form fields to Salesforce fields to send only the data you actually need.

How do you connect related records in Salesforce?

To connect related records in Salesforce, start by passing the ID of the first record into the second. Most Salesforce records depend on other records. A campaign member, for example, must connect to a contact. Once the connector finds or creates that contact, you reuse its ID.

In the form-native connector, you map the contact ID field to “ID of an object above” and select the earlier update step. In the Salesforce workflow connector, you return the Salesforce ID into a workflow variable (for example, “contact ID”) and map that variable in later steps.

The pattern holds for an opportunity that belongs to an account or a case created for a contact. Ask what the record belongs to, then map the relationship.

How do you handle repeated data, like multiple registrants on one form?

Use repeatable sections and tell the connector to process each repeat separately. If one booking includes several attendees, you don’t want “Jane John Doe Smith” merged into a single contact. You want one contact per person, each with their own campaign member record.

In the form-native connector, the update step’s repeatable options let you merge data into one record or update a different record for each repeated instance. In the workflow connector, mapping to the repeatable section produces the same per-instance behavior.

How do you control when a Salesforce action runs?

Add conditional logic. Not every action should run on every submission. In the form-native connector, use a skip-if formula: return true to skip the step, false to run it. For example, skip the contact update and campaign member creation when the total due today is zero.

The Salesforce workflow connector flips the approach with preconditions. Instead of writing when to skip, you define when to run, such as “only create a contact when contact ID is blank.” You can stack multiple conditions with all, any, or custom logic.

Because both tools accept form fields, formulas, and variables, they can test for a specific answer, an empty field, or a combination of conditions.

How do you troubleshoot Salesforce connector errors?

Start with the connector logs in FormAssembly. They show what the connector tried to do and what Salesforce returned. Successes show in green, errors in red, and the logs also show which steps ran, which were skipped, and which records were updated.

You can find logs in several places:

• At the bottom of an individual form response page.
• In the form-native connector’s “Go to” menu, under Log, or from the connector timeline.
• At the top of a workflow response, using the Logs button.

The goal isn’t necessarily to spot the word error. It’s to answer two things: what did the connector try to do, and what happened when it did? Reading logs beats resubmitting a response and guessing at the result.

What did attendees ask during the live Q&A?

Attendees asked about lookups, person accounts, Salesforce flows, and error alerts. The answers below are condensed from the live session.

Q: Can you use custom fields in a lookup?

A: Yes. You can use any Salesforce field in a lookup, as long as the form-native connector has read and write permissions for it. For example, one team asked each person to type in a unique code, stored in a custom field, so only that person could match their own record.

Q: Does FormAssembly support Salesforce person accounts?

A: Yes. Both the form-native and workflow connectors support person accounts. Map the record type ID for person accounts in your lookup and in your create or update field mappings so the connector finds or creates the right type of record. For a full walkthrough, see the dedicated person accounts webinar.

Q: Can FormAssembly replace Salesforce screen flows for creating records?

A: For many teams, yes. You can create or update contacts, associate them to accounts, and create custom application records from one connector or workflow, without writing a Salesforce screen flow. Teams can also trigger a Salesforce flow after the connector creates a record, so the two approaches work together.

Q: How do you avoid duplicates when many contacts share a last name?

A: Expand your lookup conditions. The form-native connector’s “like” operator doesn’t behave exactly like Salesforce’s. A search for “Smith” can also match “Smiths.” Add fields that tell the Smiths apart, such as email, location, or another identifier. If your lookup needs many conditions, the workflow connector’s custom logic is easier to manage than stacked AND and OR groups.

Q: How do you get email alerts for connector errors?

A: Open your username menu, go to General Settings, and turn on the notification for downtime or processing errors on your forms and workflows. When a connector hits an error, you receive an email with a link to the affected response and the error itself.

Q: Where can you get help building forms for Salesforce?

A: Start with Fai, FormAssembly’s built-in AI assistant, or browse the template library. Fai can suggest fields and wording based on common practices for the type of form you describe, and your team reviews and approves every change before anything goes live. Because there is no single recommended set of questions, begin with what the form needs to accomplish, such as the information you need to place a volunteer, then work backward.

Watch the full webinar

The replay includes the full live demos for both connectors, side-by-side screens you can pause and follow, and the complete Q&A. Whether you’re new to the FormAssembly Salesforce integration or revisiting a setup you built years ago, the basics are worth a second look.

Watch the on-demand replay.