Recipe · n8n + REST
Fresh segments for client campaigns, weekly
One scheduled pull per client ICP per week. A segment nobody else emails yet, with the posting as the opener. This play replaces list-buying and VA hours.
The loop
Cron → search → dedupe → sequencer. Four n8n nodes per client. The search returns one row per company with its matching active reqs, so the output maps 1:1 to a campaign audience.
Step 1: prove the query from your terminal
Sign up and copy the API key on screen: the free tier needs no card. Tune the role and geo from your terminal until the rows match your client's ICP.
curl -s 'https://api.reqbeat.com/v1/reqs/search?q=sales&geo=United+Kingdom&limit=10' \
-H "X-API-Key: $REQBEAT_API_KEY"Step 2: schedule it in n8n
When the query is right, put the same search on a Monday
cron. Paginate with cursor, not a larger limit. Oversized
pages are rejected, not truncated.
// 1. Cron: Mondays 07:00
// 2. HTTP Request: header X-API-Key
GET https://api.reqbeat.com/v1/reqs/search
?q=sales&geo=United+Kingdom
&since={{ $today.minus(7, 'days') }}
// 3. Code: drop company_ids seen last week
// 4. Instantly / Smartlead: import segmentStep 3: dedupe and load
Keep a per-client set of contacted company_ids in an n8n static-data
store or a sheet. New-this-week rows become the segment. The matched posting becomes
the personalization line.
Economics per client
- Search bills per sourced company row, at $0.10 per row. A weekly 50-company segment is a small line item. An empty week costs nothing.
- Every plan has a hard spend cap already set. A runaway workflow stops instead of running up a bill.
- One account serves many client workspaces. The Starter plan's allowances cover several weekly segments before metering starts.
Why clients renew on it
The targeting story is simple: "we email companies that posted a matching req this week, and here is the posting". Fresh segment, visible receipt, measurable reply lift in one campaign cycle.