Clay adds credit spend limits, HTTP API and SOQL sources in quality-of-life release
Clay's January 30, 2026 changelog adds credit spend limits on workbooks, credit cost warnings, HTTP API and SOQL data sources, bulk exclusions of up to 300,000 entities and spreadsheet-style table controls.
By Cora Whitley, GTM AI Analyst, Chief of StaffClay published a changelog entry on January 30, 2026 listing about a dozen improvements to its core table and search experience. The entry covers credit controls, new data sources, search tools and table interactions, with several items limited to Enterprise or Explorer plans and above. Clay's changelog index describes the same release as including 22x faster action runs and 10x faster AI processing. Several items are tied to credit visibility before and during runs.
The details
- Credit Spend Limits on workbooks are Enterprise only and pause runs when a cap is reached.
- HTTP API as a Source creates tables from any API endpoint.
- SOQL as a Source imports Salesforce records through queries and is Enterprise only.
- Bulk Exclusions remove up to 300,000 entities from searches on Explorer plans and above.
- Saved Searches store filter criteria for People, Companies and Jobs sources.
Context
Clay launched an app inside ChatGPT in December 2025 and became available as a connector in Claude on January 26, 2026, days before this release. Later in 2026 Clay added Lusha and Beauhurst data in March, launched Audiences in June and made its MCP generally available in July. In September 2026 it made Sequencer generally available.
Not disclosed
- Benchmarks behind the 22x and 10x speed figures
- Default credit limits applied to new workbooks
- Rate limits on HTTP API sources
- Vendor
Clay- Category
- Data & Enrichment
- Announcement type
- Feature update
Report an error
Vendors and readers can flag a factual error in this story, or ask for an image or logo to be removed. Email Cora, the editor, with the link. Image and logo removals happen within one business day. For factual corrections, Cora replies with next steps and a ForgeX lead approves the fix before it is published.
