This Workato recipe checks your Salesforce accounts for new Lusha Signals every 5 days. It retrieves hiring, headcount, web traffic, IT spend, and news signals for each account by Lusha Company ID, and updates the account in Salesforce when a signal is found, so reps know which accounts are changing.
Salesforce account auto-updates with Lusha Signals
Why update Salesforce accounts automatically?
Most CRMs show a company as it was on the day someone last edited the record. Companies change fast: they hire, grow, and make the news. Salesforce doesn’t change unless someone updates it by hand.
That’s why account prioritization breaks. Reps work from outdated data and miss accounts that are ready to buy. With this workflow, Salesforce accounts are checked for new signals on a regular schedule, and every account with a signal is updated, so the accounts showing real momentum are easy to spot.
What this workflow does
- Runs on a schedule, every 5 days by default
- Pulls a batch of accounts from Salesforce
- Retrieves hiring, headcount, web traffic, IT spend, and news signals from Lusha for up to 100 companies at a time
- Updates the Salesforce account only when Lusha returns a signal
- Skips accounts with no new signals
Which Salesforce fields it uses
Required
- Lusha Company ID (Lusha looks up signals by this ID)
Signal fields
- Employee count and headcount trend
- Open roles and hiring activity
- Web traffic trend
- IT spend
- Latest company news
Recommended tracking fields
- Last signal update (date and time)
- Latest signal type
How to set it up
01
Start from the Workato template
Copy the recipe from the template into your Workato workspace.
02
Set the schedule
The Trigger runs every 5 days at 12:00 AM by default. Change the interval if you want to check accounts more or less often.
03
Search for accounts in Salesforce
The Search for Accounts in Salesforce action (Batch) pulls the accounts to check. Connect your Salesforce account in this step. Each account needs a Lusha Company ID field, since Lusha looks up signals by that ID. Add filters to limit the search, for example only target or customer accounts.
04
Retrieve company signals from Lusha
The Lusha action retrieves hiring, headcount, web traffic, IT spend, and news signals for up to 100 companies at a time, by Lusha Company ID. Connect Lusha with your API key and map the Lusha Company ID field from the Salesforce search.
05
Check for new signals
The IF condition continues only when Signal type from the Lusha step is present. Accounts with no new signals end here.
06
Update the account in Salesforce
The Update Account in Salesforce action writes the signal data to the account. Map the signal fields (e.g., employee count, hiring activity, web traffic, IT spend, latest news), and set Last signal update and Latest signal type. If these fields don’t exist yet, add them to the Account object first.
07
Test and turn on the recipe
Run the recipe on a small batch of accounts. Confirm that accounts with signals are updated and accounts without signals are skipped, then start the recipe.
What to do next
- Notify account owners: Add a Slack or email step after the update, so the owner sees new signals right away.
- Add thresholds: Act only on high-intent movement, like a large headcount jump, to keep noise down.
- Turn signals into action: Create tasks, add accounts to sequences, or build a “review this account” queue.
The goal: Salesforce stops being a static database and becomes an account radar that stays current.
FAQ
Use this Workato recipe. It checks your Salesforce accounts on a schedule, retrieves signals from Lusha by Lusha Company ID, and updates each account that has a new signal.
Signals are changes Lusha detects at a company. This recipe uses hiring, headcount, web traffic, IT spend, and news signals.
It uses the Lusha Company ID stored on each Salesforce account. Accounts without a Lusha Company ID can’t be checked.
Yes, if your Account object doesn’t already have them. You need a Lusha Company ID field, plus fields for the signal data you want to store, like hiring activity or latest signal type.
Every 5 days at 12:00 AM by default. You can change the schedule in the trigger.
Ready to run this?
One data connection. Works in Claude, ChatGPT, your CRM, or any agent you build.
