Campaign 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_Campaign_Key Label: [MoveData] General: Campaign - Platform Key Type: Auto-Launched Flow Template API version: 60.0 Status: Active
This utility flow generates standardised platform keys for campaign records by combining platform identifiers and keys into a consistent format for tracking and integration purposes. These are used to match on existing records.
Purpose#
The flow creates unique platform keys that:
- Provide consistent identification for campaigns across different platforms
- Enable reliable campaign matching and deduplication
- Support integration with external fundraising and commerce platforms
Salesforce fields#
This flow interacts with the Salesforce Campaign 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 unique external platform identifier |
Input variables#
| Variable | Type | Required | Description |
|---|---|---|---|
Platform |
String | Yes | Platform identifier (e.g., "eventbrite", "gofundme") |
Key |
String | Yes | External platform's unique identifier for the campaign |
Type |
String | No | Campaign type or category from the external platform |
Output variables#
| Variable | Type | Description |
|---|---|---|
Result |
String | Generated platform key in the appropriate format |
Flow logic#
1. Key validation#
The flow first validates that a key is provided:
- If Key is present: Proceeds to generate platform key using standard format
- If Key is null: Flow terminates without generating a key
2. Platform key generation#
The flow uses the following key format:
Standard platform key format#
Platform:Key
Example: eventbrite:123456789
The key is generated using a simple formula that concatenates the platform identifier with the key, separated by a colon.
Processing summary#
- Key validation: Check if external platform key is provided
- Key generation: Create standardised platform key using format
Platform:Key - Result assignment: Set generated key as the output result
Configuration options#
The flow uses a simple, standardised approach with no configuration options, ensuring consistency across all platform integrations.
Error handling#
- Gracefully handles null Key values by not generating a platform key
- Uses simple string concatenation for reliable key generation
- No complex error scenarios due to straightforward processing logic
Dependencies#
None