With our current form builder, Formassembly, we first lookup if the subscriber exists as a contact, if they don't, we then lookup if they exist as a lead. If contact exists, update the contact, else if they exist as a lead, then update that record instead. If neither exists, it only creates a lead. Can this plan function in the Summit App? Here's our flow chart for our open house form connector
5 réponses
I can vouch for flow! We have used a Record Triggered Flow whenever a summit events registration record is created and meets certain entry criteria to search for a lead and convert the lead if found. We also use the same flow to create/update opportunities for prospective students.
