Need Help: Jotform to Salesforce Integration Not Updating Existing Contacts

Hi,

I’m reaching out because I’m running into a persistent issue with our Jotform to Salesforce integration, and I need guidance on how to set this up correctly and reliably.

We currently have four Jotforms that are part of our client onboarding process:

• The first form successfully creates a Contact record in Salesforce.
• The remaining forms are intended to locate that same Contact and add additional information to existing fields.

The problem is that this is not working as expected.

What I’m seeing:

• The integration is successfully finding the existing Contact (based on Email).
• However, instead of updating that Contact, it is creating a new Contact record.
• In some cases, it appears to find the correct record but does not update any fields at all.

I’ve attempted multiple configurations, including:

• Matching on different field combinations
• Using “Find existing record” with “Create record”
• Adjusting field mappings and required fields

Despite this, I cannot get consistent behavior where:

• The system finds an existing Contact
• Then updates that same Contact with new form data
• Without creating duplicates

What I need clarity on:

1. Is it possible, using Jotform’s native Salesforce integration, to reliably update an existing Contact without creating a new one?
2. If so, what is the correct configuration to ensure that behavior?
3. Are there Salesforce-side settings (duplicate rules, validation rules, permissions, etc.) that could be preventing updates or causing new records to be created instead?
4. If this is not fully supported, what is the recommended approach to handle multi-step form submissions that should all write to a single Contact record?

This workflow is critical for our onboarding process, so I need a solution that is consistent and protects data integrity.

Appreciate your help in getting this resolved.

Best,

ToniMarie

Hi ToniMarie,

Thanks for reaching out to Jotform Support. I'm an AI assistant here to assist you.

Regarding your issue with the Jotform to Salesforce integration not updating existing Contacts but instead creating duplicates, here is what you need to know:

Is it possible to reliably update an existing Contact without creating a new one using Jotform's native Salesforce integration?
Yes, it is possible. Jotform's Salesforce integration supports updating existing records by using Salesforce's standard matching rules to identify duplicates and then updating the matched record.

Correct configuration to ensure this behavior:

1. Enable the option to update an existing record: In your Salesforce integration settings within Jotform, select the action Create or update a record or use Find existing record with the Update an existing record option enabled.
2. Use proper matching fields: For Contacts, Jotform uses Full Name and Email as search parameters to find existing records. Ensure your form contains these fields and they are correctly mapped to the corresponding Salesforce fields.
3. Configure duplicate rules in Salesforce: Salesforce uses standard matching rules to detect duplicates. If Salesforce detects a duplicate, it will notify Jotform, which then updates the existing record if the update option is enabled.

Salesforce-side settings that could affect updates or cause new records:

• Duplicate Rules: Salesforce duplicate rules might block updates or cause new records to be created if the rules are strict or not aligned with your integration setup.
• Validation Rules and Permissions: Required fields missing or permission restrictions in Salesforce can prevent updates.
• Picklist Field Restrictions: Mismatched picklist values between Jotform and Salesforce can cause errors.

You can check and adjust these settings in Salesforce to ensure smooth integration.

Recommended approach for multi-step form submissions updating a single Contact record:

1. Use the Find existing record action with the Update an existing record option enabled in each form after the first one.
2. Ensure consistent use of the key matching fields (like Email) across all forms.
3. Map only the fields you want to update in each subsequent form to avoid overwriting unintended data.

Additionally, monitoring the Salesforce integration logs in Jotform can help identify any errors or mismatches causing the issue.

For detailed guidance, you can refer to Jotform's help articles on setting up duplicate checking with Salesforce integration and how to integrate Jotform with Salesforce.

Give it a try and let us know how it goes.

There is no "Update an existing record option" enabled in each form after the first one available

Hi,

Reconnecting Salesforce with your form often fixes the issue. Here’s the quick way to do it:

1. In Form Builder, in the orange navigation bar at the top of the page, click on Settings.
2. Next, in the menu on the left, click on Integrations and click on Salesforce.
3. Then, hover your mouse over the All Actions section and click on the Trash Can icon to remove the integration.
4. In the Confirmation window that opens, click on Yes, Delete.

