← All tools

Enrichment

Fill empty Salesforce and HubSpot fields, with a cap on every run

Fill missing fields from a data provider, to a ceiling you set.

SalesforceHubSpotReversible

Fields nobody ever filled in. Industry, revenue and headcount are blank on most of the book, because they were never required at entry and nobody has gone back. Every segment built on them silently excludes the records that are missing them.

Enrichment fills what is missing rather than overwriting what is there. That distinction is the whole configuration: for each field you map, you decide what should happen when the CRM already holds a value.

A mapping is provider field to CRM field, plus a rule. Fill only when empty is the conservative default and the one most teams want. Overwrite is available for fields where the provider is more trustworthy than the record.

Spend is bounded by the run, not by the configuration. A credit cap belongs to the run because it is a decision about this pass, not a property of the mapping. A run stops at its cap rather than spending to the end of the scope.

How a pass runs

From scope to record.

  1. Scope. A run names the contacts it covers, and a cap on what it may spend.
  2. Preview. The run can be previewed first: how many records are in scope, how many are missing the fields you asked for, and what it would cost.
  3. Fetch. The provider is asked only about records that are actually missing something.
  4. Reconcile. Each returned value is checked against the rule for that field before it is written.
  5. Write and record. Changed fields are written and stored with their prior values.

The detail

What it needs and what it does.

Object
Contacts.
Configured in
Rules, under Enrichment, as a field mapping with a rule per field.
What it writes
The mapped fields, according to each field's rule.
Who releases it
You choose when you create the run: write on dispatch, hold the whole run for approval, or queue one proposal per record.
Reversible
Yes. Every field write is stored with its prior value and can be put back.
CRMs
Salesforce and HubSpot.

Cost

Looking is free. Only fetching is charged.

Which is why the preview is the first thing this tool offers.

Searching a provider costs nothing. Enriching a record costs a credit. The preview walks the scope and tells you how many records are actually missing the fields you asked for, which is almost never the same as how many records are in scope.

The cap is a ceiling rather than a target. A run set to five hundred stops at five hundred and reports what it did not reach, rather than quietly spending to the end of the book.

For agents

The tools your agent calls.

Reads are free and need no permission to write. Anything that changes a record is a separate grant.

preview_enrichment_run what it would fetch and what it would cost read
create_enrichment_run a run over a scope, with a cap write
dispatch_run start it write

Where to start

Find out how many you have.

The readiness scan runs detection against your own CRM and reports what it finds, before anything is merged.