Put enrichment to work.

Build for your platform

Recipe 01 · Account research

Build a relevant account shortlist

Trigger. A researcher applies an market segment.

{
  "filters": {
    "website_keywords": [
      "logistics"
    ],
    "employee_count": {
      "min": 200,
      "max": 5000
    }
  },
  "limit": 5,
  "page": 1
}

Workflow

1. Search one page using the segment’s filters.
2. Compare company names, websites and locations against your criteria.
3. Pass the selected company_id to /companies/enrich, preserving the returned string exactly.

Request budget. One search call, followed by one enrichment for each deliberately selected company.

Recipe 02 · Buying committee research

Find the right people at a target account

Trigger. An account owner chooses a company domain and the seniority they need.

{
  "domains": [
    "example.com"
  ],
  "seniorities": [
    "vp",
    "director"
  ],
  "limit": 5,
  "page": 1
}

Workflow

1. Search candidates within the selected company domain.
2. Review current role and company context before choosing a person.
3. Use their LinkedIn URL or supported name and company fields with /contacts/find-work-email. Do not pass person_id as an enrichment input.

Request budget. One search plus one field lookup for the chosen person.

Recipe 03 · Inbound routing

Add context to an inbound business email

Trigger. A business contact submits a form and your backend receives the email.

{
  "email": "alex@example.com",
  "include_phone": false,
  "include_profile": false
}

Workflow

1. Resolve the submitted business email once for that form event.
2. Compare returned employer context with the submitted company information.
3. Apply your existing assignment rules. If more company context is necessary, enrich a returned company_id in a separate call.

Request budget. One reverse lookup; company enrichment is an optional second call.

Recipe 04 · CRM record review

Complete a missing CRM contact field

Trigger. A user opens or assigns a contact record whose work email is empty.

{
  "first_name": "Alex",
  "last_name": "Reed",
  "company_domain": "example.com"
}

Workflow

1. Check that the field is still missing and that this workflow has not already completed the lookup.
2. Make one field-specific request using the known person identifiers.
3. Offer the returned email as a proposed update, then write it through your CRM integration after your merge rules pass.

Request budget. One work-email call for the missing field; no phone lookup.

Recipe 05 · Meeting preparation

Prepare a company brief before a meeting

Trigger. A user asks for a brief on a known company.

{
  "website_url": "https://example.com",
  "include_provenance": true
}

Workflow

1. Resolve the company from a confirmed website or company identifier.
2. Use available company fields to populate the brief, keeping retrieval time and any returned source information.
3. If attendee context is also needed, make a separate contact request with include_email: false, include_phone: false and include_profile: true.

Request budget. One company call; an attendee profile is a separate, optional request subject to account permission.

Recipe 06 · AI agent enrichment

Give an agent a focused lookup task

Trigger. A user asks the host to find a work email for a known professional.

{
  "linkedin_url": "https://www.linkedin.com/in/example"
}

Workflow

1. Allow targetwise_find_work_email for the task and provide the known identifier.
2. Read result.structuredContent and check status, data and unresolved_fields.
3. Return the available result to the user. Use a separate application step for any CRM update or message.

Request budget. One MCP tool call; no automatic search loop.

Keep the integration predictable.

For exact schemas and error codes, use the REST reference. For tool discovery and host behavior, use the MCP documentation.

Common questions