B (3:52)

So if I was in your CRM, my name, Andrew Warner might be Andrew Mason, and then a phone number might be changed to 310-555-1212. And. And now you're not leaking my information out.

A (4:02)

Exactly.

B (4:03)

Okay. All right. And so now it is connected to your Slack, and while it's doing this and it's doing all this research, what's the difference between this and MCP that you did before that also connected all the tools?

A (4:17)

So MCP is a powerful tool, and soon MCP will actually be the SDK under the hood. But what the SDK can do, especially when you're using an agent harness, is it can run arbitrary API requests. So whereas the MCP has all the zapier trigger in action library predefined out of the box, the SDK can say, hey, I have access to Slack's API docs. I can just go do anything I want that the Slack API allows me to do, which means it's much more flexible for a wide variety of of workflows. And here you can see it's. It's come back and shared a sanitized view of the last 10 things that have sort of popped up in Slack for me. Teammates said they need to miss a recorded meeting because they have a conflict Comms PR flagged a sensitive AI jobs question that Wade should probably look at or avoid saying. You can see here, this is a simple thing that you can do, which is, you know, Fetch the last 10 mentions of my name in Slack. But you can also build more complex workflows. So, for example, one of the things I wanted to start doing was build a better relationship with our enterprise customers. Now at zapier, we have HubSpot, which is a CRM everybody on the team uses. But HubSpot is a very complex piece of software. I only wanted to do a very small thing, which was every Sunday I wanted to go email 10 enterprise customers and just check in, see how things were going, did they have any feedback for us, how could we make the product better, etc. And logging into HubSpot felt like overkill. Plus, HubSpot isn't the only thing that has interesting information about our customers. We also have information in Databricks, which is our data warehouse. We have interesting information in Gong, which is the tool that records all of our meetings with our customers from our AES and our CSMs. And so I wanted to build a simple CRM that pulled all those data together into one UI and then helped me go generate emails for those customers. So let me show it off real quick. Let's say, you know, please open the CEO CRM. So here you go. This is my personal CEO CRM. And you know, it gives me a couple of quick highlights. At the top, the number of enterprise accounts we have, how much they're paying us. It buckets a number of accounts that need attention for whatever reason. It tells me how many accounts have a champion in them and how many of them have like a real strong power user associated with them. But then it basically just lists out all these accounts and, you know, I can pop into it and I have like a quick little panel that shows some more detail about the account. I wired up keyboard shortcuts so I can like quickly toggle through all of them and, you know, see all of these accounts, which is nice. But the main workflow that I cared a lot about was this outreach one. You know, in here it's got 10 recommended accounts for me to go reach out to and, you know, connect with for whatever reason. So this is pretty handy. But, you know, once I sort of had identified these accounts, I thought to myself, well, it's, it's nice that I've identified the account. I'd really just like some help, you know, coming up with what I should email these, these accounts. And so that's where I started to say, you know, hey, can you help me generate a Sunday outreach email to the 10 outreach accounts? Draft them in Gmail for me, please. So now it just goes and does this for me. It's incredible. Like sort of has all these accounts pulled in from HubSpot, from Databricks, this context from Gong. So it has all this information about what makes these accounts interesting or not interesting. It knows why certain accounts need attention or not. It's suggesting 10 that would be useful for me to go ping and then it just says, all right, I'll go draft an email for me. Now I like having it draft an email still rather than just send the email because I still want to have myself in the loop. I still think that I write better emails than, than these tools do, but it usually does a good enough draft that I can just tweak a few things and be like, great, you know, send it for me. And so this system, this would have been, would not have been possible or easy for me without the zapier SDK because the SDK is able to sort of pull in safely all the data from all these systems and take action in all these systems on behalf of myself.

B (9:24)

And the reason it do it's doing that is it's pulling it from all these different locations and from your CRM, which is pulling, pulling data in from HubSpot. And it knows to then start drafting these messages out on your behalf.

A (9:36)

Yeah, and you can see here, right here, while on the screen I found an existing prospector workflow. So Prospector is the name of this workflow. Now it's got the CRM short list, it's got recent touch suppression. So it's basically saying, hey, here's some accounts you should not email. I added Clay verification over time and this was because our HubSpot didn't always have up to date contact information. And so I use Clay to basically check, hey, does this person still work at this company? Is this person like the right person in the account to reach out to? So I added that it has actually let me scroll back up so I don't lose that.

B (10:12)

By the way, that Clay part is just brilliant. You told me about this before we got started. Essentially you said, look, I could message some people, but I realized sometimes their emails are out of date, sometimes they're no longer at the company. Well, what do people do about that? They use Clay. Well, if they use clay, then frigging A, I'm just gonna connect Clay in here. And now I could use clay through this agent.