Now, let's connect the Salesforce Integration again:

1. While you are still in Salesforce Integration Settings, click on the Add New Action button.
2. Select your Salesforce account in the Authentication section.
3. Then, Select an Action, and click on Next.
4. Finally, select a Salesforce object from the Select a Salesforce Object dropdown, set up the rest of the options, and click on Save.

Reach out again if you have any other questions.

that still doesnt give me the Update an existing record option

Hi,

Regarding the absence of the "Update an existing record" option in your Salesforce integration settings within Jotform, here are some important points to consider:

• The Salesforce integration in Jotform uses Salesforce's standard matching rules to identify existing records based on key fields like Full Name and Email.
• When Salesforce detects a duplicate record during creation, it can notify Jotform to update the existing record instead, but this requires enabling the "Update an existing record" toggle in the integration settings.
• If you do not see this option, ensure you have selected the correct integration action. The option typically appears when you choose "Create or update a record" or "Find existing record" actions.
• Sometimes, the option might not be visible if the integration interface or your Jotform account version does not support it fully or if the integration setup is incomplete.
• Check your Salesforce duplicate rules and validation rules, as strict duplicate rules or required fields in Salesforce might prevent updates and cause new records to be created instead.

As an alternative approach for multi-step form submissions that should update a single Contact record, you can:

1. Use the "Find existing record" action in each subsequent form to locate the Contact by Email or another unique identifier.
2. Map only the fields you want to update in each form to avoid overwriting data.
3. Ensure your Salesforce duplicate rules allow updates and do not block changes.

For more detailed guidance, please refer to Jotform's help article on setting up duplicate checking with Salesforce integration.

If the option is still not available, it might be necessary to review your integration setup or consider using Salesforce AppExchange's Jotform integration for enhanced features.

Let us know if you need further assistance.

How can I talk to a human?

Hi,

One of our Support Team members will take it from here to follow up shortly.

1. I went to that article you gave - whats the difference here Once connected, select your Salesforce Action:

• Create or Update a Record — Choose this if you want to create a new Salesforce record or update one that’s already in your account—it’s an easy way to keep your data fresh and up to date.
• Find Existing Record — Select this to look for an existing record or create a new one automatically if it’s not already in your Salesforce account.

Hi ToniMarie,

The Create or Update option is designed to ensure that the information from the form always ends up in Salesforce. For example, if the person is new, it creates a record, and if they already exist, based on a unique identifier like an email, it simply refreshes their current record with the new details. This is the best choice for standard lead generation or contact forms where the goal is to keep your database current without creating messy duplicates.

For the Find Existing Record option, it acts as a lookup or verification step. Its primary job is to search your Salesforce database to see if a specific person is already there without necessarily changing their information right away. This is most useful for workflows where you need to perform a check first. For example, if you need to pull existing data from a record and then use that record in the next Salesforce action in the same form.

In the scenario that you shared where the contact is found but it's not updated, can you share the specific form URL and the specific submission ID we can check and see what's going on further? Also, do you have custom duplicate rules in Salesforce? If so, that might work differently from the default behavior, which in this case, we suggest reviewing and updating as needed.

After we hear back from you, we’ll know what’s going on and how to help.

I got incredibly frustrated and deleted all the integrations to start from scratch - if there any other way to access the action logs? This is a nightmare

Thank you for your response. I want to clarify the exact workflow I am trying to achieve, because I believe that is where the issue is.

We are using multiple Jotforms as part of a client onboarding process:

• Form 1: Creates a new Contact in Salesforce
• Forms 2–4: Collect additional information over time and are intended to update that SAME Contact record

So the goal is not general lead capture. The goal is:

→ One Contact record per person

→ Multiple forms updating that same record over time

Here is what I experienced before resetting the integration:

• “Find Existing Record” successfully identified the correct Contact
• However, when using “Create or Update,” Salesforce either:
• Created a duplicate Contact, OR
• Failed with a DUPLICATES_DETECTED error

We also have Salesforce duplicate rules active (based on Email), which either:

• Allowed duplicates (resulting in multiple Contacts), OR
• Blocked the operation entirely

At no point was the existing Contact reliably updated.

My questions are:

