Yes, importing records from a Salesforce list does use Salesforce API calls. When you import data from Salesforce into Clay, we make API calls to pull the data from your Salesforce instance.
There's a 2,000 record limit when importing from Salesforce reports due to Salesforce API restrictions, but importing from lists allows for more comprehensive data pulls.
If you need any more help understanding how Salesforce API calls work with Clay, I'm here to assist. Would you like to provide more details about what you're trying to achieve with the integration?
No, Salesforce imports don't stop at 50,000 records. The 50,000 limit applies specifically to webhook tables, not Salesforce imports.
For Salesforce SOQL queries, Clay imports the first 50,000 records and stops - you'd need to split larger datasets using date ranges or filters. Regular Salesforce list imports can handle more comprehensive data pulls without this restriction.
If you still need help with Salesforce imports or have more questions about API usage in Clay, I'm here to assist. Would you like to share more about what you're trying to resolve or understand?
No, a live Salesforce list sending updates to Clay wouldn't count as a webhook. When you import from Salesforce lists, that uses our Salesforce integration, not the webhook functionality.
The 50,000 limit only applies to webhook tables - those are when you use Clay's webhook URL to receive data from external applications via HTTP POST requests. Your Salesforce list integration is a different type of connection that doesn't have that same restriction.
That sounds like you hit Clay's general table limit, not a Salesforce-specific restriction. All Clay tables are capped at 50,000 rows total - this includes all rows whether visible, hidden, or deleted.
When you reach this limit, the table stops accepting new rows and some functionality stops working. This is different from the Salesforce SOQL query limit of 50,000 records, which only applies to specific query types.
For ongoing Salesforce imports that might exceed 50k rows, you'd need to either split your data across multiple tables or use Enterprise features like Passthrough Tables if available.
Auto-delete can help bypass the 50,000 row limit, but it's only available on the Enterprise Plan. It automatically processes incoming data, enriches it, forwards it to a destination, then deletes the original entries to keep your table manageable.
However, regular row deletion doesn't remove the limit - the 50,000 count includes all rows whether visible, hidden, or deleted. Only the Enterprise auto-delete feature actually bypasses this restriction by handling data on a rolling basis.
