Salesforce Lookup Record Function Field Disappears Before Entry

Jon Y. · 2026-02-03T03:29:45.496Z

The Salesforce Lookup Record function is buggy. The field for selecting the clay column to match to the Salesforce object type keeps disappearing on me before I can enter the column.

Salesforce Lookup Record Function Field Disappears Before Entry | Clay

Clay Support
APP
·
·
This sounds like a UI bug with the Salesforce Lookup Record function. The field mapping interface should stay stable while you're configuring your lookup parameters. [1]
For the Salesforce Lookup Record action, you need to specify the object field you want to search within, then enter the value to search for - but the interface shouldn't be disappearing on you. [2]
Try refreshing your browser or clearing your cache first. If that doesn't work, you might want to click into the specific cell where you're seeing this issue to check if there are any error details that could help troubleshoot further.
Are you seeing any error messages when the field disappears, or does it just vanish without any indication of what's wrong?
Clay Support
APP
·
·
If you still need help with the Salesforce Lookup Record function issue, I’m here to assist. Would you like to provide more details about what you’re trying to resolve or any error messages you’ve encountered?
Jon Y.
·
·
It just vanishes without any indication of what's wrong.
Clay Support
APP
·
·
That's definitely frustrating when the UI just disappears without any feedback. This sounds like a browser or interface issue rather than a configuration problem.
Try these steps:
Use a different browser or incognito mode
Disable browser extensions temporarily
Check if you have sufficient permissions for the Salesforce object and fields you're trying to map
Since this is a UI bug that's preventing you from setting up your lookup properly, I'd recommend trying our built-in AI tool Sculptor first - it's in the top-right corner and can help build tables and set up automations. Give that a shot and let me know if it helps resolve the field mapping issue.
If Sculptor doesn't solve it, this might need human troubleshooting since the interface shouldn't be vanishing like that. [1] [2]
Clay Support
APP
·
·
Did that answer your question?
Clay Support
APP
·
·
If you still need help with the Salesforce Lookup Record function issue, I’m sorry for the trouble this has caused. Would you like to share more details about what you’re trying to achieve or any other difficulties you’re facing?
Jon Y.
·
·
I think I need a technical support human to look into this. I cannot get it to work at all
Clay Support
APP
·
·
Got it — I’m connecting you to a human teammate now.
Clay Support
APP
·
·
Our support team has got your message and we'll get back to you soon! We're currently outside of our standard office hours (9 AM to 9 PM EST, Monday through Friday), so it may take a little longer for us to respond.

If you’re dealing with a specific table, drop the URL below so we can help you quicker. Otherwise, someone from our team will be in touch soon!

image.png(93 kB)
Jon Y.
·
·
https://app.clay.com/workspaces/572542/workbooks/wb_0t8eqlhgTuDEYwU4vtm/tables/t_0t8eqlv4H2G48qcdHa3/views/gv_0t8eqlv4A7pTzW4BrH4
Mayato (.
·
·
Hi Jon, thank you for reaching out, and sorry for the trouble. When I tested the Salesforce lookup record action, the Object Fields loaded instantly. It’s possible there was a temporary backend API issue at the time you tried. Could you please check again and let me know if it’s working now? Thank you.
Jon Y.
·
·
Good morning Mayato (., After many attempts last night I managed to get the Object Fields to stay but I still received an "Inputs missing" error in the row. This morning I tried again. Same thing, the "Object Fields" field continues to disappear on me. I recorded a Loom video to show exactly what is happening. https://www.loom.com/share/fccf4d84746347089d831ae03a0e0ed0
Michael A.
·
·
Hi Jon - thanks for reaching out! This is interesting as I can't repro it on my end. It populates immediately as well. Can you try clearing your cache or if it works on a different browser? Additionally, you can also try switching keys as our input parameter populate based off of api keys.
Jon Y.
·
·
Michael A. I actually JUST tried clearing my browser cache for another reason and thought I would test it again, only to find out it still does the same thing.
Jon Y.
·
·
I have asked my Salesforce Admin to reestablish the Salesforce API/connection. I'll report back after that is done.

28 comments