Lusha Signals turn real business movement — job changes, promotions, hiring spikes, new roles — into real-time API events your GTM systems can act on.
You can enrich contacts and companies with four verified signal types: job change, promotion, headcount growth, and new job listings.
Revenue teams use Signals to re-engage past buyers, route high-intent accounts, accelerate pipeline, and catch churn risk early.
The API is simple to implement, structured for scoring and routing, and integrates with CRMs, automations, and no-code tools like Make, Zapier, and n8n.
Fit tells you who. Signals tell you when.
Explore the Lusha Signals API to bring timing into your GTM workflows.
Real-time movement. Real-world context. Smarter GTM decisions.
Static CRM data ages fast. Roles shift, budgets change, teams grow, and companies open new initiatives every week. When your CRM stays still, you miss the moments that matter.
The Lusha Signals API turns real business movement into actionable events your GTM teams can use right away. Instead of guessing when an account is ready, you get verified signals that show exactly when to act.
Today, we’re introducing a simple way to bring real-time intent into your CRM, scoring models, routing rules, and automation tools without adding operational overhead.
Why signals matter
Every revenue team works with the same challenge: figuring out when a buyer is open to a conversation.
A contact gets promoted.
A past champion moves companies.
A team starts hiring for a relevant role.
A company shows early signs of growth or risk.
These moments drive intent. They say more about readiness than any static data field. The Signals API captures these events the moment they happen and makes them usable across your GTM systems.
What Lusha Signals API gives you
Lusha Signals are verified, structured events pulled directly from the Lusha data graph. They’re refreshed continuously, delivered through a predictable schema, and built for operational workflows.
You can enrich contacts and companies with four core signal types:
Contact-level signals
- Job Change: Know when past buyers land at new companies.
- Promotion: Catch decision-makers at the start of a new role.
Company-level signals
- Headcount Growth: Spot companies adding budget and expanding teams.
- New Job Listings: Identify new initiatives by watching key roles they’re hiring for.
These signals show you who is in motion and what that motion means for your pipeline.
How GTM teams are using Signals today
Teams are already building stronger workflows using four of the most reliable buying triggers in B2B. With the Signals API, these motions become fully automated.
Re-engage past buyers who changed companies
Your strongest warm leads are buyers who already know you. When they move companies, you can reach out fast.
Time outreach around promotions
New leaders reassess tools and budgets in their first 60–90 days. Promotion signals help you meet them at the right moment.
Catch accounts in expansion mode
Headcount growth often means more budget, new tools, and upcoming initiatives. Route these companies to sales before competitors notice.
Trigger outreach when new initiatives launch
New job listings highlight what teams are trying to solve. If they’re hiring for problems your product solves, it’s the right time to reach out.
Build dynamic lead scoring models
Signals let you prioritize based on movement: promotions, job changes, hiring spikes, and company growth patterns.
Create early churn alerts
When decision-makers change roles or accounts slow down hiring, you can give CSMs an early signal to take action.
How the API works
You can call the Signals API using:
- IDs (person or company)
- Identifiers (email, domain, LinkedIn URL, name)
- Search endpoints for broader matching
- Time filters to control your signal window (default: 6 months)
- Filters to choose only the signal types you want
A typical search call looks like this:
Responses always return a consistent schema including personId or companyId, signal date, and both previous and current metadata.
You can run Signals in any environment: Salesforce, HubSpot, Snowflake, Make, Zapier, n8n, Python, or Google Sheets.
Why Lusha signals are different
The power comes from reliability and structure not volume.
- Verified, not scraped: powered by the Lusha data graph for clean, trusted signal quality.
- Structured and predictable: built to work inside scoring models, routing rules, and automations.
- API-first design: created for GTM workflows and data pipelines.
- Real-time delivery: no batch delays, uploads, or manual checks.
- Flexible integration: enrich contacts, companies, CRMs, spreadsheets, and workflows with a single call.
- Low lift: works with or without developers.
What it unlocks for revenue teams
With the Signals API, you can:
- automate timing-based outreach
- improve prioritization without extra research
- build workflows triggered by real events
- route high-intent accounts instantly
- support CS with early churn insights
- keep your CRM aligned with buyer movement
- uncover warm paths that would otherwise stay buried
Signals make CRMs dynamic again. They reflect what buyers are doing not just who they are.
The bottom line
Fit tells you who.
Signals tell you when.
Timing shapes pipeline. When you combine fit with movement, your team reaches buyers at the exact moment they’re ready.
Teams using Lusha Signals see the same pattern:
More relevant outreach. Fewer missed windows. Cleaner automation. Faster pipeline.
Get started
You can start pulling signals today.
View the full documentation or plug the API directly into your CRM and automations.
Keep reading:
How Lusha uses job-change signals to re-activate high-intent prospects
Lusha + monday CRM: keep every board enriched with verified data
Waterfall data enrichment: why streaming data beats static stacking
How one builder automated inbound lead qualification with Lusha’s API and n8n
FAQs
Lusha Signals surface verified business changes — not inferred behavior.
Job changes, promotions, hiring activity, and new roles reflect real movement inside accounts. These signals are clean, structured, and ready for scoring, routing, and automation.
The API currently supports four signal types:
- Job change
- Promotion
- Headcount growth
- New job listings
You can retrieve them at the contact or company level, depending on the signal.
Signals are powered by the Lusha data graph and refreshed continuously. All contact-level signals rely on publicly available career updates; company-level signals are validated across multiple sources.
No. You can use the API in code, or you can run Signals through Make, Zapier, n8n, or other no-code tools.
Teams use both depending on workflow size.
Yes. You can use Signals in your routing rules, lead scoring models, ABM workflows, and enrichment logic. Most GTM teams pipe Signals into Salesforce, HubSpot, Google Sheets, or Snowflake for downstream automation.
Yes. The API uses scoped, secure access and only surfaces publicly available career updates at the contact level. Company-level signals rely on aggregated, non-personal data.
- 1 credit per enrichment
- 1 credit per 25 search results
These credits follow the same model as other Lusha API calls.
You can set startDate and endDate in your request.
If you don’t specify one, the API defaults to a six-month window.
Yes. Use /signals/filters/:objectType to view what’s available.
You can retrieve only the signal types you want.
You can pass:
- Person IDs
- Company IDs
- Domain
- LinkedIn URL
- Company name
The search endpoints handle matching.
Salesforce, HubSpot, Snowflake, Google Sheets, Make, Zapier, n8n, or any custom backend.