A (10:32)

Totally. You can see I've built in a Wade style draft generation. So this is another thing where I mentioned these things don't write emails as good as I do. So I basically fed it a bunch of emails that I've written before and said, here's how I like to write emails. And so it said, and then I built a Skill that's like, hey, here's how Wade likes to write emails. I taught it how I like. And then it. Then it goes and builds like a signed Gmail draft. So it like adds in a. My. My Gmail signature in a very specific way that I want for these, you know, outreach emails.

B (11:00)

Yeah.

A (11:01)

So, you know, every step of the way, I'm basically able to give instructions to this, like I would to another human, where I'd say, like, hey, can you make it like this? Can you do it like that so I don't have to know all the underlying technology that's going on. I don't know how it's doing all this stuff. I just know that I've got an amazing coding agent in cursor, inside of cursor. And in this case, I'm using GPT 5.4. And then I've got the Zapier SDK, which allows me to hook into all these different tools and pulls data in and manipulate it in interesting ways. But I don't have to figure out how to, like, actually solve these problems. And as a result, I find myself every single day, first thing in the morning, I just talk to the agent and I say, like, hey, what work have I done recently where I should build new workflows and build new agents and build new stuff? And it will start proposing them to me and says, here's the next thing you should build. Here's the next thing you should build. Here's the next thing you should build. And as a result, I've started to build up more and more of these workflows that just run for me. And more and more of my day is getting automated end to end, which is pretty freaking awesome.

B (12:11)

Give me a few more use cases. This is number one for me because this is real relationships with real customers. You keep connecting with them, it's going to build your relationship, build your revenue, and also help you understand what they want so you can create better products for them. And how about a basic one like Daily briefs?

A (12:28)

Yeah. I do a daily brief every morning. So every morning at 6am it kicks off, it goes and checks my calendar, it checks my to do list, it checks my email. And based on all that stuff, it says, here's the important things you need to do for your day. You know, here's the, you know, you've got a big focus block in the morning. In the morning, make sure you spend time doing this. This is the one thing you have to get done. If you do this thing, you. You win the day, then you know, here's these three meetings that you have in the afternoon and here's a prep specific for that meeting. So you have each meeting a Google Doc that gets generated that says what I need to know for that meeting, which is fantastic. So that I do every single morning. Another simple one. A lot of times those meetings have pre read docs, so they've got a big Google Doc. Those I just fire into the system and say I have an exec review skill and I run that against the Google Doc and the SDK goes and fetches all the information. Sometimes it's multiple docs fetches it and then it reviews it for me and says here's what you need to know going into the meeting. Here's the questions you need to ask, here's the things you need to know about. Here's a fourth one. I review every single job offer that goes out inside of Zapier still. I used to go manually review, you know, dozens of scorecards for each applicant. I would go review their resume, I'd go look at their LinkedIn. I would make sure that we were running a really tough, rigorous review cycle. Now I just point it to the Ashby, the Ashby profile. So Ashby is our tool that we use to run interviews and keep track of applicants. So when an offer comes my way, I point it at that URL, the agent, the SDK goes and fetches the application and it fetches all the scorecards on the candidate. And then it fires off an advisory council. The advisory council and analyzes, it generates multiple Personas. So like a ruthless cfo, a wartime COO operator, a contrarian board member, a recruiting expert. Like it creates all these sub profiles and then each of those sub agents goes and reviews the candidate and says, yes, you should hire this person or no, you shouldn't hire this person. Is this person a bar raiser? And it allows me to audit our own hiring process to say, hey, are we actually doing a good job here or not? And that was a task that used to take me, you know, 30 minutes per every candidate and now it's down to like five. And that's the power of these tools is if you start to stack them, you know, all the, all of a sudden like, you know, this 30 minute task here, this 30 minute task there, they all get shrunk down to five minute tasks, two minute tasks, and then you find yourself with big new blocks of time during the day and you start to go, well, what else should I work on? You know, I can, I can run this. Maybe I should launch a New podcast. Maybe I should spend more time on social. Maybe I have a new idea for this product. And so I find myself actually doing way more work than I ever did before because I have tools like this. But it's fun. Like the more work is not actually like from a time sitting in front of keyboard thing. It's not actually that I'm spending that much more time in front of the keyboard. It's just my throughput. My velocity is just so much higher. And it's fun because I'm just not sitting around waiting for this stuff to get done. It just does the work for me. It's great.

B (15:53)

