Skip to content

Mapping a starter form

Every starter in New Form comes with no Salesforce mapping. That is on purpose: a starter cannot know which objects your organisation uses or which fields you can write to. It gives you the questions and the layout, and you spend a few minutes pointing them at your own objects.

An unmapped form still works. It shows, people submit, and every answer is saved in Sliick Responses. Nothing errors. The answers just never reach a Contact, Lead or Case until you map the fields and process the submission. If you only read responses in the console or export them to CSV, you can stop here: mapping is optional.

  1. Open the form in the Form Builder by clicking its name on the dashboard.
  2. Map one field at a time: select the field, click Map field next to Salesforce mapping, and pick the object and field. See Mapping fields to Salesforce.
  3. If an object you expect is missing from the picker, your user does not have access to it. The picker only lists objects and fields you can create records with.
  4. When you are done, use View field mappings to check every mapping and every matching field in one list before you publish.

Check two things before following the Contact form recipe: some organisations do not use Cases at all, and organisations with person accounts handle Contacts differently. If either applies to you, map the message question somewhere else, such as a custom object or a long text field on the Contact. Everything else on this page still applies.

Five fields, two objects: the person goes on a Contact, their question goes on a Case.

Field on the formMap toAlso do this
First NameContact.FirstName
Last NameContact.LastNameThe Contact’s only required field
Email AddressContact.EmailTick Use for matching
How can we help?Case.DescriptionThe question belongs on a Case, not on the person
(add) Hidden field originCase.OriginDefault Value Web
(add) Hidden field subjectCase.SubjectDefault Value Website contact form

Why tick Use for matching on Email. Someone who writes in again updates their existing Contact instead of creating a second one. That is right for a contact form, and wrong for an anonymous survey, where every response should stand alone. See Matching.

Why the two hidden fields. A Case with no Subject is hard to read in a list view, and Origin tells your support team the Case came from the web. The respondent should not have to type either, so the form fills them in.

You do not need to link the Case to the Contact. Case has only one lookup to Contact, so Sliick links them when it creates both. Settings shows Link Case to Contact already filled in; leave it as it is. You only have to choose when an object has two or more lookups to the same object. See The form’s object model.

  1. Drag Hidden Field from the palette’s Read only group onto the canvas.
  2. Set its API Name (origin) and Label (Origin). Respondents never see it, so the label is just for you.
  3. Type the fixed value into Default Value (Web).
  4. Map it like any other field.

A hidden field's settings with API Name origin, Default Value Web, mapped to Case Origin.

A mapped hidden field with a Default Value writes that value onto the record on every submission. This is how you fill a required field without asking the respondent anything, and you will use it often.

This starter has a real choice in it. Pick one of three options.

Option A, Lead. Best when the people registering are new to you and you want sales or marketing to follow up.

  1. Map Attendee First Name, Attendee Last Name and Email to Lead.FirstName, Lead.LastName and Lead.Email.
  2. Tick Use for matching on Email.
  3. Map Company to Lead.Company.
  4. Add a hidden lead_source field mapped to Lead.LeadSource with a Default Value of Web.

Do not skip the Company mapping. Every Lead needs a Company. If nothing is mapped to Lead.Company, the form collects answers normally, but every submission then fails when it is processed, possibly days after you published. If asking for a company does not suit your event, delete that question and add a Hidden Field mapped to Lead.Company with a fixed Default Value instead. The trade-off: every attendee is filed under that one company name, and it becomes the Account name if someone converts the Lead.

Option B, Contact. Best for member or customer events, where a Lead for every registration would be clutter. Map the three attendee fields to Contact.FirstName, Contact.LastName and Contact.Email, and tick Use for matching on Email. Contact has no Company field, so delete the starter’s Company question or leave it unmapped.

Option C, Campaign Member. The most accurate option. A starter cannot set it up for you, because it needs an ID from your own organisation.

  1. Do Option A or B first: a Campaign Member must point at a Lead or a Contact.
  2. Add a hidden campaign field mapped to CampaignMember.CampaignId. Set its Default Value to the campaign’s 18-character ID, copied from the campaign record’s URL.
  3. Optionally, add a hidden member_status field mapped to CampaignMember.Status, with a value from that campaign’s status list, usually Registered.

Sliick links the Campaign Member to the Lead or Contact for you. One form serves one campaign. For another event, duplicate the form and change the ID, or leave the campaign out of the form and add members with a Flow after each submission arrives.

We recommend leaving these unmapped. A survey response is a measurement, not a record about a person. All three survey starters work fully unmapped: every answer is in Sliick Responses, where you can filter it and export it to CSV, and View results shows the spread of scores.

Map them only if you have a specific place for the score, such as a custom survey object or a score field on the Case or Contact the survey followed up. If you do:

  • Do not tick Use for matching on anything. Each response should be its own record. With matching on, a second response would overwrite the first.
  • To attach a response to the record it is about, add a hidden field mapped to the lookup and pass the record ID in the link. See Sharing a form.

Send one test response all the way through:

  1. Publish the form, open its share link, and submit a test response.
  2. Open Sliick Responses, find the row, and click it to see what will be written before anything happens.
  3. Click Process. The status should change to Completed.
  4. Open the record it created and check each value landed in the right field.

If the row shows Failed, the reason is on the row. It is almost always a required field on the target object with nothing mapped to it, or a field your user cannot write to. Fix the mapping and click Retry. The original answers are kept exactly as submitted. See Processing responses onto records.