Two-Way Sync

two way sync (or bidirectional sync) is when changes are mirrored between two systems traditional triggers and actions cannot accomplish two way sync because they would result in an infinite loop for example, when a new item is added in system a, automation #1 would then add the item in system b but then an automation #2 that monitors system b for new items would be triggered and the same item would be added to system a, which again triggers automation #1 b/c it is watching system a for new items the system makes it possible to build two way sync automations that avoid infinite loops each action maps data fields from the other app's trigger data transforms are commonly needed to translate values from one app to the other in cases where a list of values needs to be mapped between the apps, the transform text app's "lookup value in key value table" action can be used in the example below, mailchimp statuses of "subscribed" and "unsubscribed" are converted into "n" and "y" values needed for donorperfect's "no email" state the system's two way sync functionality does not handle the merging of conflicts if a synced record is updated at the same time in both systems when this happens, the automation will end up only making one of the changes two way sync triggers two way sync triggers must use the trigger two way sync module instead of the trigger – emit new items module this module can be used in both polling triggers and in webhook triggers be sure to set the trigger type at the top of the module appropriately the trigger two way sync module adds a node to each emitted data time named "two way sync trigger unique row id" this data node must be selected as the unique row identifier in the trigger module the trigger module will emit a field named "two way sync identifier" that must be mapped in the automation editor to the field of the same name in the action's field mappings two way sync trigger assemblies must have a name starting with “two way sync” the system currently uses the trigger name to determine which triggers are two way sync two way sync actions two way sync actions must define a field named "two way sync identifier" as their first static data field the field must be required it is best to copy its help text from another two way sync action assembly in the system two way sync actions must use the action two way sync module with nested subassemblies to perform the configured actions the "action type" selection determines what action the subassembly should perform the trigger two way sync and action two way sync modules both store item identifiers and timestamps in the system's database that are used to determine which action type needs to be performed the action two way sync modules must be chained together in this order create > update > delete