Pay for enrichment only when the cache misses
When a record joins an audience without a title, it uses a cached enrichment if one exists.
6 stepsEach new record
The workflow diagram
What this workflow does
When a record joins an audience without a title, it uses a cached enrichment if one exists. Otherwise it checks the Workflow Wallet can cover the most you set; if not, the record is queued for later instead of failing.
Why it works. Most records were enriched by someone before, and checking the cache and budget first means you only pay for real gaps.
Nothing is sent.
How it works
It starts: When a record joins an audience, or run on an audience now.
- 1
Already has a title?
If yes, it stops for that person. If no, it goes on to "Cached enrichment exists?".
- 2
Cached enrichment exists?
If yes, it goes on to "Enrich the person". If no, it goes on to "Room in the budget?".
- 3
Room in the budget?
If yes, it goes on to "Enrich the person". If no, it goes on to "Queue it for later".
- 4
Enrich the person
Adds the person's role and profile details.
- 5
Queue it for later
Saves what was found onto the record.
- 6
Clear the queue flag
Saves what was found onto the record.
What you need
- Workflow Wallet funds for paid lookups
- An audience
What it costs
Paid steps are charged per result from your Workflow Wallet, and you set the limit.
- Execution estimates are not a total campaign price. External tool subscriptions, model usage, advertising spend and delivery costs are separate unless explicitly itemized.
$0.047 typical per 100 contacts, up to $10.00
Free sources and LeadFuze data run first. Paid lookups only fill the rest, and misses are free on most sources. Estimates use current customer prices.
Data partners
Free sources run first, then the rest in the order this workflow tries them.
Enrich the person
LeadFuze
AI Ark
Dropleads
QuickEnrich
Hunter
Tomba
MoltSets
Datagma
- +4 more

