Objective

To build a Record-Triggered Flow that runs when a SalesWings Prospect Score meets or exceeds a defined value, and sends an alert (email or notification) to the right recipients.

Before You Begin

Before starting, ensure you have:

Completed setup of the Alerter Subflow (see The Alerter Subflow article).
Access to the SW Prospect Score or SW Score object in Salesforce.
Defined which score name and value threshold should trigger alerts.
Appropriate user permissions to create and modify Flows.

When an Unmapped Score Reaches a Value

Step 1: Create a Record-Triggered Flow

From Setup, go to Process Automation → Flows → New Flow.
Select Record-Triggered Flow and click Create.

Step 2: Configure the Entry Conditions

Monitored Object:
Select SW Prospect Score (saleswings__Prospect_Score__c) as the triggering object.
Trigger Criteria:
Set the flow to run when a record is created or updated.
Formula Condition:
Choose Formula Evaluates to True and define your condition using the following format:
```
{!$Record.saleswings__Score__r.Name} = 'Name of the score' && {!$Record.saleswings__Value__c} >= 10
```
Replace 'Name of the score' and the threshold value (10) with your desired criteria.
Optimization:
Select Optimize the Flow for Actions and Related Records so the alert is triggered after the record is saved.

Step 3: Fetch Related Leads and Contacts

Because a Prospect Score can be linked to multiple Leads or Contacts, you’ll need to fetch all related records.

Add a Get Records element to retrieve SW Score Records (saleswings__Prospect_Instance__Score__c).
Configure the conditions:
- Field: saleswings__Prospect_Score__c
- Operator: Equals
- Value: {!$Record.Id}
Choose to Get All Records, or limit the number if you expect many associated Leads/Contacts.
Store the fields saleswings__Contact__c and saleswings__Lead__c for use later in the flow.

Step 4: Loop Through the Score Instances

Since multiple records may be returned, add a Loop element to iterate through each instance of the score.

Within the loop, follow a similar structure to the Tag Notification Flow:

Identify whether the instance relates to a Lead or a Contact.
Retrieve the corresponding record information (e.g., Owner, Name).
Use Assignment elements to set the alert variables (targetId, alertRecipientIds, alertSubject, etc.).
Invoke the Alerter Subflow to send the alert.

Before each new loop iteration, use an Assignment element to clear the recipientIds variable, preventing the previous alert’s recipients from carrying over.

Step 5: Diagram Overview

Your final flow should include:

A Get Records element fetching related score instances
A Loop element processing each instance
Branch logic to handle Leads and Contacts
The Alerter Subflow to send alerts
An Assignment element resetting variables before the next iteration

When a Mapped Score Reaches a Value

If your SalesWings score is directly mapped to a Lead or Contact (for example, the main SalesWings Score), you can simplify the setup.

Create two Record-Triggered Flows—one for Leads and one for Contacts.
Set the trigger on the Lead or Contact object.
Configure the entry conditions directly using fields available on those records.

Diagram:

Advanced Scenario: Multiple Conditions

You can also trigger a notification when multiple criteria are met—for example:

A score reaches a threshold and
A specific SalesWings Tag is also assigned.

This setup requires a more complex flow combining logic from both the Tag and Score workflows.
If you need assistance designing multi-condition flows, please reach out to SalesWings Customer Support.

Result

Your Salesforce flow is now set up to automatically send alerts when a prospect’s (or lead/contacts) SalesWings Score reaches or exceeds your defined threshold.
Whether you use it for individual score triggers or combined conditions, this automation ensures your team never misses a high-value engagement opportunity.