Build account org charts and decision-maker search from fresh employment data
Let a prospecting database show a current org chart for each account (who reports where, who joined, who left) and find decision makers by function and seniority.
- Free API key
- No credit card
- Run your sample
A selection of teams that run this job on Forager · plus other sales-tech platforms
Uses POST /person_role_search/, POST /person_detail_lookup/ · People search API reference
What it costs: Charged per request: credit pricing.
- People data feed
- Company data feed
- People search
- Person enrichment
- Data feed
- Feed licensee
- Sales tech
How the data flows
POST /person_role_search/ - name
- Lee Sampler
- title
- VP Revenue Operations
- mobile
- +1 (312) 555-0107
- work email
- lee@example.com
- company
- Example Inc.
Steps
- Ingest
people_feedandcompany_feedand key people to accounts by current employer - Infer department and seniority from
role_titleand build function trees per account - Refresh on each delivery: mark leavers, add new joiners, and update titles
- Fill gaps on demand with
POST /person_role_search/andPOST /person_detail_lookup/when a user opens an account
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. Ingest people_feed and company_feed and key people to accounts by # current employer # 2. Infer department and seniority from role_title and build function trees # per account # 3. Refresh on each delivery: mark leavers, add new joiners, and update # titles # 4. Fill gaps on demand with POST /person_role_search/ and POST # /person_detail_lookup/ when a user opens an account r1 = requests.post(f"{BASE}/person_role_search/", headers=HEADERS, json=body) r2 = requests.post(f"{BASE}/person_detail_lookup/", headers=HEADERS, json=body)
# 1. POST /person_role_search/ curl -X POST \ https://api-v2.forager.ai/api/{account_id}/datastorage/person_role_search/ \ -H "X-API-KEY: $FORAGER_KEY" \ -H "Content-Type: application/json" \ -d @request.json # 2. POST /person_detail_lookup/ curl -X POST \ https://api-v2.forager.ai/api/{account_id}/datastorage/person_detail_lookup/ \ -H "X-API-KEY: $FORAGER_KEY" \ -H "Content-Type: application/json" \ -d @request.json
Run it yourself: People search API reference
- Free API key
- No credit card
- Run your sample
Inputs and outputs
| Inputs | Outputs |
|---|---|
| account list | org chart |
| people_feed | decision makers by function |
| company_feed | joiners and leavers |
Questions about this recipe
Where do sales tools get the data for company org charts?
This recipe uses Forager People data feed, Company data feed, People search and Person enrichment. People data feed: A licensed file of 800M+ professional profiles, refreshed on a schedule and delivered to Snowflake or S3. Let a prospecting database show a current org chart for each account (who reports where, who joined, who left) and find decision makers by function and seniority.
What does it cost to build account org charts and decision-maker search from fresh employment data?
People search: people search 1 credit per request and people search: role details 1 credit per request, charged whether or not data comes back. Person enrichment: 1 credit per request, charged whether or not data comes back. People data feed is a flat annual licence, global or regional, not priced in credits. Growth's 8,250 monthly credits cover 8,250 search requests, 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 account list, company_feed and people_feed. You get back decision makers by function, joiners and leavers and org chart, as JSON. You also need a Forager API key, which comes with a free account.
How can I keep account org charts current as people change jobs?
Ingest people_feed and company_feed and key people to accounts by current employer. Infer department and seniority from role_title and build function trees per account.
Is there a free way to try Forager on this workflow?
Yes. Request a sample extract of the people 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?
Users complain that org charts list people who left, or a database adds org-chart and decision-maker views. Sales teams reach current decision makers and stop emailing people who left.
Which Forager products does this recipe use?
People data feed, company data feed, people search and person enrichment. People data feed: a licensed file of 800M+ professional profiles, refreshed on a schedule and delivered to Snowflake or S3. Company data feed: a licensed file of 65M+ company profiles and firmographics, delivered to Snowflake or S3 on a schedule.
How do you check data quality?
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.
How do I build company org charts from employee data?
Ingest people_feed and company_feed and key people to accounts by current employer. Infer department and seniority from role_title and build function trees per account.
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, your own code, Make and n8n. Or call the endpoints in the steps above from your own code with one API key.
How many steps is this workflow?
4 steps: ingest people_feed and company_feed and key people to accounts by current employer, infer department and seniority from role_title and build function trees per account, refresh on each delivery: mark leavers, add new joiners, and update titles and fill gaps on demand with POST /person_role_search/ and POST /person_detail_lookup/ when a user opens an account.
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.
Written answers are not available right now. The matching pages above still help, or book a demo and ask the team.
- $5 free credits
- No credit card
- Run your sample
A selection of teams that run this job on Forager · plus other sales-tech platformsA selection of teams using Forager
-
Clay - GTM workflow builders
Selected use case: Forager mobile numbers, emails and people data inside Clay tables.
-
Juicebox - AI candidate sourcing
Selected use case: Forager data behind its PeopleGPT search and sourcing agents.
-
Nooks - Power & parallel dialers
Selected use case: mobile numbers inside their dialer.
-
Vieu - ABM & intent
Relationship-mapping platform that helps sales teams and AI agents find warm introductions.
-
Aydentify - Lead databases
Lead-discovery tool that shows ingredient and packaging suppliers which consumer brands use their products.
-
HubSpot - CRM add-ons
Selected use case: enriching contact and company records with people, company and job-posting data.
-
Bitscale - GTM workflow builders
Selected use case: Forager in its contact waterfall for mobile numbers.
-
Orbital - Lead databases
Selected use case: contact lookups in its enrichment waterfall, for teams selling to local businesses.
More recipes for lead databases
-
Find the owner's mobile for local SMB accounts
-
Trigger outreach on new hires and open roles at target accounts
-
Prospect contacts at a target domain by title and country via API
-
Find fleet managers across title variants for B2B vehicle sales
-
Connect ingredient and packaging suppliers with brand-side product developers
-
Detect CRM contacts who changed jobs and alert on moved champions
