Skip to content

Matching: update instead of duplicate

By default, processing a submission creates new records. Matching lets it update an existing record instead. Use it wherever the same person or account may submit more than once.

To turn it on, tick Use for matching on one or more mapped fields. When the submission is processed:

  • If an existing record matches, that record is updated.
  • If no record matches, a new record is created.

The Use for matching checkbox ticked on an Email field mapped to Contact Email.

Every ticked field on the same object must match. For example, if you tick both Email and Last Name on Contact, an existing Contact is updated only when both agree. Otherwise a new Contact is created.

  • A weak key matches the wrong record. Last Name on its own matches many people. Use something that points to one person or account, such as Email plus Last Name.
  • If any matching field is left blank, a new record is created. Sliick does not fall back to matching on the fields that were answered. The response preview tells you which matching field was blank.
  • Make every matching field required. A respondent who skips an optional matching field gets a new record instead of an update.
  • Blank answers never clear a field. When a submission updates a record, a question left blank leaves that field on the record as it was. To clear a field, edit the record itself.
  • One strong identifier beats several fields. If the form collects a customer number or another real identifier, match on that alone. Every extra field makes a match harder, so a customer whose email changed would not match and would be duplicated.
  • If two or more records match, nothing is guessed. That submission fails, and its row tells you to merge the duplicate records or add another matching field so only one record matches. Matching ignores letter case, so ada@example.com and Ada@Example.com count as the same.
  • Two responses for the same record are combined. From 1.2, when one processing run holds two responses that match the same record, both update it. Where they disagree, the later response wins, field by field, and a field only the earlier one filled in is kept. If the combined update is refused, every response that fed into it is marked Failed, with a note that any of them may be the cause. This only applies within one run: a response processed in a later run still overwrites what an earlier run wrote.
  • An updated record keeps its record type. The form’s record type choice only applies to records it creates. See Record types.

Check your matching fields before you publish. Click an empty part of the canvas and open View field mappings. The match badges show every matching field in one list.

On a public form, matching decides who can change your records. If you match on Email, anyone who submits an existing person’s email address will update that person’s mapped fields once the submission is processed. Nothing is written until the submission is processed, by someone in the responses console or by a Flow you set up, and the console shows a preview of every row first. On any form open to the internet, review before you process, and prefer matching on something a stranger would not guess.

You can see whether a submission will match before you process it. Click its row in the responses console, and the preview says whether it will update an existing record or create a new one. See The responses console.

A response preview showing the Contact will be updated because the email matches, and a new Case will be created.