Check for a Matching Contact in Your Org

Find a Matching Contact With a Get Records Element

In your flow, add a Get Records element that queries your org for any existing contact whose email matches the email that the user entered.

1. After the Contact Info element, click .
   
2. Select Get Records.
   
3. In the Get Records configuration panel, enter these values.
   
   • For Label, enter Find a Match.
     The API Name is automatically set to Find_a_Match.
     
   • For Object, select Contact.
     
4. In the Filter Contact Records section, for Condition Requirements, verify that All Conditions Are Met (AND) is selected.
   
5. Enter this condition.
   
   • For Field, select Email.
     
   • For Operator, select Equals.
     
   • For Value, select contact > Email.
     
6. Leave the other fields set to their default values.
   

Your flow canvas should look like this.

7. Click Save.
   

Determine If a Matching Contact Was Found

Next, the flow must check to see if the Get Records element found an existing contact with the same email. Depending on the result, the flow needs to take different actions, so add a Decision element to create multiple paths that the flow can take.

1. After the Find a Match element, click .
   
2. Select Decision.
   
3. In the Decision configuration panel, enter these values.
   
   • For Label, enter Match Found?
     The API Name is automatically set to Match_Found.
     
4. In the Outcome Order section, make sure that New Outcome is selected, and enter these values into the Outcome Details section.
   
   • For Outcome Label, enter Found.
     The API Name is automatically set to Found.
     
   • For Condition Requirements to Execute Outcome, make sure All Conditions Are Met (AND) is selected.
     
   • Enter this condition requirement.
     
     • For Resource, select Contact from Find a Match > Entire Resource.
       
     • For Operator, select Is Blank.
       
     • For Value, select False.
       
       
5. In the Outcome Order section, select Default Outcome.
   
   • For Label, enter Not Found.
     
6. Save the flow.
   

On the flow canvas, the Decision element now has two paths coming from it, one to run when a matching contact is found, and one to run when no matching contact is found.

However, if a matching contact is found, the flow must confirm what the user wants to do. In the next unit, you create another screen and another decision to confirm what happens next.