This Workato recipe keeps contact roles in Salesforce up to date. On a schedule, it scans the accounts you choose, checks Lusha Signals for promotions and seniority changes, and updates Salesforce when something changed. Reps always know who gained influence, and when.
Auto-update Salesforce roles
Why keep Salesforce roles up to date automatically?
Promotions are strong buying signals, but they’re easy to miss. When a contact moves into a decision-making role, the best time to reach out is short.
Without updates, Salesforce keeps showing old titles, and reps end up targeting the wrong people. This recipe catches those changes and updates Salesforce for you.
What this workflow does
- Runs on a schedule, every 5 days by default, or weekly
- Scans the Salesforce accounts you choose, like open opportunities, ICP accounts, or named accounts
- Checks Lusha Signals for contact promotions and seniority changes
- Updates Salesforce only when a relevant signal is found
- Writes the new role, seniority, promotion date, and a “Buying Power Changed” flag
How to set it up
01
Connect your apps in Workato
Ensure active connections for:
- Salesforce: permission to read and update accounts/contacts
- Lusha: API access for company signals
02
Configure the schedule
Adjust how often the recipe runs:
- Every 5 days (default)
- Weekly for most teams
- More frequent for high-velocity sales motions
Tip: Avoid daily runs unless you have a clear use case—signals don’t change hourly.
03
Define which Salesforce accounts to monitor
In the Salesforce search step, scope accounts by:
- Open opportunities
- Target / ICP accounts
- Strategic or named accounts
This keeps signal monitoring focused and cost-efficient.
04
Configure Lusha signal retrieval
Identify companies using:
- Company domain
- Company name
Retrieve signal types such as:
- Contact promotions
- Seniority changes
05
Review conditional logic
The workflow checks:
- Signal type is present
If true → update Salesforce
If false → skip and move on
You can extend this logic to:
- Only update for senior promotions
- Flag executive-level changes differently
06
Update Salesforce records
Map signal data to:
- Contact role
- Seniority field
- Last promotion date
- Custom “Buying Power Changed” flag
07
Test end-to-end
Run the recipe manually and confirm:
- Promotion signals are detected
- Salesforce records update correctly
- No changes occur when no signal is present
What to do next
- Trigger re-engagement workflows: Notify AEs when a key contact is promoted.
- Create expansion alerts: Flag promotions inside customer accounts for upsell timing.
- Update buying committee views: Surface newly promoted decision-makers automatically.
- Log signals historically: Track promotion trends over time inside Salesforce.
- Combine with other signals: Layer promotions with funding, hiring, or tech changes for stronger intent scoring.
The goal: Buying power changes fast. This play ensures Salesforce reflects who actually has influence today, not who had it six months ago—so sales teams engage with perfect timing.
FAQ
Use this Workato recipe. It checks your Salesforce accounts for promotions with Lusha Signals and updates contact roles automatically.
Every 5 days by default. Weekly works for most teams.
The ones you choose, like accounts with open opportunities, ICP accounts, or strategic accounts.
No. Salesforce is updated only when Lusha finds a relevant signal.
Yes. You can set it to update only for senior promotions, or flag executive-level changes separately.
Ready to run this?
One data connection. Works in Claude, ChatGPT, your CRM, or any agent you build.
