Donation platform key 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_Donation_Key Label: [MoveData] Donation: Donation - Platform Key Type: Auto-Launched Flow Template API version: 60.0 Status: Active
This flow generates standardised platform keys for donation records by combining platform identifiers and external keys into a consistent format. These keys are used to match existing records and prevent duplicates in Nonprofit Cloud environments.
Purpose#
- Provide consistent keys for donations across different external platforms
- Enable reliable donation matching and deduplication during processing
- Support Nonprofit Cloud GiftTransaction objects
Salesforce fields#
This flow interacts with Nonprofit Cloud objects and their platform key fields. Below is a mapping of all fields utilised:
| Field API name | Field type | Purpose in flow |
|---|---|---|
| movedata__Platform_Key__c | Text | Stores generated platform key |
Input variables#
| Variable | Type | Required | Description |
|---|---|---|---|
Platform |
String | Yes | Platform identifier (e.g., "gofundme", "justgiving", "paypal") |
Key |
String | Yes | External platform's unique identifier for the donation |
Output variables#
| Variable | Type | Description |
|---|---|---|
Result |
String | Generated platform key in standardised format |
Flow logic#
1. Platform key generation#
The flow uses a simple but effective key generation approach:
Platform:Key
Examples:
gofundme:donation123456justgiving:78901234paypal:TXNID567890stripe:ch_1A2B3C4D5E6F
2. Key construction#
The flow performs direct string concatenation:
- Combines the platform identifier with the external key
- Uses colon (
:) as the delimiter for consistency across all MoveData flows - No validation or transformation applied to maintain simplicity and reliability
Error handling#
Input validation#
The flow relies on calling processes to ensure:
- Platform identifier is provided and not null
- External key is provided and not null
- Both values contain valid characters for platform key construction
Dependencies#
None