Troubleshooting Salesforce List Sync Issues with Clay

Henry J. · 2025-11-20T19:07:56.431Z

Hi guys - my salesforce list isn't syncing properly to Clay even though the sync is hourly: https://app.clay.com/workspaces/289628/workbooks/wb_0t4v61jVjRt4nYfYVYc/all-tables Is it because it has synced >50000 rows historically (even though they auto delete) so the webhook is now dead? Is there any way around this?

Troubleshooting Salesforce List Sync Issues with Clay | Clay

Clay Support
APP
·
·
Yes, you're correct. Webhook sources are limited to 50,000 submissions, and this limit persists even after deleting rows. [1] When this limit is reached, new records cannot be added, which disrupts workflows and integrations.
To work around this, you'll need to create a new webhook to continue receiving data. Alternatively, if you're on the Enterprise Plan, you can use Passthrough Tables to bypass the standard 50,000-row limit with automatic deletion.
Before we explore other options, I'd recommend trying Sculptor (our built-in AI tool in the top-right corner) to help set up a new workflow or table configuration.
Clay Support
APP
·
·
Was that helpful?
Henry J.
·
·
So I auto-deleted the rows, but did so using auto dedupe. If i instead use auto-delete instead of auto-dedupe, does that remove the 50k limit? I thought it was just about all historical rows, whether auto-deleted or not?
Clay Support
APP
·
·
No, switching from auto-dedupe to auto-delete won't remove the 50k webhook limit. The 50,000 submission limit persists even after deleting rows, regardless of the deletion method used. [1]
Auto-delete is an Enterprise Plan feature that helps bypass standard row limits by automatically processing and forwarding data before deletion, but it doesn't reset the webhook's historical submission count. [2] You'll still need to create a new webhook to continue receiving data once the 50k limit is reached.
Clay Support
APP
·
·
Was that helpful?
Henry J.
·
·
Is there any way around the webhook limit?
Clay Support
APP
·
·
Yes, there are a few workarounds for the 50,000 webhook limit:
For Enterprise Plan users:
- Passthrough Tables bypass the standard 50,000-row limit with automatic deletion
- Bulk Enrichment processes millions of records with no row limits, automatically deleting enriched rows after export [1]
For all users:
- Create a new webhook when you hit the limit [2]
- Split data into smaller, manageable tables
I'd recommend trying Sculptor (our built-in AI tool in the top-right corner) to help set up a new workflow or explore these alternatives.
Clay Support
APP
·
·
Was that helpful?
Henry J.
·
·
Speak to a human
Clay Support
APP
·
·
I understand your need to speak with a human, so I’m routing you to our team now for further assistance.
Clay Support
APP
·
·
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!
image.png(93 kB)
Ariana (.
·
·
Hi Henry, thanks for reaching out! The 50K limit doesn't appear to be coming into play here - there is still plenty of room for more rows. It looks like we are successfully querying the Salesforce list but not receiving any data. How many rows are in the list on the Salesforce side? Can you give us a couple examples of rows that are on the Salesforce list but are not in Clay?
Henry J.
·
·
Thanks, Ariana - and just to check - I now have auto-delete on, but it is still counting the number of rows. That makes me think that when I hit 50k, the webhook will stop working. Is that right?
Loading attachments
Ariana (.
·
·
Hi! Your workspace has pass-through tables enabled, meaning your source table acts as a pass-through conduit rather than storing the data. You have auto-delete on, so the rows will be updated and deleted once you reach 50k. Does that help?
Henry J.
·
·
Thank you! And so that means I can keep going past 50K rows so long as I use auto delete rather than auto dedupe?

16 comments