Hey - Thanks for this! We're always looking to make the product better and thisfeedbackis super helpful for us. We're going to pass this over to our product team so they can better evaluate things and see if/where this might fit into the roadmap as a future improvement.
If the tables are still in the trash, you can restore them from there. If they’re not showing up in the trash anymore, we’re unfortunately not able to recover them on our end.
Updating a saved search won’t change the behavior of an existing company search source. Once a source is added to a table, it’s locked to the search parameters it was created with.
If you want to change how the search works, you’ll need to remove that source and add a new one with the updated search. There isn’t a way to repoint or refresh an existing source to a different saved search.
CSV imports don't count toward the 20-source limit and there's no cap on how many CSVs you can import into a table. You can import them sequentially into the same table without hitting any restrictions.
For your other questions:
Deleting CSV sources: CSVs aren't logged as sources in the workbook, so there's no source entry to delete. The rows themselves remain in the table after import. So it would be a delete row action.
Deleting company search sources: When you delete a source, the rows that were added from it stay in the table. Sources in Clay don't have a delete option that removes the associated data. However, if those rows have lookups that reference values from the deleted source and you re-run them, the lookups won't pull that data again since the reference is gone.
Just flagging that this is pending a bug. In the meantime, we can work around it by manually filling in the missing values.
Do you know the table ID for these? You can grab it from the URL. In the address bar, you’ll see /table/TABLE_ID_HERE. Copy that value and add it manually.
The table ID here is t_0t5ytrzg9TRo4NurTiS. You can then edit the company table column and replace the value with this ID.
If you have many tables or multiple results, you can filter the table by the source input, add a text column, and manually input the value there. From there, use Merge Columns to combine everything and keep the build working.
We’re aware of the issue and actively working on a fix.
That error is happening because the column doesn’t have an output format defined.
Open the column settings, add an Output format that matches what you expect the model to return, then re-run the column. Once the output schema is set, the parsing error should go away and you won’t need to repeat things twice.
Can you try creating a brand-new Find People (Apollo) column and running it on a few rows? It looks like this might be tied to the existing column setup or a template issue.
Thanks for the patience here. We don’t have an update yet, unfortunately. The team is still looking into it, and I’ll follow up as soon as we have more clarity.
Sorry for the delay, I know this is blocking. Let me know if you have more questions.
