Discrepancy in Imported Results from Apify to Clay Table | Clay

Discrepancy in Imported Results from Apify to Clay Table

I'm importing an Apify actor run into a new Clay table and expect 67 results to be imported, but only 50 are. Is there a reason for this? Is there a limit based on the Apify or Clay subscription tier I'm on?

7 comments

Clay
APP
·
·
There is no subscription-based limit in Clay or Apify that would restrict your import to 50 results. The Apify integration allows importing up to 5,000 records from a single actor run, and Clay tables can hold up to 50,000 rows per table. If only 50 results are imported when you expect 67, the issue is likely related to the configuration of your import or the data available in the Apify actor run, not a plan limitation.
Source: Pull Data from Apify Actor with Apify
Matthew S.
·
·
Is there anything else about how I'm configuring the Apify import column that'd restrict the results to 50?
Clay
APP
·
·
A likely reason for importing only 50 results instead of all 67 is a filter or limit set in your Apify import configuration. For example, if you have a restriction—such as a cap on the number of results per group or a conditional formula—this can reduce the number of imported records. Double-check your import settings and any filters or conditional run formulas applied to the Apify column to ensure no limits are unintentionally set. Adjusting these should allow all 67 results to be imported if they are available in the actor run .
Sources: Apify integration | Documentation | Clay University Pull Data from Apify Actor with Apify
Matthew S.
·
·
https://app.clay.com/workspaces/282401/workbooks/wb_0sy4gerFfB4XqTS3q6m/tables/t_0syfgvxUX43pDmcMidb/views/gv_0syfgvykh98tfWJZQQp
Bo (.
·
·
There’s no limit on Apify Actor runs in Clay, so it’s likely one of two things: 1. Some of the results may be duplicates and got filtered out. 2. The Apify run may not have fully completed, so not all results were available yet. Let me know if you have more questions
Matthew S.
·
·
Thanks for the reply! Auto-dedupe is disabled for the table and I haven't run a dedupe otherwise. And on the Apify side, the run is complete; using it as a source for a brand-new table, it still only pulled in 50 rows. Could this be a bug with Clay?
Bo (.
·
·
We’re not seeing any current bugs with Apify, but let’s confirm by testing another actor. Do you have one that usually returns more than 50 results? If so, try running that and share a quick video showing both the Apify run and the Clay table, so we can see what’s coming through on each side. That’ll help us pinpoint where the issue might be. Let me know once you have that.