Contact platform key helper 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_Helper_Set_Contact_Platform_Key Label: [MoveData] Donation: Helper - Set Contact Platform Key Type: Auto-Launched Flow Template API version: 60.0 Status: Active
This helper flow manages the creation and association of platform keys for contact records, establishing the link between external platform identifiers and Salesforce contact records for integration purposes.
Purpose#
The flow provides platform key management that:
- Writes platform key records linking contacts to external platform identifiers
- Validates platform key data integrity and prevents conflicts
- Provides error handling for platform key creation failures
Salesforce fields#
This flow interacts with the Contact Platform Key custom object and its related fields. Below is a mapping of all fields utilised:
| Field API name | Field type | Purpose in flow |
|---|---|---|
| movedata__Platform_Key__c | Text | Stores external platform identifier |
Input variables#
| Variable | Type | Required | Description |
|---|---|---|---|
Record |
Contact SObject | Yes | The Contact record to associate with platform key |
Platform |
String | Yes | Platform identifier (e.g., "gofundme", "justgiving") |
PlatformKey |
String | Yes | External platform's unique identifier for the contact |
Stage |
String | Yes | Processing stage indicator ("pre" or "post") |
Output variables#
| Variable | Type | Description |
|---|---|---|
Record |
Contact SObject | Updated contact record |
Errors |
String Collection | Error messages from platform key creation |
Flow logic#
1. Platform key creation#
When validation passes, the flow creates the platform key association:
- Component: Uses
movedata__PlatformKeyCreateComponentApex action - Validation: Includes
ErrorIfDifferentObjectIdto prevent key conflicts- Ensures that the same platform key is not used on another record. This should not happen as the platform should have matched earlier.
- Association: Set the platform key, linking it to the contact record
2. Error handling#
The flow includes comprehensive error management:
- Success validation: Checks if platform key creation was successful
- Error logging: Captures error messages for troubleshooting
Error handling#
- Duplicate platform keys: When the same platform key already exists for a different contact, the flow captures the error
Dependencies#
movedata__PlatformKeyCreateComponent(Apex action)