WEBVTT 00:00.040 --> 00:02.240 Okay, back we go to amplify. 00:02.360 --> 00:04.400 Back we go into business development. 00:04.400 --> 00:06.560 Let's create a new workflow. 00:06.760 --> 00:13.360 And let's call this one business development Manager. 00:13.760 --> 00:16.200 This is where the action happens. 00:16.360 --> 00:16.880 Okay. 00:17.080 --> 00:18.880 So what's gonna trigger this workflow. 00:18.880 --> 00:19.880 What is it going to set. 00:19.920 --> 00:24.200 Going our chain of events to bring us new business. 00:24.400 --> 00:30.840 Well I'm going to suggest that we start with something which is an old friend from earlier this week. 00:30.880 --> 00:37.320 Please create a new folder in your Google Drive called ICP File Drop. 00:37.520 --> 00:44.680 ICP stands for Ideal Customer Profile and is like a business speak for a description of the customer 00:44.680 --> 00:47.040 you're really going for for your business. 00:47.040 --> 00:53.640 So ICP file drop is the first thing to make a new folder like that and then go back here. 00:53.840 --> 00:56.960 And of course you'll never guess what trigger that we want. 00:57.240 --> 01:01.860 Were you going to make something that looks in that folder and wakes up when something is dropped there. 01:01.860 --> 01:08.940 So we start by looking for Google Drive in the triggers, and we are going to say on changes involving 01:08.980 --> 01:15.340 a specific folder, look every minute, just as we did before, we're going to choose the folder from 01:15.340 --> 01:16.100 the list. 01:16.100 --> 01:18.700 And I've chosen the ICP file drop there. 01:18.700 --> 01:23.460 And I'm going to say when a file is created, there we go. 01:23.620 --> 01:26.820 And of course, the only reason this works is because we have connected with our Google Drive, and 01:26.820 --> 01:33.060 we went through that insane OAuth two flow earlier this week, which is cool that it's going to be triggered 01:33.060 --> 01:34.460 based on this. 01:34.580 --> 01:41.660 So there is the first node in our workflow, and now it's time to do the second one, which is going 01:41.700 --> 01:43.020 to again be Google Drive. 01:43.020 --> 01:44.380 Do you remember what we did next? 01:44.420 --> 01:45.780 It was Google Drive. 01:45.940 --> 01:50.580 Once we've detected that a file has changed we then have to download the file. 01:50.580 --> 01:57.140 So this is this is the download file thing which is where we we go ahead and bring in the file that 01:57.140 --> 01:58.260 just just got added. 01:58.260 --> 02:01.200 And the trick here file we want download. 02:01.200 --> 02:04.480 We want to choose from ID not based on a file. 02:04.480 --> 02:06.320 We want to make this an expression. 02:06.320 --> 02:11.200 And that needs to be the ID that's come in from the previous node. 02:11.240 --> 02:18.280 And so we do JSON ID because you may remember we saw earlier this week that that um trigger that is 02:18.280 --> 02:19.760 triggered when a file is added. 02:19.760 --> 02:23.280 What it passes to the next node is the ID of that file. 02:23.280 --> 02:25.560 So this should work perfectly. 02:25.920 --> 02:26.680 Excellent. 02:26.680 --> 02:31.520 So that has now woken up when a file is dropped in, the file has been downloaded. 02:31.520 --> 02:32.680 What do we need to do next. 02:32.720 --> 02:35.080 Well we're going to assume it's a PDF file. 02:35.080 --> 02:36.600 That's going to be the rule for now. 02:36.600 --> 02:38.000 So we're going to add something in here. 02:38.000 --> 02:41.000 We want an extract from file node. 02:41.240 --> 02:43.600 And it comes extract from PDF. 02:43.960 --> 02:45.200 And this is all set up right. 02:45.200 --> 02:47.880 Actually we want the input binary field to be data. 02:47.920 --> 02:49.480 We want it to extract from PDF. 02:49.480 --> 02:50.680 No more options there. 02:50.800 --> 02:53.960 That's just going to work out of the box perfectly. 02:54.400 --> 02:55.160 At least I hope so. 02:55.200 --> 02:58.160 Okay, now we hit something of a fork in the road. 02:58.160 --> 03:05.100 What we want to do now is given this ICP, we want to first of all look to find leads. 03:05.100 --> 03:11.740 That would be good leads, good prospects for this ICP by searching the internet and then potentially 03:11.740 --> 03:16.340 for those, we're going to want to load them into Pipedrive and we're going to send them draft emails. 03:16.340 --> 03:19.660 And we have three subagents for those three steps. 03:19.660 --> 03:23.100 And there's certainly a school of thought that would be to say, we've got these three things. 03:23.100 --> 03:24.820 We want to do them one after another. 03:24.860 --> 03:30.820 This sounds like a workflow, and we can put them on a timeline and have each one run equally. 03:30.820 --> 03:34.940 You could say this is something where we want to be able to potentially have some autonomy. 03:34.980 --> 03:38.980 Maybe we'd want to have a couple of shots at getting different sets of leads until we're happy with 03:38.980 --> 03:39.340 them. 03:39.340 --> 03:46.140 And so it's something where allowing an LLM to orchestrate the workflow could result in better outcomes. 03:46.500 --> 03:50.940 And the right answer, of course, is that you have to try both and see, and you have to have a good 03:50.940 --> 03:52.900 way to measure effectiveness. 03:52.900 --> 03:57.700 And that way would typically be what kind of revenue, what kind of sales leads do you actually generate 03:57.700 --> 04:01.190 and which approach ends up resulting in better outcomes. 04:01.190 --> 04:06.590 And for today, of course, we're going to do the AI agent, the autonomous way because it's more fun. 04:06.590 --> 04:09.350 And it's a it's a more interesting way to start with. 04:09.350 --> 04:10.750 But you should try both. 04:10.950 --> 04:17.630 Uh, but let's go ahead now and create an AI agent and equip it with tools so that it can call our sub 04:17.630 --> 04:18.390 workflows. 04:18.430 --> 04:19.430 Okay, let's do it. 04:19.470 --> 04:22.790 Plus AI, AI agent. 04:22.790 --> 04:23.950 We know it so well. 04:24.150 --> 04:27.270 Chat model I'm going to pick OpenAI. 04:27.470 --> 04:29.470 You can pick whatever model you like. 04:29.630 --> 04:37.230 And within OpenAI I'm going to pick GPT 5.2 a nice beefy model. 04:37.230 --> 04:41.830 But you should pick whatever suits your budget and interests and experiment with different models. 04:41.830 --> 04:43.350 Always good to experiment. 04:43.390 --> 04:44.190 No need for memory. 04:44.190 --> 04:45.630 This isn't going to be a conversation. 04:45.630 --> 04:47.510 It's going to be a one time thing. 04:47.510 --> 04:51.270 When a file drops and it's time to add our tools. 04:51.270 --> 04:55.710 And we are of course going to add some tools that are going to be calling sub workflows. 04:55.750 --> 04:56.750 Okay, here we go. 04:56.790 --> 05:00.570 Plus And we're going to call Nate an workflow tool. 05:00.570 --> 05:01.770 That's exactly what we want. 05:02.130 --> 05:02.810 All right. 05:02.810 --> 05:04.690 We want to choose one from the list. 05:04.730 --> 05:06.610 They're going to be within amplify. 05:06.850 --> 05:10.290 And here is our familiar prospecting subagent. 05:10.290 --> 05:11.730 We did it such a long time ago. 05:11.970 --> 05:14.130 It has one field called query. 05:14.330 --> 05:17.170 And that is something that we're going to let the model define. 05:17.210 --> 05:19.530 Now what we do need to do is add a description of this. 05:19.530 --> 05:28.530 So we want to say call this tool to search the internet for leads. 05:29.250 --> 05:40.370 Uh, and uh also use prospecting tools to predict their email address. 05:41.410 --> 05:51.290 This tool will return uh, lead information. 05:52.370 --> 05:53.050 There we go. 05:53.770 --> 05:56.650 And now we will, uh, put in here. 05:57.830 --> 06:01.790 a description of the prospect. 06:04.670 --> 06:05.470 Very nice. 06:05.710 --> 06:07.470 That is now defined. 06:07.470 --> 06:08.510 That tool. 06:08.670 --> 06:10.710 The prospecting subagent. 06:11.270 --> 06:13.590 Uh, maybe we'll actually just change this again. 06:13.590 --> 06:14.950 Call this prospecting. 06:18.030 --> 06:18.550 Tool. 06:18.870 --> 06:20.870 Make it very clear to it what it's doing. 06:20.990 --> 06:21.710 Excellent. 06:21.750 --> 06:22.990 Time to add the second tool. 06:23.030 --> 06:23.910 Second tool. 06:23.950 --> 06:26.270 Call workflow tool. 06:26.270 --> 06:28.510 Also from from the list. 06:28.510 --> 06:30.670 Which one do we want here? 06:30.870 --> 06:35.390 Well this is the Revops subagent the one we just built. 06:35.550 --> 06:42.310 Uh, and this is something which is where we want to to call this for each of the different sales leads. 06:42.510 --> 06:53.750 Uh, and uh, so I'd say, uh, call this tool to save a sales lead in the database. 06:54.710 --> 06:55.710 Describe. 06:58.210 --> 07:06.090 The the prospect the the prospect need uh, providing. 07:10.770 --> 07:21.410 Their, um their company, let's say their name, company and email address. 07:24.410 --> 07:37.970 A description of the sales lead, including their name, email address, company role. 07:37.970 --> 07:41.170 We should put in there to the name, company role and email address. 07:41.170 --> 07:42.010 Very good. 07:42.050 --> 07:42.650 Fine. 07:42.970 --> 07:43.610 Okay. 07:43.970 --> 07:44.650 Done. 07:44.690 --> 07:45.690 We've got that. 07:45.690 --> 07:48.570 That is our revops sales agent. 07:48.610 --> 07:53.650 Now, you might have spotted something that's a little bit suboptimal about this flow, which is that 07:53.650 --> 08:00.390 we actually have this prospect data in a JSON format being returned by one of our of our workflows. 08:00.390 --> 08:03.750 And what we're doing is our agent is turning it into natural language. 08:03.750 --> 08:09.550 We're passing that as just a description into this subagent, and that Subagent is actually going to 08:09.590 --> 08:11.990 parse that back into JSON again. 08:11.990 --> 08:17.390 So you could you could argue, perhaps there might be a tighter way to do this that would require less 08:17.390 --> 08:18.670 parsing and parsing. 08:18.670 --> 08:23.190 But I think I'd suggest to you that perhaps there could be many different routes in which sales information 08:23.190 --> 08:24.070 might come in. 08:24.070 --> 08:29.390 So in order to be most flexible and support different agent combinations in the future, this is the 08:29.390 --> 08:30.590 way I decided to do it. 08:30.590 --> 08:36.670 But for sure, if you want to do it in a in a tighter way, then you'd perhaps not have sales lead descriptions 08:36.670 --> 08:43.670 the input here, but you'd have separate inputs for the name, role, company and email and then it 08:43.670 --> 08:46.950 would probably be tighter, more reliable approach. 08:47.190 --> 08:48.910 But this will work for us right now. 08:48.950 --> 08:49.710 Let's see. 08:50.190 --> 08:50.670 Okay. 08:50.710 --> 08:52.670 And we've got our third tool to add. 08:52.710 --> 08:53.590 Let's finish it off. 08:53.590 --> 08:54.110 Here we go. 08:54.150 --> 08:55.330 I press the plus. 08:55.530 --> 08:59.930 I go for a call and it an workflow tool from list. 08:59.970 --> 09:02.090 The third one, of course, is the SDR. 09:02.570 --> 09:09.450 This is, uh, something which which will, um, generate all of the emails. 09:09.690 --> 09:24.690 Uh, this, uh, tool generates, uh, SDR sales emails, uh, sales, uh, outreach emails to all prospects 09:25.370 --> 09:33.450 that have been loaded into the Pipedrive CRM. 09:35.010 --> 09:35.610 Okay. 09:36.050 --> 09:41.450 And again, as an enhancement, the people that are really, uh, tracking me carefully, that are ready 09:41.450 --> 09:45.850 to you've got your hands on the keyboards to to to message me and say by you. 09:46.010 --> 09:52.490 I do realize that it would be tighter for this to actually pass in the list of prospects, but I wanted 09:52.490 --> 09:53.690 to keep it relatively simple. 09:53.690 --> 09:57.340 I didn't don't want to overcomplicate it, but of course I'll be a better way to do this. 09:57.340 --> 10:01.660 Otherwise it's going to generate a whole ton of emails every single time, which is probably not a great 10:01.660 --> 10:01.940 idea. 10:01.940 --> 10:04.020 So that would be a good enhancement. 10:04.140 --> 10:07.860 Um, but I didn't want to get sidetracked into too much detail. 10:08.140 --> 10:11.620 Okay, so this generates SDR sales outreach emails. 10:11.620 --> 10:14.380 Let me just check here that I've been clear enough sales leads. 10:14.380 --> 10:16.700 And let's let's call this in the Pipedrive. 10:19.260 --> 10:21.260 CRM database. 10:21.260 --> 10:24.700 Let's make sure it's absolutely clear what's going on here. 10:25.060 --> 10:26.820 Um, okay. 10:27.180 --> 10:28.100 Very nice. 10:28.340 --> 10:29.500 So back we go. 10:29.500 --> 10:32.020 Let's check these three things here. 10:32.020 --> 10:36.620 This one clearly says call this prospecting tool to search the internet for leads. 10:36.620 --> 10:41.700 This one clearly says call this tool to save a sales lead in the Pipedrive CRM. 10:42.140 --> 10:48.500 Uh, and then this one here says this tool generates SDR outreach for all prospects that have been loaded 10:48.660 --> 10:50.420 into the Pipedrive CRM. 10:50.460 --> 10:59.080 Let's say call this tool one time to generate all draft emails. 10:59.080 --> 11:00.600 Let's make that super clear. 11:00.640 --> 11:03.560 Always good to be specific and clear in these. 11:03.760 --> 11:16.480 And let's say here call this tool for uh, separately for each prospect to be saved. 11:17.760 --> 11:18.280 Done. 11:18.480 --> 11:19.520 That's super clear. 11:19.960 --> 11:22.240 And then back we go. 11:22.240 --> 11:35.520 And finally, for this tool, uh, call this tool once to retrieve multiple sales prospects. 11:37.200 --> 11:39.360 Okay, we've set that up. 11:39.360 --> 11:41.640 We've described everything very clearly. 11:41.800 --> 11:46.080 Uh, we may have to come back and tweak it and refine it because it's very iterative, experimental, 11:46.080 --> 11:47.280 this process of prompting. 11:47.280 --> 11:49.440 But it seems like a very good start. 11:49.640 --> 11:53.200 Uh, it's almost time to, uh, give this whole thing a try.