Guidance Needed for Setting Upsert Key in Email Match Operation

Justin T. · 2025-02-23T00:21:08.291Z

Hi, Im confused on where to set the Upsert key on this operation. Im trying to use email to match it. No options seem to come up for me.

Guidance Needed for Setting Upsert Key in Email Match Operation | Clay

11 comments

· Sorted by Oldest

Justin T.
·
·
Following up here. Thanks 🙏
Channeled
APP
·
·
For the Salesloft Upsert Person operation, you don't need to explicitly set an upsert key - the integration automatically uses the email address (Primary Email Address field) as the matching key. When you provide an email address, the system will automatically search for a person in Salesloft using that email. If a match is found, it will update the existing record; if no match exists, it will create a new person record.
Sources: Upsert Person with Salesloft Snowflake integration overview | Documentation | Clay University
Channeled
APP
·
·
Was that helpful?
Channeled
APP
·
·
Hi Justin T.! This thread was recently closed by our Support team. If you have a moment, please share your feedback:
Osman S.
·
·
Hey Justin T.! You need to have an external ID set on the object for upserts to work
❤️1
Mark L.
·
·
Hey Justin, did you get what you need here? Echoing Osman, to use the Upsert Object action, the Salesforce object will need to have a field designated as an "External ID" within Salesforce. An example of what that would look like for a Salesforce admin:
(127 kB)
Does your Lead object in Salesforce have any fields with that "External ID" checkbox checked?
Justin T.
·
·
Ohh. I didn’t realize it wasn’t like that by default. I only checked the field level indexing. Thank you!
Justin T.
·
·
Actually, Lead.Email should be a default external ID. There’s no option to mark it external
Mark L.
·
·
Ah, right, the default email field (for example) wasn't designed by Salesforce for the purpose (e.g. not indexed the same way, not guaranteed unique, etc.). You'll need to use an existing field that's designated as an External ID, or create a new one marked as such.
Justin T.
·
·
Still hitting the same issue. I created a custom field Contact.Email2__c and ported the data from Contact.Email over. Clay found it and it's set up in the setting but still failing.
Mark L.
·
·
This table, right? https://app.clay.com/workspaces/460716/workbooks/wb_FKteE6KFJPNX/tables/t_PsJcKVsC5R2D/views/gv_AipfRKNS8ogp Be sure to supply a value for the designated lookup field – you'll need to scroll down a bit to find it.
(178 kB)
Could you try updating that, and let me know how it goes?

Justin T.
·
·
Following up here. Thanks 🙏
Channeled
APP
·
·
For the Salesloft Upsert Person operation, you don't need to explicitly set an upsert key - the integration automatically uses the email address (Primary Email Address field) as the matching key. When you provide an email address, the system will automatically search for a person in Salesloft using that email. If a match is found, it will update the existing record; if no match exists, it will create a new person record.
Sources: Upsert Person with Salesloft Snowflake integration overview | Documentation | Clay University
Channeled
APP
·
·
Was that helpful?
Channeled
APP
·
·
Hi Justin T.! This thread was recently closed by our Support team. If you have a moment, please share your feedback:
Osman S.
·
·
Hey Justin T.! You need to have an external ID set on the object for upserts to work
❤️1
Mark L.
·
·
Hey Justin, did you get what you need here? Echoing Osman, to use the Upsert Object action, the Salesforce object will need to have a field designated as an "External ID" within Salesforce. An example of what that would look like for a Salesforce admin:
(127 kB)
Does your Lead object in Salesforce have any fields with that "External ID" checkbox checked?
Justin T.
·
·
Ohh. I didn’t realize it wasn’t like that by default. I only checked the field level indexing. Thank you!
Justin T.
·
·
Actually, Lead.Email should be a default external ID. There’s no option to mark it external
Mark L.
·
·
Ah, right, the default email field (for example) wasn't designed by Salesforce for the purpose (e.g. not indexed the same way, not guaranteed unique, etc.). You'll need to use an existing field that's designated as an External ID, or create a new one marked as such.
Justin T.
·
·
Still hitting the same issue. I created a custom field Contact.Email2__c and ported the data from Contact.Email over. Clay found it and it's set up in the setting but still failing.
Mark L.
·
·
This table, right? https://app.clay.com/workspaces/460716/workbooks/wb_FKteE6KFJPNX/tables/t_PsJcKVsC5R2D/views/gv_AipfRKNS8ogp Be sure to supply a value for the designated lookup field – you'll need to scroll down a bit to find it.
(178 kB)
Could you try updating that, and let me know how it goes?