Start from an event with a clear purpose
Use a user action, record lifecycle event or rule that explains why enrichment is needed now.
Event-driven contact enrichment
Trigger waterfall contact enrichment when your workflow needs it.
Call the TargetWise REST API when a known record reaches the point where a work email or business phone is needed. Each requested field can follow eligible routes across 15+ specialist sources before one normalized result returns to your workflow.
No CSV upload, background scan or whole-database refresh.
Event-driven enrichment
IllustrativeRequestA known contact entered the review stepRule triggered · work email requested
TargetWise routeOne entity per lookup
Person + companyResolved
Work emailReturned
Next stepCustomer rule evaluates
15+ sourcesavailable for contact waterfall routing
REST APIfor deterministic event logic
One callfor the known entity
Explicitmatched, partial or not found
Enrich where the decision happens
Replace manual file handoffs with a single API request.
A contact-enrichment workflow sends one known professional at the moment a work email or business phone is needed and returns the result directly to the logic that requested it.
The trigger can come from application code, CRM automation, a product action or an authorized agent host. TargetWise does not need a periodic export or broad access to the customer’s database.
The calling workflow supplies the professional and company context, selects email, phone or both, and receives a normalized result after eligible waterfall routes have completed. The workflow handles matched, partial and not-found outcomes and controls any later write.
Automation should make boundaries clearer.Define the trigger, identity requirements, requested contact fields, terminal outcomes, retry limit and downstream approval before enabling the workflow.
Automation building blocks
A complete enrichment step has more than an API call.
Design the trigger and outcome behavior with the same care as the request itself.
Confirm the subject before the call
Use a LinkedIn profile URL, or a person name with company name or domain, to reduce ambiguous matches.
Request only the contact fields needed
Select work email, business phone or both for the decision this workflow is making.
Call one TargetWise operation
TargetWise manages the eligible waterfall routes and returns one normalized business outcome.
Handle all business outcomes
Build deterministic paths for matched, partial and not-found results.
Control what happens after retrieval
Keep merge rules, approvals, writes and communications in separate workflow logic.
Reference automation
Trigger, request, branch and continue.
REST and MCP use the same operational discipline around the enrichment step.
Receive the event
A known record reaches the point where external context is required.
Call TargetWise
Send one supported identity and, for contact enrichment, the requested fields for this branch.
Evaluate the result
Apply rules to matched, partial, not-found or operational-error outcomes.
Continue safely
Write, review, notify or stop according to separately controlled logic.
One integration layer
Use one enrichment step instead of wiring 15+ providers into every workflow.
TargetWise keeps provider eligibility, field routing and supplier-specific response mapping behind one customer-facing contract. Your automation sends the supported identity and requested contact fields, then evaluates one normalized result.
The workflow still owns retries, acceptance, merge rules and downstream actions. A business no-match is a completed result; only temporary operational failures should follow a retry limit with backoff.
- Field-specific routing across eligible sources
- One normalized response contract
- Matched, partial and not-found outcomes
- No supplier credentials in workflow code
- Customer-owned acceptance and write rules
Outcome router
What the next step receives
1Matched — accepted fields available
2Partial — only some fields available
3Not found — terminal business outcome
4Error — operational recovery path
Automation patterns
Add enrichment at a defined moment—not everywhere.
A precise trigger makes the value and data purpose easier to understand and measure.
Find the work email before assignment.
Call enrichment when a known professional enters the routing rule, then pass the contact outcome directly to the next step.
Complete one missing field on demand.
Trigger from an open or assigned record instead of exporting a list for later processing.
Complete a known professional profile.
Request the requested contact field only when the product flow needs it and keep no-match behavior explicit.
Let an agent invoke a MCP action.
Use the host for permissions while deterministic workflow logic controls outcomes and downstream changes.
Frequently asked questions
What to know before you build.
Good automation makes each trigger, requested field, terminal outcome and downstream action explicit.
Free plan
Test the entire workflow—including its stop conditions.
Use representative matches, partial results and expected no-match records before enabling a production trigger.