Urgent Help Needed: Fixing Issues in Two Tables | Clay

Urgent Help Needed: Fixing Issues in Two Tables

I need help with two tables. I've set them up with the entire tables, but I'm unable to identify and fix the issues. I'm not sure if the issues are with the prompts or what. Need immediate assistance.

15 comments

Channeled
APP
·
·
To identify and fix issues with your tables in Clay, try these steps: 1. For list-related errors: If you're trying to write lists to tables, ensure the data is formatted correctly. Add the list through the "Other data from this table" section. 2. For display issues: If you see empty rows after filtering, it might be a front-end performance issue. Try clearing your cache and refreshing your screen. 3. For prompt-related problems: Use the AI prompt help tool by clicking "Help me" when configuring the "Use AI" enrichment. This will help you generate a tailored prompt for your desired outcome. 4. For general performance issues: Perform a hard refresh (Cmd + Shift + R on Mac, Ctrl + F5 on Windows) to resolve latency or loading problems. 5. For data accuracy: Verify your input data format, double-check prompts and search parameters, and consider using our metaprompters to craft better prompts. If issues persist, you may need to request human assistance for more specific troubleshooting.
Source: Writing AI prompts in Clay | Documentation | Clay University
Noor E.
·
·
Table 1: LI HIRING v1
Apollo isn’t finding contacts in the following three columns:
Find_managers
Find_founder
Find_talent
FYI: The Select_founder column isn’t pulling any leads, which is not a problem. My niche is accounting firms under 1000 employees, and most firms are run by partners, not a single owner
The export columns below are not all pulling into lemlist. (I previously deleted the contacts from lemlist as I initially had some errors, so I want to rerun these columns and move the contacts to lemlist now.)
Export_lemlist_manager
Export_lemlist_talent
Export_lemlist_founder
What is the “Lookup Lead In Campaign” column on the far right? I’m not sure what it’s for. Perhaps Reyhan helped me add it? I’m not sure if it should be exporting data or how it’s intended for use.
Please review the full table and confirm full optimization.
Table 2: TALENT REPLACEMENT
The find_manager column is pulling in thousands of leads. Something is wrong.
This impacts everything else that’s dependent on this column. Please fix the error and review all table functionality for optimizations so that I might successfully add all leads to my campaign in Lemlist and launch.
Channeled
APP
·
·
I understand you're having issues with your Clay tables. Let's address them one by one: 1. Apollo contact-finding issues: • Ensure your company domains or LinkedIn URLs are correctly formatted in the table. • Double-check your search parameters for each column (Find_managers, Find_founder, Find_talent). 2. Lemlist export problems: • Use the "write to table" feature to export data to Lemlist. • Verify that your Clay API key is correctly linked in Settings > Connections > Clay. 3. "Lookup Lead In Campaign" column: • This might be a custom column. Review its configuration or remove if unnecessary. 4. TALENT REPLACEMENT table issues: • Check the find_manager column's search parameters. They might be too broad, causing excessive results. To optimize both tables: 1. Review and refine your search parameters for each column. 2. Clear your cache and perform a hard refresh (Cmd + Shift + R on Mac, Ctrl + F5 on Windows) to resolve any display issues. 3. Use the "Preview People" option before importing to ensure accurate results. If problems persist, you may need to request human assistance for more specific troubleshooting.
Noor E.
·
·
Can I please get some help here?
Noor E.
·
·
??
Bo (.
·
·
Hey, For Table 1 (LI HIRING v1): Most rows are successfully pulling contacts, but it's normal if some don't return results—especially in niche cases like accounting firms without clear founders. The Select_founder column is working as expected given your audience. Regarding Export_lemlist columns: it looks like the contacts have already been added to campaigns, which is why re-running them might show no new results. P.S. A better hygiene of table here would be to send those values to a new table to have them in their own rows, preventing any kind of issues with troubleshooting down the road! The Lookup Lead in Campaign column is used to check if a contact already exists in your Lemlist campaign—helpful for avoiding duplicates or tracking export issues. For Table 2 (TALENT REPLACEMENT): It's showing a similar number of leads to Table 1. If it's pulling too many results unexpectedly, there may be a filter or input that needs adjusting. Feel free to send over a Loom video so we can take a closer look and optimize the setup. Let me know which rows or columns you want us to review in more detail.
Noor E.
·
·
I need help with rectifying both tables asap. please
Bo (.
·
·
Hey — happy to help. Can you let me know what specific issues you’re running into?
Noor E.
·
·
Both tables, aren't working properly
Noor E.
·
·
can you help me with the prompts to ensure that they're working properly
Noor E.
·
·
I need this done today
LuisArturo
·
·
Hey there sorry for the delay here, can you clarify which prompts inside of the tables are not working correctly I see that they both contain a number of AI columns so not sure which ones are the ones that need editing.
Noor E.
·
·
For first table, previously the leads were correcting moving into Lemlist. Now they're not moving for some reason.
Noor E.
·
·
For Second table, ‘format_location” column is eliminating many leads.
LuisArturo
·
·
Hey there sorry for the delay here, to clarify what is going on in the first table, the reason these leads are not being added is because they already exist inside of the Lemlist campaign and so will not be added a second time or because the run condition was not met for the integration to run for a row.
(63 kB)
As for the second table, to clarify when you say that it is eliminating many leads, are you referring to the rows where the integration has not run at all here. If yes, then this is also due to the fact that the conditional formula used to see whether or not a row will run was not met.
(58 kB)