Hey @ross.hopkins,
It’s been a while so you may have already got this figured out but I thought I’d jump in here just in case!
It looks like only a few options are being shown in the dropdown menu. If you click the Show all options link on the dropdown menu it should reveal more options, including the _zap_search_was_found_status field:
It’s the _zap_search_was_found_status field that you’ll want the Filter to check as that will give either a true or false value which will indicate whether an existing record was found or not. :)
Hi @ross.hopkins
Something to consider…
If you have a lot of records that would be “updated”, then by using the Filter step, you’d actually be using more Tasks in your Zap vs just having the Zap find/create + update.
Thanks Sam - I did eventually find the Zapier variable (and felt a bit silly for missing it! 
).
And thanks, Troy. I did consider that seeing as the field mapping isn’t shared that there isn’t that much to be gained from having the one Zap vs two, other than being able to view a whole process. It is very rare we’d update a Lead though so think I’m ok on the volume front.
The only issue I’ve really run into is Salesforce’s fuzzy matching to stop duplicate Leads after the “Find and Create” Action didn’t find a record; I wish there was a graceful way to handle that occurrence.
@SamB @Troy Tessalone
I have this same need, and I’m looking to save my customers from having to map the same 40 fields twice in the zap. Will it work if I have the “Find and Create” action just create the record with the bare minimum fields, and then have the Update event update all the fields?
@jeffernst
Yes, that’s an approach to take, but depends on the logic you are trying to implement.
For example, should a record be updated if it already exists?
- Find/Create Record
- Update Record
