This workflow runs on a daily scheduled cadence. It checks every account with an open opportunity against Lusha’s signal layer, writes new signals directly to the Salesforce opportunity record, and alerts the AE when a high-priority signal fires at an active deal account.
1
Trigger — Scheduled Flow runs daily
A Scheduled Flow runs every morning and queries for all open Opportunity records — stage not equal to Closed Won or Closed Lost. For each opportunity, it retrieves the associated Account to use as the Lusha signal lookup identifier.
2
Action — Call Lusha API to check account signals
For each account, the Flow calls Lusha’s signals endpoint with the company name or domain. Lusha returns all active buying signals — funding events, executive moves, hiring surges, intent signals, and tech stack changes — scored and dated.
3
Action — Filter for new signals only
The Flow compares the signal dates against the last signal check timestamp on the opportunity record. Only signals that appeared since the last check are processed — so the AE sees what’s new, not a repeat of signals already logged.
4
Action — Write signals to the opportunity record
New signals are written to a custom signal log field on the Opportunity record — signal type, score, date, and a one-line description. The latest signal summary is written to a dedicated field visible in the opportunity layout so the AE sees it immediately when they open the record.
5
Action — Create task and fire alert for high-priority signals
If a signal scores above your alert threshold — funding event, executive hire, or intent score above 70 — a high-priority task is created for the AE and an optional Slack notification fires with the signal details and a link to the opportunity.
6
Output — AE sees live signals on every open deal
The AE opens a deal record and sees exactly what has happened at the account since the last call — without checking a separate tool, without manually researching the account, and without waiting for the manager to ask in a pipeline review.
What you’ll get back
An opportunity record that looks like this when the AE opens it before a call:
| Salesforce field | Value |
|---|
| Opportunity name | [Deal name] |
| Stage | Stage 3 — Proposal |
| ACV | $42K |
| Close date | [date] |
| Lusha — Latest signal | ⚑ Series B closed — $22M — 8 days ago |
| Lusha — Signal score | High |
| Lusha — Signal log | Series B $22M (8 days ago) · New CRO hired (14 days ago) · 8 SDR roles posted (11 days ago) |
| Lusha — Last signal check | [date] |
| Lusha — Alert fired | ✓ Task created · Slack notification sent |
Task created for AE
| Field | Value |
|---|
| Priority | High |
| Subject | ⚑ New signal — [Account name] — Series B closed |
| Due date | Today |
| Description | [Account name] just closed a Series B — $22M raised. A new CRO joined 14 days ago and 8 SDR roles have been posted since. This account is in active investment mode. Re-engage this week with an updated business case tied to the new funding and scaling motion. |
| Related to | [Deal name] opportunity |
Slack notification (if configured)
⚑ New buying signal — open deal
Account: [Account name]
Deal: [Deal name] — Stage 3 — $42K
Signal: Series B closed — $22M — 8 days ago
Additional signals: New CRO (14 days ago) · 8 SDR roles posted (11 days ago)
Signal score: High
Re-engage this week — the timing window is open.
View opportunity in Salesforce →
Build it
Step 1 — Add signal fields to the Opportunity object
In Salesforce Setup, go to Object Manager → Opportunity → Fields & Relationships. Add the following custom fields:
| Field label | Field type | API name |
|---|
| Lusha — Latest signal | Text | Lusha_Latest_Signal__c |
| Lusha — Signal score | Picklist (High / Medium / Low / None) | Lusha_Signal_Score__c |
| Lusha — Signal log | Long Text Area | Lusha_Signal_Log__c |
| Lusha — Last signal check | Date/Time | Lusha_Last_Signal_Check__c |
| Lusha — Alert fired | Checkbox | Lusha_Alert_Fired__c |
| Lusha — Alert threshold | Picklist (High only / High and Medium) | Lusha_Alert_Threshold__c |
Step 2 — Build the Scheduled Flow
In Salesforce Flow Builder, create a new Scheduled Flow:
- Schedule: Daily — recommended 5am so signals are ready before the working day starts
- Query: Opportunity records where StageName not in (‘Closed Won’, ‘Closed Lost’)
- Loop: iterate through each opportunity
- For each opportunity: HTTP Callout to Lusha signals endpoint with Account.Website or Account.Name
- Filter response: keep only signals where signal date is after Lusha_Last_Signal_Check__c
- Score signals: High if funding event or executive hire, Medium if hiring surge or intent above 60, Low if tech stack change
- Update Records: write signal summary, score, and log to opportunity fields, update last check timestamp
- Decision: if signal score is High or meets alert threshold — create Task and fire Slack notification
- Save and activate
Step 3 — Add signal fields to the opportunity page layout
In Salesforce Setup, go to Object Manager → Opportunity → Page Layouts. Add the Lusha signal fields to a dedicated section near the top of the layout — “Lusha Intelligence” — so the AE sees the signal summary immediately when they open the record. The Latest Signal and Signal Score fields are the most important to surface prominently.
Step 4 — Configure alert thresholds
Set the Lusha_Alert_Threshold__c field on each opportunity based on the deal’s value and stage. High-value deals in late stages should alert on any High signal. Earlier-stage deals can alert on High signals only to reduce noise. You can also build a Flow rule that automatically sets the alert threshold based on ACV — deals above $50K alert on High and Medium, deals below $50K alert on High only.
Step 5 — Test with a live opportunity
Open a test opportunity linked to a company you know has recent signal activity. Manually trigger the Flow from the debug panel. Confirm the signal fields populate correctly, the signal log is appended rather than overwritten, and the task is created with the right priority and description. Full troubleshooting guidance at docs.lusha.com/guides.
Example outputs in this workflow are illustrative — they reflect the structure, fields, and format of real Lusha API output, but were not pulled from a live session. Build this workflow with your own Lusha API key and Salesforce org to see live results.
