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

Inside a CRM add-on or customer-success tool, warn the account owner when a customer advertises a role that asks for experience with a competitor's product, an early churn or displacement signal.

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

Free API key
No credit card
Run your sample

Uses POST /organization_search/, POST /job_search/ · Company enrichment API reference

What it costs: Charged per request: credit pricing.

Job postings API
Company enrichment
API
Embedded in a platform
B2B SaaS

How the data flows

2 inputs → Job postings API + Company enrichment → 4 fields sample data

01 · Inputs

Company domain

example.com

Full name + company

Jane Example · Example Inc.

02 · Forager

Job postings API + Company enrichment POST /organization_search/

Match found

03 · Outputs

Jane ExampleVP Revenue Operations · Example Inc.

posting title: VP Revenue Operations
posting url: example.com
date featured: 2026-10-01
name: Jane Example
mobile: +1 (415) 555-0142
work email: jane@example.com

4 fields in the responseexample data

Steps

Map customer accounts to organization ids with POST /organization_search/ (domains)
Search their active postings with POST /job_search/ (organization_ids, description as a boolean query of competitor names, is_active)
Attach the posting title, url and date_featured to the account record
Notify the account owner and open a save or expansion task

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. Map customer accounts to organization ids with POST
# /organization_search/ (domains)
r1 = requests.post(f"{BASE}/organization_search/", headers=HEADERS, json=body)

# 2. Search their active postings with POST /job_search/ (organization_ids,
# description as a boolean query of competitor names, is_active)
r2 = requests.post(f"{BASE}/job_search/", headers=HEADERS, json=body)

# 3. Attach the posting title, url and date_featured to the account record

# 4. Notify the account owner and open a save or expansion task

# 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

# 2. POST /job_search/
curl -X POST \
  https://api-v2.forager.ai/api/{account_id}/datastorage/job_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
customer domains	`account with matching posting`
competitor product names	`posting title`
	`posting url`
	`date_featured`

Questions about this recipe

Can job postings warn me that a customer is moving to a competitor?

Inside a CRM add-on or customer-success tool, warn the account owner when a customer advertises a role that asks for experience with a competitor's product, an early churn or displacement signal. Account owners hear about a possible switch while there is still time to act, instead of at renewal.

What does it cost to alert account owners when a customer posts a job naming a competitor?

Job postings API: 2 credits per request, charged whether or not data comes back. Company enrichment: 1 credit per request, charged whether or not data comes back. 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 competitor product names and customer domains. You get back account with matching posting, date_featured, posting title and posting URL, as JSON. You also need a Forager API key, which comes with a free account.

How do I search job descriptions for a product name?

Map customer accounts to organization ids with POST /organization_search/ (domains). Search their active postings with POST /job_search/ (organization_ids, description as a boolean query of competitor names, is_active).

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

Yes. Create a free account at app.forager.ai: it comes with $5 in free credits and an API key, and there is no credit card to sign up. Run it on records you already know, or book a demo and send us a list: we run it and show you what we find.

When should I run this workflow?

When a customer account publishes a posting whose description mentions a competitor's product. Account owners hear about a possible switch while there is still time to act, instead of at renewal.

Which Forager products does this recipe use?

Job postings API and company enrichment. Job postings API: search live and historical job postings by company, title and location to spot hiring signals. 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 and called through the API from 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: map customer accounts to organization ids with POST /organization_search/ (domains), search their active postings with POST /job_search/ (organization_ids, description as a boolean query of competitor names, is_active), attach the posting title, url and date_featured to the account record and notify the account owner and open a save or expansion task.

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.

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

How the data flows

Steps

Inputs and outputs

Questions about this recipe

Can job postings warn me that a customer is moving to a competitor?

What does it cost to alert account owners when a customer posts a job naming a competitor?

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

How do I search job descriptions for a product name?

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

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

Merge CRM duplicates that use a personal and a work email

Offer mobile and email enrichment as native actions in a GTM workflow builder

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