Skip to content

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_Recurring_Key Label: [MoveData] Donation: Recurring - Platform Key Type: Auto-Launched Flow Template API version: 60.0 Status: Active

This utility flow generates standardised platform keys for recurring donation records by combining platform identifiers. These are used to match on existing records.

Purpose#

The flow creates unique platform keys that:

  • Provide consistent identification for recurring donations across different donation platforms
  • Enable reliable recurring donation matching and deduplication

Salesforce fields#

This flow interacts with the NPSP Recurring Donation object and its related fields. Below is a mapping of all fields utilised:

Field API name Field type Purpose in flow
md_npsp_pack__Platform_Key__c Text (100) Stores unique external platform identifier

Input variables#

Variable Type Required Description
Platform String Yes Platform identifier (e.g., "gofundme", "justgiving")
Key String Yes External platform's unique identifier for the recurring donation

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#

When key validation passes, the flow generates the platform key:

  • Formula: Uses {!Platform}:{!Key} format
  • Assignment: Sets result to generated platform key value

Platform key format#

Platform:Key

Example: gofundme:recurring123

Processing summary#

  1. Key validation: Check if external platform key is provided
  2. Key generation: Create standardised platform key using format Platform:Key
  3. 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

Ask MoveData AI
Ask about setup, configuration, or troubleshooting
How can I help you with MoveData today?