1. Is it possible, using Jotform’s native Salesforce integration, to reliably update an existing Contact across multiple forms without creating duplicates?
2. If so, what is the exact configuration required to ensure that behavior?
3. Does “Create or Update” rely entirely on Salesforce duplicate rules to determine updates, or is there a way to explicitly target and update a specific record?
4. For a multi-form workflow like this, do you recommend a different approach (such as using a unique identifier or a different integration method)?

I have reset the integrations, so I no longer have the original action logs, but I can recreate a test scenario if needed.

This workflow is critical for our onboarding process, so I need to ensure it works consistently without creating duplicate records.

Thank you for your help.

Hi ToniMarie,

I checked your form, but the Salesforce integration has been removed. Unfortunately, integration logs are lost and can't be recovered. In the log, when there's an error like Failed with a DUPLICATES_DETECTED error, it will indicate a bit more information that'll help us identify the block.

If you're trying to prevent other users of your Salesforce account from adding duplicates of an existing record, you may consider adding the user that's integrated in your Jotform Salesforce as an exception to that rule. This gives the form access, through the account integrated, to full access to bypass the bouncers and update records without triggering the block.

Since you're only trying to create a record and update it if it already exists, I suggest using the Create or Update a Record action option. This relies fully on Salesforce contact matching rule. This would work even for a multi-form workflow, as the record is supposed to be updated every time a request is made, regardless of which form it was made from.

Also, we suggest enabling the Update an Existing Record option and using the name and email field as the identifier. Don't add too many fields here, as that might return a mismatch and can cause duplicate records to be created. We also have a guide on How to Integrate Your Jotform Forms with Salesforce that we suggest checking out.

Once you have your integration set up already, try making a few submissions, and if the same thing happens again, let us know together with the link to the form so we can check further.

Reach out again if you need any help.

Thank you, this is helpful. I want to make sure we set this up correctly before reconnecting.

A few clarifications:

1. When using “Create or Update a Record,” does Jotform rely entirely on Salesforce’s matching rules, or does it apply any internal matching logic as well?
2. If we set email as the primary identifier, will the integration reliably update an existing contact when the email matches, even if other fields differ?
3. On the duplicate rules side, do you recommend setting the integration user to bypass duplicate blocking entirely, or just switching the rule behavior from “block” to “allow with alert”?
4. If duplicate rules remain active, will Jotform return a visible error we can monitor, or will submissions silently fail?
5. For multi-form workflows, is there any risk of race conditions or timing issues that could still result in duplicates when submissions happen close together?
6. Are there any known limitations with updating existing records when using conditional logic or partial field mapping in the form?

Once I confirm these points, I’ll reconnect and run controlled test submissions.

Hi ToniMarie,

When using the Create or Update a Record action, Jotform relies entirely on Salesforce’s standard matching rules to identify existing records. Jotform does not apply additional internal matching logic beyond what Salesforce provides. If you set Email as the key matching field, the integration will reliably update an existing Contact when the email matches, even if other fields differ.

It is recommended to configure your Salesforce duplicate rules to allow the integration user to bypass duplicate blocking. This means adding the integration user as an exception to the duplicate rules, allowing updates without triggering blocks. Alternatively, switching the duplicate rule behavior from block to allow with alert can also work, but may require monitoring.

If multiple submissions occur very close together, such as from different forms, there is a chance of race conditions on the Salesforce side, especially if matching rules are not strict. This can lead to duplicate records being created before the first match is processed. Conditional logic will not prevent updates, but be sure to map only the fields you intend to update to avoid unintentionally overwriting data.

If duplicate rules block an update, Jotform will return a visible error such as a DUPLICATES_DETECTED error. You can monitor these errors through the Salesforce integration action logs in Jotform and via email notifications sent when errors occur.

Let us know if you have any other questions.

Thanks!

I think I figured it out (:

if I have another question can I ask or do I start a new help ticket?

Hi ToniMarie,

If your next question is related to this specific Salesforce onboarding setup, please keep posting here. If you run into a completely different problem, It’s best to open a new ticket. This helps us keep our logs organized and ensures you get the fastest help for that specific topic.

Let us know if you have any other questions.