Devin M.

Here’s a good example: I ran a google review scrape at a company level using apify that dumps into a google sheet. I did this because every time I try to pull the results in from apify directly the output gets truncated to 20 reviews only when i need to run analysis on a bigger sample set, and it also only pulls in the most recent apify pull instead of appending the table with new content. So the google sheet has a ton of great data in it. Right now I have to have it wired up through a webhook to dump into clay. it seems super unnecessary when a google sheet could just be the source. Let me ask what the reasoning is for not allowing a google sheet as a source?

https://app.clay.com/workspaces/285869/workbooks/wb_0szgf7lseifFhhDhHag/tables/t_0szi28qmrpfUJv9mEEV/views/gv_0szi28q34s4ed9iirAD Primary Specialty Column. I’ve been running this column with 4o mini for months without issue. Today it’s timing out or erroring a ton.

How about google sheet as a source! Seems like a no brainer! Andreas just watched some of your vids on the topic

The use case would be to make it easier to run a claygent on the list of urls from one column and also make it easier to push back to our crm

Sweet. Will try this.

My workaround so far has been to have a working table, and then write to another table for the major outputs of the enrichment…it could be solved with just more columns in one table.

Think about all the opps for custom messaging just from running a domain waterfall, email waterfall, then the linkedin waterfall. Then enrich from profile. You could have a ton of columns with useful enriched data right there to customize messaging with.

Two things I see right off the top.