All right, let's talk about some of the things that I'm going to be able to do with this because I'm going to be using this now that it's out. The number one thing that comes to my mind is I do need a daily brief and it should pull in. Since I'm posting on YouTube and I want more views, I want to understand what's hot on YouTube right now. I have access to YouTube through an API. Basically what I want is for it to start analyzing it as part of my daily brief. I have somebody on our team who just feeds me articles that he finds that he thinks that are going to be helpful for me. I'll add that into the daily brief and pull it out of Slack into there. I like to know how we're doing with Mercury. I'm assuming I could attach my Mercury bank information in to know what our burn is.

A (16:32)

If Zapier supports the app, you can hook it up and then the agent has access to the API. And so anything you can do in the API, Zapier will help you tackle it.

B (16:43)

Okay. And then if Lauren in our Slack is saying, andrew, this is an urgent thing to look at today because it has access to my Slack and it'll have access to my calendar. It could just put it on my calendar to free time based on my requests.

A (16:56)

100%.

B (16:57)

Okay. I see all the different things that I can do with this. Your CRM is my favorite so far. What I'm wondering is how did you find these things that you're doing on a repeated basis to turn into automations? How is it identifying what those are?

A (17:11)

So here was what hooked me. I made a concentrated effort to say I am going to do all of my work inside of Cursor and just said this is where I'm going to do all my work. And even at first when it was maybe a little slower because I wasn't quite Used to the workflow, yet I still forced myself to do it that way. Okay. Then every week I would just ask it, hey, look over everything we did together this week and give me ideas for new tools, new automations that we should go build that would make my work much more, like, faster, higher quality, better, etc. And it would propose three or four or five things. And of the, you know, five things it would propose, I'd be like, great, let's go build three. And we would just, we just do that process over and over and over again and it just starts to compound. And plus, once you start, once you start automating a few things, you find that your own brain starts to get better at spotting opportunities because you're like, oh, I remember this other thing I did that was kind of like this. I can probably do this in the same way or a same version of it. And so it's like a habit. Like, the more you do it, the better you get over time.

B (18:28)

How are you saving it? Are you asking whatever AI tool you're using to save in an MD file what you just did so you can analyze it at the end of the week?

A (18:37)

Yeah, so mostly. So there's two things I do. One, you can just ask the agent to review all of your chats so you don't have to save it. You can just say, look at all the chats that I've had.

B (18:47)

Wait, it can look at chats even though I've closed the chat window?

A (18:50)

You can? Yes. So you can say, review every chat we've had this week.

B (18:53)

I thought that was the problem with Claude code, that I can't get it to look at all my past chats.

A (18:59)

It works well for me inside a cursor, so that.

B (19:02)

Okay, that is killer. Look at all my chats this week so I don't even have to have it save at the end of a conversation. And then just tell me what we could have automated.

A (19:09)

Just tell me what we should have done. Yep. And so that's a big one. Then my, my, my approach is I usually do it the manual way first. So, like, I'll usually just like, you know, pop open a new chat and I'll just start yapping at it. And then if I find myself doing the same thing kind of over and over again, then I'll build like a skill for it. So, for example, one workflow I did a lot was, I've got this meeting coming up. The team has this Google Doc. Can you help me review it? I want to know what's strong in the Google Doc, what's weak, what type of questions I should be asking, Da da da da da da da. And so I just kept doing that over and over and over again. And so that got turned into the exec review copilot. And so now anytime I want to run that, I just do exec review copilot. I copy paste in the Google Doc or docs, and then it just goes off and does all that stuff. So these things just so. So then I kind of graduate to there. And then you often can find. Well, if. If I'm. If I have. If I know I have a meeting and I've already got the doc, why am I the one that's sort of waiting to go do this? Can I just have it in my daily brief? Like in the morning, it should just go look at what's in my calendar. It should be able to see that in my calendar this doc exists. So it should just go ahead and kick off the exec review copilot. And then the link to that prep should actually happen inside my daily brief instead of me having to be the one that triggers this stuff. So you start to go from just manual, like I'm just doing this all the time to now, as you find yourself just doing these things over and over and over, you're just progressively adding small little features that make it slicker and slicker over time.

B (20:52)

Is the daily brief a skill that's then part that is triggered by a cron job?

A (20:57)

Yes, I have a cron job triggering the daily brief right now.

B (21:02)

Wade, can we get the skill that you use for demo mode, the skill that you use for the executive review copilot, something that will help us create a daily brief similar to what you've got?

A (21:11)

Yep, sure can.

B (21:12)

All right, we're going to have a link to it in the show notes. All right. I'm really excited to play around with this. This is so fricking fun. And the idea is that I'm just going to keep coming into Claude, giving it more access. I use VS code and just seeing what I can do and what I could have it do for me.

A (21:28)

Love it.

B (21:29)

Hell yeah. Okay. Hey, my agent says that if you watch this far, you're going to want to subscribe. And Google thinks that if you watch this far, you'll want to watch that video.