Contact record match flow
Note
This flow is self-documenting and should be viewed within Salesforce (Setup > Process Automations > Flows). This document is to support working through a visual flow. Please note: the flow commentary is produced using AI.
Overview#
Flow name: MoveData_Donation_Contact_Duplicate Label: [MoveData] General: Contact - Record Match Type: Auto-Launched Flow Template API version: 49.0 Status: Active
This flow performs duplicate detection for contact records by using platform keys to identify existing contacts in Salesforce, enabling proper record matching and preventing duplicate creation.
If there is no match, MoveData will execute the Salesforce Duplicate Detection rules after the flow (if configured).
Purpose#
The flow provides duplicate detection capabilities that:
- Uses generated platform keys to look up existing contact records
- Checks the platform key lookup system for matches
- Returns Salesforce Record IDs when duplicates are found
- Supports both Salesforce Key and Platform Key lookup strategies
- Implements MoveData break functionality for advanced flow control
Salesforce fields#
This flow interacts with the Contact Platform Key system and its related fields. Below is a mapping of all fields utilised:
| Field API name | Field type | Purpose in flow |
|---|---|---|
| Platform Key System | Text | Stores external platform identifier for matching |
Input variables#
| Variable | Type | Required | Description |
|---|---|---|---|
SalesforceKey |
String | No | Existing Salesforce Record ID (if known) |
PlatformKey |
String | Yes | Generated platform key for lookup matching |
Custom_MovedataBreak |
Boolean | No | MoveData break control flag |
Output variables#
| Variable | Type | Description |
|---|---|---|
Result |
String | Salesforce Record ID of matching contact (if found) |
Break |
Boolean | Break flag for flow control |
RecordList |
String Collection | List of matching record IDs |
Flow logic#
1. Salesforce key priority check#
The flow first determines the lookup strategy:
- If SalesforceKey is provided: Evaluates break conditions and returns the existing Salesforce Key
- If SalesforceKey is null: Proceeds to platform key lookup
2. Break evaluation#
When a Salesforce Key exists, the flow evaluates break conditions:
- If Custom_MovedataBreak is true: Sets break flag and adds record to result list
- If Custom_MovedataBreak is false: Proceeds without break handling
3. Platform key validation#
The flow checks if a platform key is available:
- If PlatformKey is provided: Proceeds to platform key lookup
- If PlatformKey is null: Flow terminates without returning a match
4. Platform key lookup#
When a platform key exists, the flow performs platform key matching:
- Uses
movedata__PlatformKeyLookupComponentApex action - Searches Contact records using the platform key lookup system
- Returns the matching Salesforce Record ID if found
Lookup strategy#
The duplicate detection follows this hierarchy:
- Direct Salesforce Key: If provided, use immediately (highest priority)
- Break evaluation: Process MoveData break functionality if applicable
- Platform key lookup: Search existing records using platform key matching
- No match: Returns null if no duplicate found
- Salesforce Duplicate Rules: MoveData will execute the Salesforce Duplicate Detection rules after the flow (if configured)
Dependencies#
movedata__PlatformKeyLookupComponent(Apex action)