How do I trigger Salesforce automation from a score change?

Trigger Salesforce automation from a score change by building record-triggered Flows that fire when a Fit or Health score crosses a threshold or a tier flips, creating tasks, sending alerts, and enrolling accounts in Revenue Plays without anyone watching a dashboard. Automation on the score change is what turns a number into action.

This guide covers the Flow mechanics: the triggers, entry conditions, and guardrails. For the concept of working a scored queue, see turning a score into action; for a full build, see building your first Revenue Play.

What can a score change trigger?

How do I build the Flow?

Use a record-triggered Flow on the Account or Contact set to run when the record is updated to meet the condition. Point the entry condition at the SignalRx score or tier field, and for a Revenue Play membership field use contains rather than equals, because that field holds several play names at once. Then do the obvious thing: create a Task, send an alert, add to a Campaign, or reassign the owner.

How do I keep automation from misfiring?

Fire on the change, not on every recompute, and add guardrails, no repeat within a window and skip unscored accounts, so a nightly refresh does not spam tasks. A DSO rebrand that re-enriches dozens of locations at once should not generate dozens of duplicate alerts. These are the same guardrails as the churn alerts.

What does this depend on?

Scores written to native fields (writing scores back), because a Flow can only act on fields it can see, the same fields that carry the Fit and Health scores. Those scores are trustworthy triggers only because of what feeds them: SignalRx scores both accounts and contacts by weighing public healthcare data against your own internal signals of revenue, support, and product usage tracked over time, with inference deciding which source to trust, and it fills sparse records across sources first so even a thin account can cross a threshold and enroll rather than sit unscored. The resulting scores, segments, and tags land on native Salesforce fields as Revenue Plays and list views, which is exactly what a Flow reads.

Key takeaways

• Fire a record-triggered Flow on a score or tier change event.
• Use contains on play membership fields, and add guardrails so recomputes do not spam tasks.
• It depends on scores living on native fields.

See it in action: Discover High-Fit Prospects with SignalRx.

Related: How do I turn a score into action? and How do I write scores back to Salesforce?