Overview
This integration syncs customer data between Salesforce and UserEvidence and installs Salesforce UI components (lightning components, dashboards, reports) to give your team visibility into advocacy and reference activity directly in Salesforce.
You can configure it as:
Read-only: Pull Salesforce data into UserEvidence
Read/Write: Pull data from Salesforce AND write advocacy activity back to Salesforce (creates records, updates fields, enables Reference Management modal on Opportunity pages)
Note: The managed package is required for both integration types. Also, you may see "Zealot" in some field API names (e.g., Zealot_ReferenceID). This is the original product name—UE Advocacy for Reference was previously called Zealot. The functionality is identical; field names cannot be changed as the API sync depends on these exact names.
What This Integration Does
Data Sync
Reads Account, Contact, and Opportunity data from Salesforce into UserEvidence every 24 hours
Writes advocacy and reference activity back to Salesforce (when enabled)
Creates UE Advocacy records in Salesforce when advocates complete missions
Updates Opportunity fields when reference requests are fulfilled
Salesforce UI Components
The managed package also installs:
Custom Object: UE Advocacy (UE_Advocacy__c) to store all advocacy records
Lightning Components: Reference Management modal for Opportunity pages, Advocates list
Reports: Revenue influenced by references, win rates, reference impact
Dashboard: KPI overview for advocacy performance
This means your sales, marketing, and CS teams can see advocacy data directly in Salesforce without leaving the platform.
Prerequisites
Required Permissions
The Salesforce user authenticating the integration needs:
Read access to: Account, Contact, Opportunity objects
Modify All Data permission (or object-level Create/Edit permissions on all synced objects)
API Enabled permission
Customize Application permission (for installing managed package)
IP Allowlist Configuration
Add Workato’s IP addresses to your Salesforce trusted IP ranges:
Setup → Security → Network Access → New
(These IPs ensure Workato can communicate with your Salesforce instance)
Trusted URL
Setup → Security → Trusted URLs → New
(Note: You must have connect-src, frame-src & img-src checked)
Read-Only vs Read/Write Integration
Feature | Read-Only | Read/Write |
What it does | Pulls Salesforce data into UserEvidence every 24 hours | Pulls data from Salesforce AND writes advocacy activity back |
Use case | You only want advocate data enriched with Salesforce info | You want reference requests tracked in Salesforce + full advocacy reporting |
Managed package required? | Yes | Yes |
Reference Management modal | Not available | Available (displays on Opportunity pages) |
Writeback to Salesforce | None | Creates UE Advocacy records + updates Opportunity custom fields |
Salesforce UI components | Yes (reports, dashboards, custom object) | Yes (all components + interactive Reference Management modal) |
Setup complexity | Moderate (authenticate + install package + map fields) | More involved (includes writeback configuration + optional modal setup) |
Setup Steps
1. Authenticate via Workato
Your CSM sends a Workato invite → You complete authentication
Accept Workato invite email
Log into Workato
Switch workspace to your company name
Navigate: Projects icon → Connections → Create → Connection
Search for Salesforce
Under Location, select Execute Query
Click Connect and log into Salesforce
Confirm “Connection Established” appears
Notify your CSM (they’ll enable the Salesforce tile in your admin)
2. Define Which Contacts to Sync (SOQL Query)
Before mapping fields, identify which Contacts should sync into UserEvidence.
UserEvidence needs a SOQL query to filter which Contacts are relevant for your advocacy program. This prevents syncing your entire Salesforce database and focuses on potential advocates.
Provide this SOQL query to your CSM during setup.
Questions to Answer:
1. Which Contacts are important to identify as advocates?
Consider:
Contact record type
Account ARR/revenue thresholds
Customer lifecycle stage
Existing reference/advocacy flags
Product usage indicators
Account health scores
2. Which Contacts should be excluded/disqualified?
Consider:
Banned or churned contacts
Competitor accounts
Free tier / trial-only accounts
Specific record types to exclude
Example SOQL Query:
(Contact.RecordType.Name = 'Customer Contact' AND Contact.RecordType.Name != 'Banned Contact') AND (Account.Active_ARR__c > 10000 OR Contact.Customer_Reference__c = True OR Contact.Product_Champion__c = True) AND Account.Type != 'Competitor'
Common Filtering Criteria:
Filter Type | Example Field | Typical Logic |
Revenue threshold | Account.Active_ARR__c | > 10,000 |
Customer status | Account.Customer_Status__c | = 'Active' or 'Paying' |
Reference opt-in | Contact.Customer_Reference__c | = True |
Record type | Contact.RecordType.Name | = 'Customer Contact' |
Account exclusion | Account.Type | != 'Competitor' or != 'Internal' |
Product usage | Account.Product_Usage_Score__c | > 50 |
Lifecycle stage | Account.Lifecycle_Stage__c | = 'Customer' or 'Champion' |
Provide this SOQL query to your CSM during setup.
3. Configure Field Sync
Admin → Integrations → Salesforce CRM → Configure
Step 1: Select Fields to Read from Salesforce
Choose which fields UserEvidence should pull. Note: Custom fields can also be selected if they exist in your Salesforce. Common selections:
Account standard fields:
Id, Name, Type, Industry, Website
BillingCountry, BillingState, BillingCity
OwnerId
Contact standard fields:
Id, AccountId, FirstName, LastName, Email, Title, Phone
MailingCountry, MailingState, MailingCity
OwnerId, LeadSource
Opportunity standard fields:
Id, AccountId, Name, StageName, Amount, CloseDate, Type
OwnerId, Probability, PrimaryCampaignSourceId
Note: Field selections won’t visibly save in the Configure interface as you make them. This is expected behavior—your selections are recorded in the background. Don’t worry if you don’t see them persist on screen; they will be applied once you complete the configuration flow.
Step 2: Enable Write Settings (Optional)
Keep disabled = Read-only integration → Click Continue without writing to Salesforce
Toggle ON = Read/Write integration → Enables writeback capabilities
4. Select Fields for Advocacy Scoring
These fields enrich Contact data and help UserEvidence calculate advocacy scores.
Questions to Answer:
When manually looking for a good advocate, which Account and Opportunity fields do you check?
Think about what signals indicate:
High-value customer
Strong product engagement
Likely to provide references
Strategic account importance
Example Field Selections:
Account Fields:
Account.Active_ARR__c (or ARR, MRR, etc.)
Account.Type (Customer, Enterprise, SMB, etc.)
Account.Customer_Health_Score__c
Account.Product_Usage_Score__c
Account.Industry
Account.Employee_Count__c
Account.Tier__c (Enterprise, Mid-Market, SMB)
Account.Customer_Since__c
Account.NPS_Score__c
Opportunity Fields:
Opportunity.Amount
Opportunity.TCV__c (Total Contract Value)
Opportunity.ACV__c (Annual Contract Value)
Opportunity.StageName
Opportunity.Type (New Business, Expansion, Renewal)
Opportunity.Win_Reason__c
Opportunity.Primary_Use_Case__c
Opportunity.Product__c
Contact Fields:
Contact.Title
Contact.Level__c (C-Level, VP, Director, etc.)
Contact.Engagement_Score__c
Contact.Last_Activity_Date__c
Contact.Customer_Reference__c
Common Advocacy Signals:
Signal Type | Field Examples | Why It Matters |
Account value | ARR, MRR, TCV, ACV | Higher-value customers often more willing to advocate |
Account health | Health Score, NPS, Usage Score | Healthy customers = better advocates |
Customer tenure | Customer_Since__c, Contract_Start_Date__c | Longer customers have more experience to share |
Executive access | Contact.Level__c, Contact.Title | C-level contacts carry more weight for references |
Product engagement | Product_Usage_Score__c, DAU/MAU metrics | Active users provide better testimonials |
Deal characteristics | Opportunity.Win_Reason__c, Use_Case__c | Understand why they bought (good for case studies) |
Account tier | Account.Tier__c, Segment__c | Enterprise vs SMB may have different advocacy value |
Share your field selections with your CSM so they can map them correctly in the integration.
5. Install Managed Package (Required for Both)
Required for both read-only and read/write integrations
Click the Install UE Advocacy Package link (appears in configuration flow)
Complete installation in Salesforce (approve for all users recommended)
Return to UserEvidence Admin
Check “I’ve installed the package”
Click Save Mapping Configuration
Review summary → Click Save Mapping Configuration again
What the Managed Package Installs
What the Managed Package Installs
Custom Objects
UE Advocacy (UE_Advocacy__c) – Stores all advocacy and reference records in Salesforce
Apps & UI Components
Component | Type | Purpose |
UE_Advocacy_UtilityBar | Lightning Page (FlexiPage) | Quick-access tools for UE Advocacy users |
UE Advocacy Layout | Page Layout | Defines field layout for UE Advocacy records |
advocatesList | Lightning Web Component | Displays and manages advocate information |
referenceManagement | Lightning Web Component | Creates and manages reference requests on Opportunity pages |
referenceStageFlow | Lightning Web Component | Guides users through reference request stages |
opportunityReferenceInfo | Lightning Web Component | Displays reference notes and formatted status |
ReferenceManagementController | Apex Class | Backend logic for lightning components |
ReferenceManagementControllerTest | Apex Class | Unit tests for ReferenceManagementController |
Custom Fields on UE Advocacy Object (UE_Advocacy__c)
Field Name (API) | Label | Type | Purpose |
Account__c | Account | Lookup(Account) | Links to Salesforce Account. Relationship: UE_Advocates. |
Contact__c | Contact | Lookup(Contact) | Links to Salesforce Contact (matched by email). Relationship: UE_Advocates. |
Mission_Reward__c | Mission Reward | Text(100) | Reward advocate received |
Mission_Submission__c | Mission Submission | Long Text Area(32768) | Advocate’s submission content (text or URL) |
Mission_Type__c | Mission Type | Text(100) | Type of advocacy activity |
Custom Fields on Opportunity Object
Field Name (API) | Label | Type | Purpose |
UE_Advocacy_ReferenceID__c | UE Advocacy Reference ID | Text(128) | Unique ID linking back to UE Advocacy record. If populated, a reference request was fulfilled by UE Advocacy. |
Reference_Completed_By__c | Reference Completed By | Text(200) | Contact who fulfilled the reference request |
Reports & Dashboards
All reports live under the UE_Advocacy report folder.
Component | Purpose |
Opportunity Revenue Influenced by Reference | Total revenue influenced by references |
Request Reference Impact | Impact of reference requests on pipeline |
References Received | Volume and throughput of references |
Win Rate of Opportunities with Reference | Win rate comparison: opportunities with vs without references |
Average Time to Close With Reference | Average close time for opportunities with references |
UE Advocates By Account Report | Lists advocates per account |
UE Advocacy Dashboard | KPI overview for advocacy and reference performance |
Other Components
List View: “All” (displays all UE Advocacy records)
Custom Tab: UE_Advocacy (Trophy motif, for UE_Advocacy__c object)
Custom Application: UE Advocacy (Lightning app with utility bar)
Content Asset: zealotlogo (branding for tab/app — unchanged from original)
Folders: UE_Advocacy report folder and UE_Advocacy dashboard folder (organizes dashboards and reports)
Note: These components are automatically created during installation. View them in Salesforce: Setup → Object Manager → UE Advocacy. You can delete unused components, but never rename field API names (breaks the sync).
Standard Fields Synced (Both Directions)
Fields UserEvidence READS from Salesforce:
Account: All selected in configuration (typically account name, industry, billing address, owner)
Contact: All selected (name, email, title, phone, mailing address, owner)
Opportunity: All selected (amount, stage, close date, type, owner, probability)
Fields UserEvidence WRITES to Salesforce (Read/Write only):
Creates UE Advocacy object records (UE_Advocacy__c) when advocates complete missions
Updates Opportunity with UE_Advocacy_ReferenceID__c and Reference_Completed_By__c when reference requests are fulfilled
Optional: Add Reference Management Modal to Opportunity Pages
Only if you have Read/Write integration enabled
This allows sales reps to request references directly from the Opportunity page without leaving Salesforce.
Salesforce Setup → Lightning App Builder
Edit Opportunity Record Page
Search for referenceManagement in component list
Drag onto page (typically Tab or Highlights Panel section)
(Optional) Set Component Visibility Filters to control when it appears:
Example: Only show for opportunities > $50K
Example: Only show for stages “Discovery” through “Closed Won”
Save and activate
Package Components — Full Inventory (UE Advocacy)
This section lists every component in the Salesforce managed package after the Zealot → UE Advocacy refactor. It uses UE_Advocacy object naming, UE Advocacy/UE Advocates labels, and updated paths. Folder sharing (sharedTo) has been removed for managed package deployment.
Generated: February 2026 (post-refactor)
Summary
Metadata Type | Count | Description |
ApexClass | 2 | Server-side controllers and tests |
LightningComponentBundle | 4 | Lightning Web Components |
CustomObject | 1 | Custom object UE_Advocacy__c |
CustomField | 7 | 5 on UE_Advocacy__c, 2 on Opportunity |
Layout | 1 | Page layout for UE_Advocacy__c |
ListView | 1 | List view on UE_Advocacy__c |
Report | 7 | Reports in UE_Advocacy folder |
Dashboard | 1 | UE Advocacy Dashboard in UE_Advocacy folder |
ReportFolder | 1 | UE_Advocacy report folder (no sharedTo) |
DashboardFolder | 1 | UE_Advocacy dashboard folder (no sharedTo) |
CustomApplication | 1 | UE Advocacy Lightning app |
CustomTab | 1 | Tab for UE_Advocacy__c |
FlexiPage | 1 | UE Advocacy Utility Bar |
ContentAsset | 1 | zealotlogo (unchanged) |
Apex Classes
API Name | Path |
ReferenceManagementController | force-app/main/default/classes/ReferenceManagementController.cls |
ReferenceManagementControllerTest | force-app/main/default/classes/ReferenceManagementControllerTest.cls |
Package member format: API name only (e.g. ReferenceManagementController).
Lightning Component Bundles (LWC)
API Name | Path | Exposed | API Version |
advocatesList | force-app/main/default/lwc/advocatesList/ | No | 60.0 |
opportunityReferenceInfo | force-app/main/default/lwc/opportunityReferenceInfo/ | No | 60.0 |
referenceManagement | force-app/main/default/lwc/referenceManagement/ | Yes | 57.0 |
referenceStageFlow | force-app/main/default/lwc/referenceStageFlow/ | No | 60.0 |
Bundle contents (per LWC): *.js, *.html, *.css, *.js-meta.xml.
referenceManagement targets: lightning__RecordPage, lightning__RecordAction (Screen Action on Opportunity).
Custom Object: UE_Advocacy__c
Property | Value |
API Name | UE_Advocacy__c |
Label | UE Advocacy |
Plural Label | UE Advocates |
Name Field Label | Mission Name |
Path | force-app/main/default/objects/UE_Advocacy__c/UE_Advocacy__c.object-meta.xml |
Deployment Status | Deployed |
Sharing Model | Read/Write |
External Sharing Model | Private |
Visibility | Public |
Features | Activities, Bulk API, History, Reports, Search, Sharing, Streaming API; Feeds disabled |
Custom Fields — UE_Advocacy__c
API Name | Label | Type | Description |
Account__c | Account | Lookup(Account) | Relationship label: UE Advocates. Relationship name: UE_Advocates. Delete constraint: SetNull. |
Contact__c | Contact | Lookup(Contact) | Relationship label: UE Advocates. Relationship name: UE_Advocates. Delete constraint: SetNull. |
Mission_Reward__c | Mission Reward | Text(100) | Optional. |
Mission_Submission__c | Mission Submission | Long Text Area(32768) | The value of the advocate’s submission. Will either be text or URL. |
Mission_Type__c | Mission Type | Text(100) | Optional. |
Custom Fields — Opportunity
API Name | Label | Type | Description |
Reference_Completed_By__c | Reference Completed By | Text(200) | The name of the advocate who completed the reference call for this opportunity. |
UE_Advocacy_ReferenceID__c | UE Advocacy Reference ID | Text(128) | If populated, this is the ID of a reference request which was fulfilled by UE Advocacy. |
Layouts
API Name (package member) | Object | Path |
UE_Advocacy-UE Advocacy Layout | UE_Advocacy__c | force-app/main/default/layouts/UE_Advocacy__c-UE Advocacy Layout.layout-meta.xml |
Sections: Name (required), Mission_Submission__c, Mission_Type__c, Mission_Reward__c, Contact__c, Account__c, OwnerId; System: Created By, Last Modified By. Related lists: Activities, History.
List Views
API Name | Label | Filter Scope | Object |
UE_Advocacy.All | All | Everything | UE_Advocacy__c |
Reports
All reports live under the UE_Advocacy report folder. Folder has no sharedTo (managed package).
Package Member | Report Label | Report Type |
UE_Advocacy/Average_Time_to_Close_With_Reference_ELF | Average Time to Close With Reference | Opportunity |
UE_Advocacy/Opportunity_Revenue_Influenced_by_Refere_wR3 | Opportunity Revenue Influenced by Refere | Opportunity |
UE_Advocacy/Opportunity_Revenue_Influenced_by_Refere_OPH | Opportunity Revenue Influenced by Refere | Opportunity |
UE_Advocacy/References_Received_vQP | References Received | Opportunity |
UE_Advocacy/Request_Reference_Impac_EnK | Request Reference Impact | Opportunity |
UE_Advocacy/Win_Rate_of_Opportunities_with_Reference_SLF | Win Rate of Opportunities with Reference | Opportunity |
UE_Advocacy/UE_Advocates_By_Account_Report_pNg | UE Advocates By Account Report | CustomEntity$UE_Advocacy__c@UE_Advocacy__c.Account__c |
Dashboards
Package Member | Folder | Title |
UE_Advocacy/UE_Advocacy_Dashboard | UE_Advocacy | UE Advocacy Dashboard |
Report & Dashboard Folders
Type | API Name | Path | Sharing |
Report Folder | UE_Advocacy | force-app/main/default/reports/UE_Advocacy.reportFolder-meta.xml | None (sharedTo removed) |
Dashboard Folder | UE_Advocacy | force-app/main/default/dashboards/UE_Advocacy.dashboardFolder-meta.xml | None (sharedTo removed) |
Custom Application
API Name | Label | Description |
UE_Advocacy | UE Advocacy | UE Advocacy is a platform that helps B2B companies mobilize their most valued advocates. Give your advocates (happy customer evangelists, employees and influencers) missions like referral leads, reference call setups, case studies, video testimonials, etc. |
Nav type: Standard. UI type: Lightning. Form factors: Small, Large. Brand: logo = zealotlogo, header color #0070D2, overrides org theme. Utility bar: UE_Advocacy_UtilityBar.
Custom Tab
API Name (package member) | Object | Notes |
UE_Advocacy | UE_Advocacy__c | Tab for custom object UE_Advocacy__c. customObject=true. Motif: Custom48: Trophy. |
FlexiPages
API Name | Master Label | Type |
UE_Advocacy_UtilityBar | UE Advocacy Utility Bar | UtilityBar |
Template: one:utilityBarTemplateDesktop. Regions: utilityItems, backgroundComponents.
Content Assets
API Name | Path (metadata) | Notes |
zealotlogo | force-app/main/default/contentassets/zealotlogo.asset-meta.xml | Language: en_US. Visible by external users: false. Referenced by UE Advocacy app as logo. Unchanged by refactor. |
Package Member Quick Reference
Type | Members |
ApexClass | ReferenceManagementController, ReferenceManagementControllerTest |
LightningComponentBundle | advocatesList, opportunityReferenceInfo, referenceManagement, referenceStageFlow |
CustomObject | UE_Advocacy |
CustomField | UE_Advocacy.Account, UE_Advocacy.Contact, UE_Advocacy.Mission_Reward__c, UE_Advocacy.Mission_Submission__c, UE_Advocacy.Mission_Type__c, Opportunity.Reference_Completed_By__c, Opportunity.UE_Advocacy_ReferenceID__c |
Layout | UE_Advocacy-UE Advocacy Layout |
ListView | UE_Advocacy.All |
Report | UE_Advocacy/Average_Time_to_Close_With_Reference_ELF, UE_Advocacy/Opportunity_Revenue_Influenced_by_Refere_wR3, UE_Advocacy/Opportunity_Revenue_Influenced_by_Refere_OPH, UE_Advocacy/References_Received_vQP, UE_Advocacy/Request_Reference_Impac_EnK, UE_Advocacy/Win_Rate_of_Opportunities_with_Reference_SLF, UE_Advocacy/UE_Advocates_By_Account_Report_pNg |
Dashboard | UE_Advocacy/UE_Advocacy_Dashboard |
DashboardFolder | UE_Advocacy |
ReportFolder | UE_Advocacy |
CustomApplication | UE_Advocacy |
CustomTab | UE_Advocacy |
FlexiPage | UE_Advocacy_UtilityBar |
ContentAsset | zealotlogo |
File Path Index
All metadata and source files that belong to the package, by path (post-refactor):
force-app/main/default/applications/UE_Advocacy.app-meta.xml
force-app/main/default/classes/ReferenceManagementController.cls
force-app/main/default/classes/ReferenceManagementController.cls-meta.xml
force-app/main/default/classes/ReferenceManagementControllerTest.cls
force-app/main/default/classes/ReferenceManagementControllerTest.cls-meta.xml
force-app/main/default/contentassets/zealotlogo.asset
force-app/main/default/contentassets/zealotlogo.asset-meta.xml
force-app/main/default/dashboards/UE_Advocacy.dashboardFolder-meta.xml
force-app/main/default/dashboards/UE_Advocacy/UE_Advocacy_Dashboard.dashboard-meta.xml
force-app/main/default/flexipages/UE_Advocacy_UtilityBar.flexipage-meta.xml
force-app/main/default/layouts/UE_Advocacy__c-UE Advocacy Layout.layout-meta.xml
force-app/main/default/lwc/advocatesList/
force-app/main/default/lwc/opportunityReferenceInfo/
force-app/main/default/lwc/referenceManagement/
force-app/main/default/lwc/referenceStageFlow/
force-app/main/default/objects/UE_Advocacy__c/UE_Advocacy__c.object-meta.xml
force-app/main/default/objects/UE_Advocacy__c/fields/Account__c.field-meta.xml
force-app/main/default/objects/UE_Advocacy__c/fields/Contact__c.field-meta.xml
force-app/main/default/objects/UE_Advocacy__c/fields/Mission_Reward__c.field-meta.xml
force-app/main/default/objects/UE_Advocacy__c/fields/Mission_Submission__c.field-meta.xml
force-app/main/default/objects/UE_Advocacy__c/fields/Mission_Type__c.field-meta.xml
force-app/main/default/objects/UE_Advocacy__c/listViews/All.listView-meta.xml
force-app/main/default/objects/Opportunity/fields/Reference_Completed_By__c.field-meta.xml
force-app/main/default/objects/Opportunity/fields/UE_Advocacy_ReferenceID__c.field-meta.xml
force-app/main/default/reports/UE_Advocacy.reportFolder-meta.xml
force-app/main/default/reports/UE_Advocacy/Average_Time_to_Close_With_Reference_ELF.report-meta.xml
force-app/main/default/reports/UE_Advocacy/Opportunity_Revenue_Influenced_by_Refere_OPH.report-meta.xml
force-app/main/default/reports/UE_Advocacy/Opportunity_Revenue_Influenced_by_Refere_wR3.report-meta.xml
force-app/main/default/reports/UE_Advocacy/References_Received_vQP.report-meta.xml
force-app/main/default/reports/UE_Advocacy/Request_Reference_Impac_EnK.report-meta.xml
force-app/main/default/reports/UE_Advocacy/Win_Rate_of_Opportunities_with_Reference_SLF.report-meta.xml
force-app/main/default/reports/UE_Advocacy/UE_Advocates_By_Account_Report_pNg.report-meta.xml
force-app/main/default/tabs/UE_Advocacy__c.tab-meta.xml
Apex and LWC Functions
(Unchanged from pre-refactor. ReferenceManagementController and LWC behavior are the same; API base URLs in referenceManagement.js remain joinzealot.com per plan.)
Apex
ReferenceManagementController
Purpose: Supplies data to the Reference Management flow by loading contacts for the current Opportunity.
Method: getOpportunityContacts(Id opportunityId) — @AuraEnabled(cacheable=true), returns related Contact records for the Opportunity.
ReferenceManagementControllerTest
Purpose: Unit tests for ReferenceManagementController (getOpportunityContacts, null/invalid ID handling).
Lightning Web Components (LWC)
referenceManagement — Main Reference Management UI on Opportunity; brand config (api.joinzealot.com), Request (Slack) and Choose (API) flows, modals, contact loading.
advocatesList — Displays list of chosen advocates.
opportunityReferenceInfo — Displays reference notes and formatted status.
referenceStageFlow — Displays reference lifecycle as a step path with tooltips.
Testing & Verification
Testing & Verification
Make sure steps 1-5 have been completed above
Go to Admin → Integrations → Salesforce CRM → Configure
Map at least a few fields (Account Name, Contact Email, etc.)
Wait 24 hours – UserEvidence pulls data once per day
Check your UserEvidence dashboard – You should see Salesforce data populating advocate profiles
What Should Be Visible After First Sync
Advocates with matching emails should now show:
Account Name
Job Title
Account Owner
Any other fields you mapped
Verify Writeback (Read/Write Only)
Have an advocate complete a mission in UserEvidence
Approve the mission submission
Check Salesforce → UE Advocacy tab
You should see a new UE Advocacy record with:
Contact (linked)
Mission Name
Mission Type
Mission Submission
If the mission was a reference request linked to an Opportunity:
Check the Opportunity record
Custom fields UE_Advocacy_ReferenceID__c and Reference_Completed_By__c should populate
Confirm No Duplicate Records
Each advocate submission should create ONE UE Advocacy record. If you see duplicates, contact your CSM.
Common Issues & Solutions
Common Issues & Solutions
Issue: “Connection Established” but fields aren’t syncing
Solution:
Verify you clicked “Save Mapping Configuration” in UserEvidence admin
Wait full 24 hours for first sync
Check that the Salesforce user has Read permissions on all mapped objects
Issue: Not enough (or too many) Contacts syncing
Solution:
Review your SOQL query with your CSM
Test the query directly in Salesforce (Developer Console → Query Editor)
Adjust revenue thresholds, record types, or exclusion criteria
Ensure custom fields in the query exist and are spelled correctly
Issue: Can’t see UE Advocacy tab in Salesforce
Solution:
Managed package may not be installed correctly
Go to Setup → Installed Packages → Verify package is listed
Check user profile has access to the UE Advocacy app
Issue: Reference Management modal not appearing on Opportunities
Solution:
Verify managed package is installed
Check Lightning page assignment (Setup → Lightning App Builder → Opportunity Record Page)
Verify component visibility filters aren’t hiding it
Confirm Read/Write integration is enabled
Issue: Writeback not working (no UE Advocacy records created)
Solution:
Confirm “Enable Salesforce Capability” is toggled ON
Verify managed package is installed
Check Salesforce user has Create/Edit permissions on UE Advocacy object (UE_Advocacy__c)
Ensure missions are APPROVED (submissions don’t writeback until approved)
Issue: “API limit exceeded” errors
Solution:
Workato syncs use API calls. If you’re hitting limits:
Reduce frequency of other API integrations
Contact Salesforce about increasing API limits
Contact your CSM to discuss optimization
Issue: Custom fields not mapping
Solution:
Custom field API names must be selected exactly
Verify the Salesforce user can read the custom field
Check field-level security settings in Salesforce
Issue: Managed package installation fails
Solution:
Verify authenticating user has “Customize Application” permission
Check if conflicting custom objects/fields exist with same names
Try installing in sandbox first to identify conflicts
Contact your CSM for package installation support
Issue: Advocacy scores seem inaccurate
Solution:
Review which Account/Opportunity fields you selected for scoring
Ensure revenue fields (ARR, ACV, etc.) are mapping correctly
Check if health scores or engagement metrics are syncing
Contact your CSM to adjust scoring weights
Quick Reference Checklist
Quick Reference Checklist
For Read-Only Integration:
Accept Workato invite
Authenticate to Salesforce
Provide SOQL query to filter Contacts (work with CSM)
Select Account/Opportunity fields for advocacy scoring
Map fields in UserEvidence admin
Install managed package
Wait 24 hours for sync
Verify data appears in UserEvidence
Check Salesforce for UE Advocacy tab, reports, and dashboards
For Read/Write Integration:
Accept Workato invite
Authenticate to Salesforce
Provide SOQL query to filter Contacts (work with CSM)
Select Account/Opportunity fields for advocacy scoring
Map fields in UserEvidence admin
Toggle “Enable Salesforce Capability” ON
Install managed package
(Optional) Add Reference Management modal to Opportunity pages
Have an advocate complete a mission
Approve the mission
Verify UE Advocacy record created in Salesforce
Check that Opportunity fields updated (if reference request)
Pre-Setup Checklist (Share with Your CSM)
Before your kickoff call, prepare:
1. SOQL Query for Contact Filtering
Which Contact record types to include/exclude?
Minimum ARR or revenue threshold?
Any existing reference/advocacy flags in Salesforce?
Account types to exclude (competitors, internal, etc.)?
2. Field Selection for Advocacy Scoring
What Account fields indicate a high-value customer?
What Opportunity fields show deal quality?
Any custom health/engagement scores to include?
3. Technical Access
Who will authenticate to Workato? (needs admin permissions)
Who will install the managed package?
Do we need to install in sandbox first for testing?
4. Business Context
What’s your current ARR distribution? (helps set thresholds)
How do you currently identify advocates manually?
What makes a “good” reference for your sales team?
Need help? Contact your CSM.