Okay, back we go to amplify.
Back we go into business development.
Let's create a new workflow.
And let's call this one business development Manager.
This is where the action happens.
Okay.
So what's gonna trigger this workflow.
What is it going to set.
Going our chain of events to bring us new business.
Well I'm going to suggest that we start with something which is an old friend from earlier this week.
Please create a new folder in your Google Drive called ICP File Drop.
ICP stands for Ideal Customer Profile and is like a business speak for a description of the customer
you're really going for for your business.
So ICP file drop is the first thing to make a new folder like that and then go back here.
And of course you'll never guess what trigger that we want.
Were you going to make something that looks in that folder and wakes up when something is dropped there.
So we start by looking for Google Drive in the triggers, and we are going to say on changes involving
a specific folder, look every minute, just as we did before, we're going to choose the folder from
the list.
And I've chosen the ICP file drop there.
And I'm going to say when a file is created, there we go.
And of course, the only reason this works is because we have connected with our Google Drive, and
we went through that insane OAuth two flow earlier this week, which is cool that it's going to be triggered
based on this.
So there is the first node in our workflow, and now it's time to do the second one, which is going
to again be Google Drive.
Do you remember what we did next?
It was Google Drive.
Once we've detected that a file has changed we then have to download the file.
So this is this is the download file thing which is where we we go ahead and bring in the file that
just just got added.
And the trick here file we want download.
We want to choose from ID not based on a file.
We want to make this an expression.
And that needs to be the ID that's come in from the previous node.
And so we do JSON ID because you may remember we saw earlier this week that that um trigger that is
triggered when a file is added.
What it passes to the next node is the ID of that file.
So this should work perfectly.
Excellent.
So that has now woken up when a file is dropped in, the file has been downloaded.
What do we need to do next.
Well we're going to assume it's a PDF file.
That's going to be the rule for now.
So we're going to add something in here.
We want an extract from file node.
And it comes extract from PDF.
And this is all set up right.
Actually we want the input binary field to be data.
We want it to extract from PDF.
No more options there.
That's just going to work out of the box perfectly.
At least I hope so.
Okay, now we hit something of a fork in the road.
What we want to do now is given this ICP, we want to first of all look to find leads.
That would be good leads, good prospects for this ICP by searching the internet and then potentially
for those, we're going to want to load them into Pipedrive and we're going to send them draft emails.
And we have three subagents for those three steps.
And there's certainly a school of thought that would be to say, we've got these three things.
We want to do them one after another.
This sounds like a workflow, and we can put them on a timeline and have each one run equally.
You could say this is something where we want to be able to potentially have some autonomy.
Maybe we'd want to have a couple of shots at getting different sets of leads until we're happy with
them.
And so it's something where allowing an LLM to orchestrate the workflow could result in better outcomes.
And the right answer, of course, is that you have to try both and see, and you have to have a good
way to measure effectiveness.
And that way would typically be what kind of revenue, what kind of sales leads do you actually generate
and which approach ends up resulting in better outcomes.
And for today, of course, we're going to do the AI agent, the autonomous way because it's more fun.
And it's a it's a more interesting way to start with.
But you should try both.
Uh, but let's go ahead now and create an AI agent and equip it with tools so that it can call our sub
workflows.
Okay, let's do it.
Plus AI, AI agent.
We know it so well.
Chat model I'm going to pick OpenAI.
You can pick whatever model you like.
And within OpenAI I'm going to pick GPT 5.2 a nice beefy model.
But you should pick whatever suits your budget and interests and experiment with different models.
Always good to experiment.
No need for memory.
This isn't going to be a conversation.
It's going to be a one time thing.
When a file drops and it's time to add our tools.
And we are of course going to add some tools that are going to be calling sub workflows.
Okay, here we go.
Plus And we're going to call Nate an workflow tool.
That's exactly what we want.
All right.
We want to choose one from the list.
They're going to be within amplify.
And here is our familiar prospecting subagent.
We did it such a long time ago.
It has one field called query.
And that is something that we're going to let the model define.
Now what we do need to do is add a description of this.
So we want to say call this tool to search the internet for leads.
Uh, and uh also use prospecting tools to predict their email address.
This tool will return uh, lead information.
There we go.
And now we will, uh, put in here.
a description of the prospect.
Very nice.
That is now defined.
That tool.
The prospecting subagent.
Uh, maybe we'll actually just change this again.
Call this prospecting.
Tool.
Make it very clear to it what it's doing.
Excellent.
Time to add the second tool.
Second tool.
Call workflow tool.
Also from from the list.
Which one do we want here?
Well this is the Revops subagent the one we just built.
Uh, and this is something which is where we want to to call this for each of the different sales leads.
Uh, and uh, so I'd say, uh, call this tool to save a sales lead in the database.
Describe.
The the prospect the the prospect need uh, providing.
Their, um their company, let's say their name, company and email address.
A description of the sales lead, including their name, email address, company role.
We should put in there to the name, company role and email address.
Very good.
Fine.
Okay.
Done.
We've got that.
That is our revops sales agent.
Now, you might have spotted something that's a little bit suboptimal about this flow, which is that
we actually have this prospect data in a JSON format being returned by one of our of our workflows.
And what we're doing is our agent is turning it into natural language.
We're passing that as just a description into this subagent, and that Subagent is actually going to
parse that back into JSON again.
So you could you could argue, perhaps there might be a tighter way to do this that would require less
parsing and parsing.
But I think I'd suggest to you that perhaps there could be many different routes in which sales information
might come in.
So in order to be most flexible and support different agent combinations in the future, this is the
way I decided to do it.
But for sure, if you want to do it in a in a tighter way, then you'd perhaps not have sales lead descriptions
the input here, but you'd have separate inputs for the name, role, company and email and then it
would probably be tighter, more reliable approach.
But this will work for us right now.
Let's see.
Okay.
And we've got our third tool to add.
Let's finish it off.
Here we go.
I press the plus.
I go for a call and it an workflow tool from list.
The third one, of course, is the SDR.
This is, uh, something which which will, um, generate all of the emails.
Uh, this, uh, tool generates, uh, SDR sales emails, uh, sales, uh, outreach emails to all prospects
that have been loaded into the Pipedrive CRM.
Okay.
And again, as an enhancement, the people that are really, uh, tracking me carefully, that are ready
to you've got your hands on the keyboards to to to message me and say by you.
I do realize that it would be tighter for this to actually pass in the list of prospects, but I wanted
to keep it relatively simple.
I didn't don't want to overcomplicate it, but of course I'll be a better way to do this.
Otherwise it's going to generate a whole ton of emails every single time, which is probably not a great
idea.
So that would be a good enhancement.
Um, but I didn't want to get sidetracked into too much detail.
Okay, so this generates SDR sales outreach emails.
Let me just check here that I've been clear enough sales leads.
And let's let's call this in the Pipedrive.
CRM database.
Let's make sure it's absolutely clear what's going on here.
Um, okay.
Very nice.
So back we go.
Let's check these three things here.
This one clearly says call this prospecting tool to search the internet for leads.
This one clearly says call this tool to save a sales lead in the Pipedrive CRM.
Uh, and then this one here says this tool generates SDR outreach for all prospects that have been loaded
into the Pipedrive CRM.
Let's say call this tool one time to generate all draft emails.
Let's make that super clear.
Always good to be specific and clear in these.
And let's say here call this tool for uh, separately for each prospect to be saved.
Done.
That's super clear.
And then back we go.
And finally, for this tool, uh, call this tool once to retrieve multiple sales prospects.
Okay, we've set that up.
We've described everything very clearly.
Uh, we may have to come back and tweak it and refine it because it's very iterative, experimental,
this process of prompting.
But it seems like a very good start.
Uh, it's almost time to, uh, give this whole thing a try.