Clay Product Roundup Q1.2 | Quality of life improvements

I don't know what is up with Clay or that it's just my Wi-Fi, but it is really slow.

Again, it's not that slow.

It's probably probably their Wi-Fi.

Yeah. [laughter]

Uh my name is Luda.

My name is Aaron Rohill.

I'm Josh. I'm Nil.

Nikolai.

Jenny. I'm

Brandon.

My name is Tom.

Okay. on the cross table lookups like there it it isn't very performant. It's

like it like takes hours. No. Yeah, it

was really really slow previously. No,

that was really annoying. It's very

slow. I know, says Rachel. I agree with Rachel there. And then the user said,

Rachel there. And then the user said, "That's a product gap. That is clearly intentional to make cost control more difficult. I understand your frustration

difficult. I understand your frustration with this limitation. Would you like me to connect you with a human agent?" The

user sent borderline predatory behavior.

Well, I don't think it was intentional, but [laughter] um I can see their point.

The issue I was running into was the following. I want to get all the

following. I want to get all the contacts associated with accounts that closed during the year of 2022. Biggest

range I could feasibly get was January 1st to 8th. I was wondering if there was any way to get around this.

Please, please, please make speed, specifically client, a priority. Um, no.

There are some things that we fixed on Clay's side. We are now running actions

Clay's side. We are now running actions as fast as we possibly can. So, you

should notice a major speed up in how fast we're running actions across the board.

Not only AI [music] actions, but all real actions are are I guess a lot faster too.

Jennifer says, "Does Clay have an API that I can use?" Hey there, Jennifer.

This can all be solved with the new HTTP API as a source. um where she can basically put in any endpoints and any gets, post, whatever method she wants and basically unlocks unlimited list

building. Um she'll [music] be able to

building. Um she'll [music] be able to do this all natively within Clay now without using what did she mention? She

mentioned Zapier um confusion with endpoints that should automatically all be um supported now.

Do you have any plans to [music] introduce credit limits at a user level?

Yeah, I mean, well, now you can actually set credit limits and we have guard rails. [music]

rails. [music] And so, as a workspace admin, you can go to your workbook settings and then you can [music] set a credit limit for how

much that workbook can spend. I promise

it was not intentionally predatory.

[laughter] And hopefully this feature proves that we are indeed committed to allow you to get the most out of your clay credits and workspace.

This one just says uh and there's no name. Running into another UI issue

name. Running into another UI issue where the copy paste functionality isn't working or doesn't appear to be. Uh I

wish Clay has some kind of an undo button. I have burned credits by

button. I have burned credits by accident. We're adding um bulk copy and

accident. We're adding um bulk copy and paste which is much requested. um as

well as a undo [music] and redo functionality so that you'll pretty soon uh be able to work with all of these uh sort of great shortcuts that you're accustomed to in [music] like a

spreadsheet for example. So I appreciate that. To get data into Clay, you had to

that. To get data into Clay, you had to uh create [music] a separate report or list which involved a bunch of manual work which is especially annoying because Salesforce actually has a query language that allows you to query for

arbitrary data. there's no more limits

arbitrary data. there's no more limits on the import patterns they can use to get data into clay. Whereas before they would have to, you know, create lists or reports in Salesforce. There was like a a whole other step before they could get

the data they need to do into clay. So

it it fundamentally removes a step for folks trying to get their Salesforce data into into Clay. What if I want to offset my search results and get the next 50,000 or the next [music] 50,000 or the next 50,000 after that? And so if

you're using up to three different tables, uh now you can actually exclude the first [music] two search results, the first three search results, those sets of 50,000. If you use this in combination with like our saved searches

feature, then you're going to end up with uh the ability to create the same search using the same configuration and then exclude the past results so that you can continue offsetting and offsetting and offsetting. And since

clay tables are obviously limited to 50,000, uh if you export these as CSVs and use those three CSVs, that's 300,000 uh results that you can offset your results by, which if you're doing like a

fairly narrow search, I think that's a pretty reasonable expectation that hopefully you're not [music] dealing with more than like half a million results. Hopefully, uh you should maybe

results. Hopefully, uh you should maybe narrow your search in that case. I think

our goal is to ship a UI that works with you rather than kind of like getting in your way sometimes. I think 2026 is going to be the year of really consolidating more and more of their [music] go to market workload in clay.

The broader vision is is to be able to kind of keep track of your your whole TAM in clay. So every customer that you could possibly ever want to reach out to or communicate with and then do everything you need to do to to find the

best one for your business and and communicate with them easily.