Hiring Spike for a Concept
If multiple job posts for the same concept show up, they are building or scaling around that initiative.
Sentence: Companies mentioning [term] across multiple job posts (configurable threshold + time window)
Examples:
- term=“ERP Migration”, count_threshold=5, window_days=90
- term=“Outbound Sales”, count_threshold=10, window_days=30
The term field accepts variants, the agent matches semantically.
Optional descriptive_icp helps you specify a Company Category to target. It can be any company description in natural language (a category, industry, or business model), but never firmographic filters like employee count, location, or funding, which belong only in your ICP (icp_id). The items below are just examples of possible descriptive ICPs.
Examples: B2B SaaS Companies, B2B Fintech Companies, Neobanking Companies, B2B Customer Support SaaS Companies, Health-tech SaaS companies that sell to dentists, or Companies that offer Developer Observability Solutions.
Firmographic criteria such as funding, employee count, and company locations are set via your ICP (using icp_id), not as natural-language parameters. Repeating it in natural language will harm performance.
Headers
Body
Sentence: [descriptive_icp] companies mentioning [term] in [count_threshold]+ job posts in [window_days] days
Detect companies with concept spikes - a keyword or concept appearing repeatedly across a company's job posts within a time window.
Name/identifier for this signal run
The concept or keyword to detect spikes for. Examples: 'kubernetes migration', 'AI governance', 'ERP modernization'.
Minimum number of matching job posts to qualify as a spike. Must be >= 2.
x >= 2Time window in days to count posts within. Range: 1-365.
1 <= x <= 365Helps you specify a Company Category to target. It can be any company description in natural language (a category, industry, or business model), but never firmographic filters like employee count, location, or funding, which belong only in your ICP (icp_id). The items below are just examples of possible descriptive ICPs. Examples: B2B SaaS Companies, B2B Fintech Companies, Neobanking Companies, B2B Customer Support SaaS Companies, Health-tech SaaS companies that sell to dentists, or Companies that offer Developer Observability Solutions. Optional - when omitted, searches across all industries.
ICP ID for firmographic filtering. Required unless accounts are provided.
Skip blocklist, deduplication, and industry checks for faster time-to-first-result. Tradeoff: may surface blocklisted or duplicate accounts.
Upload a list of accounts (website and/or linkedin_url) to run the signal against. When provided, trait search is skipped and these accounts are used directly. At least one of icp_id or accounts must be provided.
Run this signal daily to discover new results (default: false, runs once)
Audience name for auto-adding discovered accounts (default: ' - Accounts')
Audience name for people enrichment (default: ' - People')
Credit limit for this signal. Signal stops once this many credits are consumed.
Auto-add discovered accounts to CRM in safe mode. New accounts are created; existing accounts are enriched without ownership changes.
Enrich discovered people with work emails. Requires enable_safe_crm_addition to be true.
Enable advanced LLM-based people finder for deeper people discovery.
Response
Successful Response
Common response shape for signal deployment endpoints. Returns at minimum the signal_id and a status. Some agents return additional fields (e.g. message, campaign_id) which are not documented in this shape.