Keep one canonical company record per account in a CRM add-on

Give a CRM data-quality product a licensed company layer, so duplicate and misspelled accounts collapse to one company and firmographics stay filled in.

Get a free API key + $5 Get a sample run

Free API key
No credit card
Run your sample

Tools named: LinkedIn

Uses POST /organization_search/ · Company enrichment API reference

What it costs: Charged per request: credit pricing.

How the data flows

2 inputs → Company data feed + Company enrichment → 5 fields sample data

01 · Inputs

Company

Example Inc.

company feed

company-feed-2026-10-01.jsonl

02 · Forager

Company data feed + Company enrichment POST /organization_search/

Match found

03 · Outputs

Jane ExampleVP Revenue Operations · Example Inc.

industry: Software
employees range: 120
name: Jane Example
title: VP Revenue Operations
mobile: +1 (415) 555-0142
work email: jane@example.com

5 fields in the responseexample data

Steps

Load company_feed and index it by domain, linkedin_slug and forager_id
Match each customer's accounts by domain or LinkedIn company URL and assign forager_id
Flag accounts that share a forager_id as duplicates and propose merges
Resolve accounts the feed did not match with POST /organization_search/ (domains, linkedin_public_identifiers) and fill industry, employees_range and addresses

import json, os, requests

BASE = "https://api-v2.forager.ai/api/{account_id}/datastorage"
HEADERS = {"X-API-KEY": os.environ["FORAGER_KEY"]}
body = json.load(open("request.json"))  # request fields: see the API reference

# 1. Load company_feed and index it by domain, linkedin_slug and forager_id

# 2. Match each customer's accounts by domain or LinkedIn company URL and
# assign forager_id

# 3. Flag accounts that share a forager_id as duplicates and propose merges

# 4. Resolve accounts the feed did not match with POST /organization_search/
# (domains, linkedin_public_identifiers) and fill industry, employees_range
# and addresses
r1 = requests.post(f"{BASE}/organization_search/", headers=HEADERS, json=body)

# 1. POST /organization_search/
curl -X POST \
  https://api-v2.forager.ai/api/{account_id}/datastorage/organization_search/ \
  -H "X-API-KEY: $FORAGER_KEY" \
  -H "Content-Type: application/json" \
  -d @request.json

Generated from the recipe stepsRequest fields: API reference

Run it yourself: Company enrichment API reference

Get a free API key + $5 Get a sample run

Free API key
No credit card
Run your sample

Inputs and outputs

Inputs	Outputs
CRM accounts	`forager_id per account`
company feed	`duplicate groups`
	`industry`
	`employees_range`
	`addresses`

Questions about this recipe

How can a CRM add-on dedupe accounts using a company dataset?

Load company_feed and index it by domain, linkedin_slug and forager_id. Match each customer's accounts by domain or LinkedIn company URL and assign forager_id.

What does it cost to keep one canonical company record per account in a CRM add-on?

Company enrichment: 1 credit per request, charged whether or not data comes back. Company data feed is a flat annual licence, global or regional, not priced in credits. Growth's 8,250 monthly credits cover 8,250 company lookups, or a mix. Self-serve plans are Starter, Growth, Pro and Scale. See plans and prices

What do I need to run this recipe, and what comes back?

You send company feed and CRM accounts. You get back addresses, duplicate groups, employees_range and forager_id per account, as JSON. You also need a Forager API key, which comes with a free account.

Which company data feed gives a stable company id?

This recipe uses Forager Company data feed and Company enrichment. Company data feed: A licensed file of 65M+ company profiles and firmographics, delivered to Snowflake or S3 on a schedule. Give a CRM data-quality product a licensed company layer, so duplicate and misspelled accounts collapse to one company and firmographics stay filled in.

Is there a free way to try Forager on this workflow?

Yes. Request a sample extract of the company data feed on a 30-minute call and check the fields against your own records before you license it.

When should I run this workflow?

When a customer connects their CRM, or a feed delivery updates company records. Customers work from one record per company, and routing and reporting run on complete firmographics.

Which Forager products does this recipe use?

Company data feed and company enrichment. Company data feed: a licensed file of 65M+ company profiles and firmographics, delivered to Snowflake or S3 on a schedule. Company enrichment: firmographics for a company from its domain or name: industry, headcount, locations, growth and open roles.

How do I know the data is right?

The test that counts is your own: send a list of profiles you care about. We run it and show you what we find, number by number, so you can measure hit rate and connect rate yourself.

Which tools can run this workflow?

Native in Clay, partner-built in Deepline and Cargo, delivered as a data share to Snowflake, Databricks and Amazon S3 and called through the API from Google BigQuery, Make, n8n and your own code. Or call the endpoints in the steps above from your own code with one API key.

How many steps is this workflow?

4 steps: load company_feed and index it by domain, linkedin_slug and forager_id, match each customer's accounts by domain or LinkedIn company URL and assign forager_id, flag accounts that share a forager_id as duplicates and propose merges and resolve accounts the feed did not match with POST /organization_search/ (domains, linkedin_public_identifiers) and fill industry, employees_range and addresses.

Is there a contract or minimum commitment?

No contract to start: a free account comes with $5 in credits. To keep using Forager, choose a monthly or yearly plan. Monthly plans cancel anytime and unused credits roll over; yearly plans grant all credits upfront and cost 10% less. Larger volumes are agreed with our team.

Can we show Forager data inside our product?

Yes, under platform terms. Self-serve plans cover internal use by your own team. Showing Forager data to your users, or passing records on, is licensed separately: talk to sales about volume and which fields your users need to see.

Keep one canonical company record per account in a CRM add-on

How the data flows

Steps

Inputs and outputs

Questions about this recipe

How can a CRM add-on dedupe accounts using a company dataset?

What does it cost to keep one canonical company record per account in a CRM add-on?

What do I need to run this recipe, and what comes back?

Which company data feed gives a stable company id?

Is there a free way to try Forager on this workflow?

When should I run this workflow?

Which Forager products does this recipe use?

How do I know the data is right?

Which tools can run this workflow?

How many steps is this workflow?

Is there a contract or minimum commitment?

Can we show Forager data inside our product?

More recipes for CRM add-ons

Detect CRM contacts who changed jobs and alert on moved champions

Pre-build each new customer's TAM on day one inside an AI-native CRM

Power a CRM's native contact-enrichment button

Alert account owners when a customer posts a job naming a competitor

Merge CRM duplicates that use a personal and a work email

Build natural-language candidate search on a licensed people feed

Put people, company and job data your users can act on inside your product