> For the complete documentation index, see [llms.txt](https://docs.kernel.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kernel.ai/integrations/salesforce-integration/enrich-with-kernel.md).

# Automatic refresh

How Kernel keeps Salesforce account data current through scheduled refreshes and the Enrich with Kernel action.

{% embed url="<https://pub-8e1d08f439ec43bdbb79f1055a273a02.r2.dev/automatic-refresh-frequency-e4010970.mp4>" %}

Automatic refresh controls how often changed Kernel values are written back to Salesforce. It is separate from the nightly CRM import and from Salesforce Record Sync schedules.

This page covers automatic updates to Kernel Account and the **Enrich with Kernel** action for one Account. Use [Set up Record Sync and schedules](https://docs.kernel.ai/integrations/salesforce-integration/record-sync-backfill-and-schedules) when you want to copy selected values between Kernel Account and Account.

## Automatic refresh frequency

Kernel values can change as research or feedback updates the data. Automatic refresh sends changed values to Kernel Account on the cadence you choose: Daily, Weekly, Monthly or Never.

Each run sends accounts whose Kernel values have changed since the previous run. It does not rewrite every Account. Check that a new value has reached Kernel Account before expecting a Salesforce field-copy mapping to place it on Account.

## Enrich with Kernel

**Enrich with Kernel** runs the configured inbound enrichment workflow for one Account from Salesforce. A rep opens the Account, selects the action and confirms the request.

Processing happens in the background. The result is written to the destinations configured for that workflow, so check the mapped destination fields when processing completes.

A completed enrichment from the previous 14 days can be reused from cache. Clicking the action again does not necessarily start new research. If a request is already running, Kernel returns that in-progress request instead of starting another one.

## Why it matters

* Reps can refresh account data from the Salesforce record they are already using.
* Refreshes can happen on demand, not only during scheduled syncs.
* The standard unlocked package works in sandbox and production without custom development.
* The action respects Salesforce object and field permissions.
* Built-in caching prevents duplicate enrichments for 14 days
* Requests are rate-limited and concurrency-capped automatically