Flow Commands are special behaviours that can be triggered by setting a value in an output-enabled variable with a specific name.

If you wish to end the execution of a MoveData flow and mark it as Failed, you can create an output-enabled Boolean variable named Cancel and set it to true. It is best practice to output a message to the execution log before you end the flow to help with context.

This command is most commonly used during the “Record Match” action when finding the record for the phase. A common example is enabling a developer to select a record and skip any further entries in the phase (as there can be multiple campaigns) and to ensure the “Mapping” action does not run and overwrite the values on the determined record. To see this in action, please take a look at this knowledge base article: .

If you wish to use a “Break” or “Continue” command but also want the Post-Upsert action for the phase to run, then create an output-enabled Boolean variable named PostUpsert and set it to true.

A flow context variable is a special variable that has been passed to a flow to inform the workflow of a specific context that is executing.

When the “Record Match” action is executing for a Lead, Contact or Account, MoveData will execute the Salesforce Duplicate Detection Rules. In order for this to run, an in-memory Salesforce Record needs to be created and populated; this is achieved by running the “Mapping” flows as part of the “Record Match” action.

When the mapping flows run, sometimes a developer will want to apply some additional mapping rules in their flow during the “Record Match” or duplicate check. This is often because the rules for Salesforce Duplicate Detection are quite narrow.

A common example is when performing a Salesforce Duplicate Detection on a Contact, writing a phone number to multiple phone fields (such as Phone and Mobile). This is to ensure a duplicate match if the provided phone number is in either of these fields; however, when persisting the record in Salesforce, the phone number should only be persisted to one of these fields.

There are a number of notification variables that are contextual. For example, when a donation is made, newsletter is only relevant to the donor and no other individual in the notification. When processing a notification, the IsActor variable is set to true when processing the primary contact / the contact the notification centers around.

Converts a DateTime variable into a Date variable.

Writes an entry to the Notification’s Execution Log. Please refer to -- to see how to use this component.