Salesforce setup for Edge Webforms
This page covers the Salesforce-side configuration needed to receive webform submissions via Edge Webforms.
Custom fields on Trip
Create these subscriber custom fields on KaptioTravel__Trip__c. These are org-specific fields, not managed-package fields.
Webform fields (populated from form answers)
| Label | API Name | Type | Notes |
|---|---|---|---|
| Selected Tour and Tier | Selected_Tour_Tier__c | Text(255) | Pre-populated from the tour page |
| Travel Date | Travel_Date__c | Text | Visitor-entered travel date |
| Travel Date Flexible | Travel_Date_Flexible__c | Checkbox | +/- 5 day tolerance |
| Group Size Adults | Group_Size_Adults__c | Number | Number of adults |
| Travel From | Travel_From__c | Text | Departure city |
| Ready to Book | Ready_To_Book__c | Picklist | Yes / Still exploring options |
| Best Time to Call | Best_Time_To_Call__c | Picklist | Dynamic options: Today HH:00, Tomorrow HH:00 |
| Marketing Opt Out | Marketing_Opt_Out__c | Checkbox | Consent withdrawal |
| Additional Requests | Additional_Requests__c | Long Text Area(5000) | Free-text |
B2B fields (populated for travel agent submissions)
| Label | API Name | Type | Notes |
|---|---|---|---|
| Is Trade Enquiry | Is_Trade_Enquiry__c | Checkbox | True when submitted by an agent |
| Travel Agency Name | Travel_Agency_Name__c | Text | Agency name |
| IATA / Accreditation Number | Agent_Accreditation_Number__c | Text(20) | Used to match to Travel Agent Account |
Intelligence fields (populated by scoring engine when enabled)
These fields are only needed when intelligence.enabled: true. They can be created upfront or deferred.
| Label | API Name | Type | Notes |
|---|---|---|---|
| Enquiry Priority Tier | Enquiry_Priority_Tier__c | Text | Tier name (e.g. Urgent, Standard, Quick Quote) |
| Enquiry Priority Score | Enquiry_Priority_Score__c | Number | 0-100 |
| Enquiry Score Tags | Enquiry_Score_Tags__c | Text | Comma-separated tags |
| Enquiry Routing Queue | Enquiry_Routing_Queue__c | Text | Suggested queue name |
| Enquiry SLA Target | Enquiry_SLA_Target__c | Text | SLA target (e.g. 1h, 4h) |
Page layout
Add a WebForm Information section to the Trip page layout:
- Layout: 2 columns
- Left column: Selected Tour and Tier, Travel Date, Group Size Adults, Ready to Book, Best Time to Call
- Right column: Travel Date Flexible, Travel From, Marketing Opt Out, Additional Requests
For B2B, add a second section Trade Enquiry with: Is Trade Enquiry, Travel Agency Name, IATA / Accreditation Number.
Field-level security
Grant Read + Edit on all webform fields via the Kaptio Admin Permission Set (or the equivalent admin permission set in your org):
Setup > Permission Sets > Kaptio Admin Permission Set > Object Settings > Trip > Edit > enable the webform fields.
Record type and status
Edge Webforms creates Trips with:
- Record Type: as configured in
trip-mapping.yamltarget.recordType(default:Qualification) - Status: as configured in
trip-mapping.yamltarget.defaultStatus(default:Enquiry)
Ensure these values exist in your org's Trip record type and status picklist.
Trip conversion guide setup
Applies when your tenant uses two-stage intake (Lead or custom object capture) with the Trip conversion guide.
Fields on the source object
| Purpose | Lead source | Custom object source |
|---|---|---|
| Trip reference stamp | A Trip lookup, e.g. Trip__c (configured as lead.converted_trip_field) | Same |
| Converted marker | Native (IsConverted) — a converted Lead status must exist and be mapped in Lead settings | A status picklist including the configured converted.status_value |
| Account / Contact stamps | Native (ConvertedAccountId, ConvertedContactId) | Optional lookups (converted.account_field, converted.contact_field) |
Embedding the panel on the record page
The conversion guide is an Edge Canvas embedded via the edgeCanvasRunner component. On the Lead (or custom object) record page:
- Edit the record page in Lightning App Builder and add the
edgeCanvasRunnercomponent withcanvasIdset to your conversion canvas (e.g.lead-to-trip). - Check the page activation scope. Record-page activation is app-, record-type-, and profile-specific — a panel activated for one Lightning app is invisible in every other app. Verify the page is active for the app your sales agents actually work in, not just the app you tested with.
- Ensure the Remote Site Setting and CSP Trusted Site for the Edge canvas host exist (they are shared with other Edge canvases — see Salesforce embedding).
Integration user permissions
The conversion runs with the Edge integration user's permissions. It needs:
- Read on the source object; create/edit on Account, Contact, and Trip.
- Edit on the source object's stamp fields (Trip lookup, status, optional Account/Contact lookups).
- Update Converted Leads (Lead sources only, recommended): without it, the one conversion shape where Salesforce creates the PersonAccount during conversion — a brand-new direct customer — cannot stamp the Trip back onto the now-read-only Lead. The Trip is still created and linked correctly; the panel reports the missing stamp as a warning.
Org validation rules
Trips created by the conversion guide are subject to your org's validation rules, and the panel surfaces the org's own error message to the agent. Two patterns worth checking upfront:
- Group size rules (e.g. "Group Size must be 1 or greater") — set
trip.default_group_sizein the path config. - Primary contact completeness rules (e.g. "Primary Contact must have an Email and a Phone") — these make intake phone/email quality matter; see what the record needs to look like.