Create Recruitment Campaign Watchlist signal

Watch a fixed list of companies and get told when one of them starts hiring in VOLUME - the moment an account staffs up is the moment budget and headcount have just been approved, which is usually the same meeting your budget comes out of.

Two signals sit either side of this one. The Recruitment Campaign signal DISCOVERS companies from filters, where this one starts from your list. The Job Offers Watchlist fires on any single new posting at a company you watch, where this one fires only on a hiring PUSH - a company qualifies only once it has at least minJobCount open roles matching your filters inside the publishedDate window. That threshold is the whole point: one open role is noise, ten is a plan.

Input: companies (a name, a domain, or a LinkedIn company URL per entry, or an object {name, domain, linkedinUrl} carrying all three), minJobCount and optional maxJobCount (the volume band that qualifies a company), publishedDate (the recency window the roles must fall in, e.g. 30d), plus the usual jobTitleInclude / jobTitleExclude, locations and companySizeFilters filters, optional persona targeting (enablePersonaTargeting, targetPersonas, companyOnlyWhenContactsRefused - default false, still deliver the company, with no contact, when every candidate found there was filtered out instead of nothing, requireContact - default false; true = only leads with a contact: a company where nobody matching your personas is found is neither delivered nor charged) and enrichment flags (getEmails, getPhones).

Output: one COMPANY-level lead per qualifying company - not one per posting. Each is pushed to your webhookUrl with a signal object carrying one of the open roles as the evidence, a company object, and contact empty. Turn persona targeting on and the decision-makers matching your targetPersonas are resolved at each company and delivered as person-leads instead.

Only companies that resolve to a WEBSITE are watched: the filtering happens at the job-data source, which matches companies on their domain. An entry given as a bare name starts contributing once its domain resolves, and until then it is listed but not matched. GET /api/v1/watchlists/{signalId}/companies is the one place that shows what is actually being watched - check it first if the signal delivers less than you expected.

companies is consumed into the watchlist, so it is NOT echoed back in the config of this or any later response - the watched list has exactly one home. Add or remove companies with POST / DELETE on /api/v1/watchlists/{signalId}/companies; an edit re-scopes what is monitored automatically, with no need to recreate the signal.

Use cases:

• Budget-approved timing on named accounts - a company hiring ten roles at once has just had headcount signed off, which is the same meeting your budget comes out of; the volume is the qualifier a single posting cannot give you.
• Scaling customers, not just new ones - watch your own base and treat a hiring push as the moment a team outgrows the plan it is on, ahead of the renewal conversation.
• Sell to the build-out - recruiters, staffing, onboarding, equipment, workspace and payroll all have a buying window that opens when the campaign starts, not when the seats are filled.
• Competitor momentum - a competitor staffing a whole function tells you where they are betting, early enough to answer it.