OK very cool! That definitely helps out A LOT.
I do have a couple of questions for you to clear a up.
1) So if my destination App (Active Campaign) has 25 potential fields that can be posted to, do I need to run 25 separate tests to map all 25 fields properly from my initial source App (Infinity)?
2) What would happen if we received new data into both Active Campaign or Infinity, and we set them both up to post to each other when a contact attribute updates? Would they then get stuck in an infinite loop trying to post to each other the new update? Or would they recognize that an attribute is the same in each system and stop trying to post?
as an example let's say that I get facebook leads directly into Active Campaign sometimes and I get different leads into Infinity from another marketing source. When either new lead happens I would have Pabbly set up to send the contact data to the other system. What would happen if the first name changes on a contact from John to David in Infinity, but both systems are set to look for attribute updates? Infinity would try to send to Active Campaign to make the update, would Infinity now get an attribute change update from Pabbly because a field changed in Active Campaign? Hence creating an infinite loop?
