When running lookup multiple rows in other table there are no options to select a table. I have the other table I’m looking for in the same workbook and the API is set up in the account settings. For context, I have a list of accounts, I want 4 contacts for each, I built a find people table and want to build another find people table for accounts that don’t have at least 4 contacts using different search parameters.
The "Lookup Multiple Rows in Other Table" action requires you to specify the Table to Search as an input field. [1] When setting up this action, you'll need to provide:
Table to Search - The ID of the table to search
Target Column - The column to match against
Filter Operator - How to compare values
Row Value - The value to search for
Limit (Optional) - Maximum rows to return [2]
If you're not seeing table options, try refreshing the action setup or ensure your API key is properly configured. The table should appear in the "Table to Search" field where you can select your find people table. [3]
For your use case of finding accounts with fewer than 4 contacts, you can use this lookup to check existing contact counts before running additional searches.
Was that helpful?
This was not helpful. I’ve refreshed the page, cleared cache, ensured the API key is properly setup, I’ve even restarted my device in case there was a chrome update that was preventing this for some reason. After all of this I’m still not seeing any tables to connect to.
I'm sorry to hear you're still having trouble. I'll connect you to a human agent who can assist you further.
Clay Support is sharing a file with you.
Our support team has got your message and we'll get back to you soon!
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!
thanks, looking forward to it
Hello Andrew! Thanks for reaching out! Can you send the table link URL for me to take a look? Looks like it is an issue with your Clay API key. The easy fix is to just go to Connections > Clay > delete the api keys. Now when you setup a new lookup it will automatically create a new api key and the issue will be resolved!
thanks Sayli G. - what are the potential downstream impacts of deleting a configured Clay API key? Would I need to review if any other tables are leveraging that key to ensure I don’t break something for a colleague? Feel free to email me andrew@tmarketers.com - I’d prefer not to share a URL in this public channel.
Hello Andrew! Just emailed you! For future reference anyone who does not have access to your workspace cannot view your table!
Going to go ahead and close this out so that we can continue our conversation there!
