1. Clay Native Job Enrichment vs. PredictLeads vs. JobPostings API (HTTP Action)
GTM teams running high-volume outbound in Clay or n8n often burn thousands of dollars per month checking whether target accounts are hiring. Here is how direct HTTP API enrichment compares:
| Capability / Cost Metric | JobPostings API (Clay HTTP / n8n) | Clay Native Find Jobs Waterfall | Legacy Enterprise Intent (PredictLeads / Mantiks) |
|---|---|---|---|
| Starting Price | $19/mo (25K Credits) or $25 PAYG | $149–$800/mo Clay plan + 2–4 Clay credits/row | $500/mo – $1,500+/mo annual contract |
| Cost When 0 Jobs Match | $0.00 (0 Credits deducted) | Often consumes lookup credits or waterfall overhead | Fixed monthly seat/dataset fee |
| Direct ATS Board Coverage | 434 sources (Greenhouse, Lever, Ashby, Workday, iCIMS, Rippling) | Primarily LinkedIn & aggregated scrapes | 150–250 sources (delayed batch sync) |
| Live On-Demand ATS Re-Check | Yes (?refresh=true queries employer ATS live) | No (cached snapshot) | No (weekly or daily batch) |
| Extracted Tech Stack & USD Salary | Included in every record (skills[] + salary{}) | Requires extra AI prompt credits to parse JD | Add-on technographic module ($10K+/yr) |
2. Copy-Paste Clay HTTP API Configuration & n8n Python/JS Node
Add an 'HTTP API' enrichment column in Clay or a Code/HTTP Request node in n8n to fetch active requisitions for any target account or keyword slice:
Clay HTTP API Column Setup + Python / n8n Workflow Script
Query active ATS jobs by company domain or keyword recency and extract ready-to-merge outbound variables (job title, direct ATS URL, USD salary range, and tech stack).
# Clay HTTP API Column Configuration:
# Method: GET
# URL: https://api.jobpostingsapi.com/v1/jobs/search
# Query Params: q="security engineer", posted_since="7d", country="US", limit="5"
curl -sG "https://api.jobpostingsapi.com/v1/jobs/search" \
-H "x-api-key: jp_live_your_api_key" \
--data-urlencode "q=security engineer" \
--data-urlencode "posted_since=7d" \
--data-urlencode "country=US" \
--data-urlencode "limit=5"3. Best Practices for Zero-Waste Clay & n8n Hiring Workflows
Structure your Clay table or n8n cron workflow to maximize reply rates while keeping API credit consumption under $20/month:
- Use Conditional Run Rules in Clay: Set your Clay HTTP API column to run only when {{company_domain}} is present and ICP Score >= 70. Because JobPostings API charges 0 Credits on empty search results, checking non-hiring ICP accounts is 100% free.
- Combine Tech Stack + Seniority Signals: Instead of generic 'We saw you are hiring' openers, reference the exact skills[] array (e.g., Snowflake + dbt + Terraform) and USD compensation band returned by the API to prove domain relevance.
- Verify Stale Requisitions Before Sending: Before enrolling a prospect into a multi-step sequence, pass ?refresh=true to GET /v1/companies/{slug}/jobs to confirm the requisition hasn't already been filled on Greenhouse, Lever, or Ashby.
Interactive Engineering Workbench · GET /v1/jobs/search
Verify real-time latency, pagination math & JSON schema
Frequently Asked Questions
- How do I connect JobPostings API to Clay.com without paying extra Clay credits?
- In any Clay table, click 'Add Column' -> 'HTTP API', set Method to GET, URL to https://api.jobpostingsapi.com/v1/jobs/search or https://api.jobpostingsapi.com/v1/companies/{{domain}}/jobs, and add the header x-api-key: jp_live_your_key. Clay HTTP API columns use your own API key at 0 Clay credits.
- Do I get charged Credits when a target company in my Clay table has 0 open jobs?
- No. JobPostings API uses strict outcome-based credit accounting: 1 Credit = 1 returned job record. When a query returns 0 matching jobs or HTTP 404, 0 Credits are deducted.
- Can I trigger an n8n or Make.com workflow whenever a company posts a new role?
- Yes. Schedule an n8n Cron node every hour to call GET /v1/feeds/new or GET /v1/jobs/search?posted_since=1h with your target role keywords and push matching companies directly into Clay, HubSpot, or Smartlead.
- Does the API return the company's domain name so I can find decision-makers?
- Yes. Every job record includes company.name, company.slug, and company.domain alongside the direct ATS board URL (Greenhouse, Lever, Ashby, Workday, iCIMS, etc.).