Data setup
Connect your source, map fields, set risk rules, and test identity matching.
Start in Connections and choose your source. Salesforce setup follows Connection → Data flows → Configure risk → Entity resolution. Each step unlocks the next one as you complete it.
For file-based setup, follow Amazon S3. For Clay, follow Use a Kernel key.
1. Connect Salesforce
Open Salesforce and connect the org you want Kernel to use. Check the selected environment and connected Salesforce user.
The integration user needs access to the source account fields and destination fields. Follow the Salesforce integration guide for installation and permissions.
2. Map fields
Open Data flows → Account import → Edit. Match the Salesforce source fields to the inputs Kernel should read. For example, map Website to Account URL and Parent Account ID to Parent Account ID.
Choose fields your team keeps accurate. A reliable legal name, website, address, or parent helps Kernel distinguish companies with similar names. Check any unavailable field and correct it before saving.
Save mapping prepares the fields for the next import. Set up the destination separately under To Salesforce. Connections and sync explains the import and output editors, nightly sync, automatic refresh, and Record Sync.
3. Configure risk
Risk settings determine how cautiously Kernel treats an account when recommending a data action. Use the three sections to:
Add Safeguards to protect records from deletion or being merged away.
Set Risk scoring rules and the score boundaries for your risk tiers.
Classify User types so ownership contributes the right level of risk.
Risk management explains each setting. Active users covers user classification and ownership.
4. Test entity resolution
Entity resolution matches a CRM record to a real company and gives that company a KERN ID. Test a small sample before approving the settings for your CRM.
Choose an identity mode
Select New run to open Configure identity matching. Choose how Kernel should resolve a conflict between the account name and website when no legal name is provided:
Bias towards URL
Your websites are more reliable than account names.
Bias towards name
Your account names are curated and more reliable than websites.
Review Fields used for entity resolution to see which Salesforce fields supply the name, legal name, websites, LinkedIn URL, address, country, and other identity evidence. Country strongly influences the country of legal registration. Update the import mapping if the wrong field is being used.
Choose a sample
Enter a Sample SOQL query (WHERE/ORDER/LIMIT) to select up to 500 accounts. For example:
The query selects the records in the test. The identity mode and field mappings control how those records are matched.
Select Test sample and wait for the run to finish. Open the completed run to review the matched companies, confidence, reasoning, and changed fields. Use Columns to show the information you need. The Accounts tab brings together the accounts included in your test runs.
Include difficult examples in your review: companies with similar names, subsidiaries that share a parent website, records with missing websites, and records whose legal name differs from their trading name.
Approve the settings
After a successful test, select Approve & Lock, choose the tested identity mode, and confirm. Kernel uses the approved identity settings across your CRM.
Approval locks the identity field mapping and mode. Contact the Kernel team to unlock them when a change is needed. See Entity resolution for how the matching works.
Inbound flows
Open Inbound flows after setup to manage how incoming records reach Kernel. The list shows each flow's type, schedule, field mappings, status, and last update.
Live
The flow is active and ready to process records.
Off
Scheduled runs are turned off.
Awaiting
The settings are complete and an enrichment workflow still needs to be linked.
Not configured
The flow needs more setup, such as an active schedule.
Select a flow to open Configuration. Edit the name and settings, then select Save. A live flow's type is locked.
Scheduled inbound
Schedule controls how often the flow runs: Minute, 5 minutes, Hourly, Daily, or Off.
CRM where clause selects which Salesforce records to import. Start with WHERE and use Salesforce field names. For example:
Where the flow shows Pull source and Push destination, choose the saved data flows to read records and write results. Enabled controls whether scheduled runs start; switching it off lets runs already in progress finish.
A flow with Enrichment workflow configured uses its linked workflow to process incoming records.
Inbound API
Use Field mappings to connect the incoming fields to the Kernel fields they populate. Select Add field to add a mapping, then choose both fields in the row.
New flows and history
Use New inbound flow when it is enabled in your workspace. Give the flow a name, choose Scheduled inbound or Inbound API, complete the settings, and select Save. If the flow shows Enrichment workflow required, ask the Kernel team to connect the workflow before using it.
Open an existing flow's History tab to see when its configuration changed, who changed it, and the old and new values.
Last updated